Artefact Triage Preservation

Community

Sahil-SS9

artefact-triage-preservation

Triage unknown files safely: identify, fingerprint, chain-of-custody and preserve evidence before any analysis.

Overview

Publisher	Sahil-SS9
Repository	`agent-personas`
Skill name	`artefact-triage-preservation`
Stars	67
Forks	4
Bundled files	1
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by Sahil-SS9 on GitHub. Read the source before you install it.

Installation

Install the Artefact Triage Preservation AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/Sahil-SS9/agent-personas/tree/main/skills/artefact-triage-preservation
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/Sahil-SS9/agent-personas/tree/main/skills/artefact-triage-preservation

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/Sahil-SS9/agent-personas.git /tmp/agent-personas
mkdir -p .claude/skills
cp -r /tmp/agent-personas/skills/artefact-triage-preservation .claude/skills/artefact-triage-preservation

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Artefact Triage Preservation in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Artefact Triage Preservation on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Artefact Triage Preservation is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Artefact triage and preservation

Treat every unknown file as a crime scene: what you touch, you alter. Stabilise before you study.

When to use

First contact with an unknown artefact: a binary, document, firmware image, disk or memory capture, archive or email attachment.

Procedure

Work on copies only. The original becomes read-only evidence immediately; every derived copy records the original's SHA-256.
Identify before tools touch it: file signature/magic, container structure, hashes, size, timestamps. Treat file output as a hypothesis — packed or malformed files lie.
Establish provenance: where it came from, when, from whom; record the acquisition channel. A sample without provenance is reported as such.
Choose the containment level before any execution: presumed hostile unless the owner's scope says otherwise. Execution decisions belong to the runtime-investigation stage, never the triage stage.
Package evidence: archive (original + hashes + notes + tool versions + a timeline of every action taken) with a manifest that lets a stranger reproduce the workspace.
Triage depth ladder: signature → container/packer hints → strings (as hints, not conclusions) → imports/capabilities (hypotheses) → deeper analysis only with a written question the step will answer.
Timebox the pass: triage aims to route the artefact (what is it, how dangerous to handle, what it likely is) — not to answer every question.

Decision rules

An execution decision made during triage is a defect: route, do not run.
ldd, debuggers and instrumentation are not read-only operations; if a tool can execute or modify the artefact, it does not belong in triage.
If identification is ambiguous (packed, obfuscated, unusual entry), say so and hand over the ambiguity, not a forced guess.
Archive integrity is part of done: the manifest verifies, or the triage is not done.

Pitfalls

Opening archives with auto-extraction tools that execute contained code or follow links.
Treating strings/imports as evidence of behaviour rather than capability hints.
Losing timestamps by copying without preserving metadata.

Done

An evidence package with verified hashes, provenance, identification with stated confidence, containment decision, routing recommendation and retained ambiguity.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

NOTICE1 KB

Frequently asked questions

What does the Artefact Triage Preservation AI skill do?

Triage unknown files safely: identify, fingerprint, chain-of-custody and preserve evidence before any analysis.

Why use Artefact Triage Preservation on TypingMind?

Because you install it once and use it with any model. Artefact Triage Preservation is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Artefact Triage Preservation in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Sahil-SS9/agent-personas/tree/main/skills/artefact-triage-preservation. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Artefact Triage Preservation?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Artefact Triage Preservation?

As many as you like. As long as a model supports skills, you can use Artefact Triage Preservation with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Artefact Triage Preservation AI skill free?

Yes. It is published on GitHub by Sahil-SS9 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Adversarial Ux Test

NousResearch

OrganizationPopular

Roleplay a hostile user to find and triage UX pain points.

3 Statement Model

Build integrated IS/BS/CF financial workbooks in Excel.

Comps Analysis

Build comparable-company valuation workbooks in Excel.

Lbo Model

Build leveraged buyout workbooks with IRR/MOIC in Excel.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Artefact triage and preservation

When to use

Procedure

Decision rules

Pitfalls

Done

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now