agentleFS
annatchijovaannatchijova/SKILLS/acquisition-order-of-volatility/SKILL.md

acquisition-order-of-volatility

Skill9 starsChanged 4 months agoLicence not identifiedView on GitHub

Collect digital evidence in order of volatility, or destroy the thing you came for — memory, network state, and running processes evaporate the moment you pull power or start "just looking," and the act of collecting alters the scene, so order and method are the evidence's admissibility, not a formality. Use whenever evidence is being captured from a live or suspect system: "acquire the disk", "grab a memory dump", "should we pull the plug or shut down gracefully", "image this machine", "collect logs from the compromised host", "preserve the evidence", "is this forensically sound", "we already rebooted it". Sibling of finding-custody (chain of custody of the artifact) and tamper-evident-audit-chain (proving it was not altered after); it governs the collection act itself. It does not analyze the acquired image (that is the investigation) and never presents evidence collected out of order or without footprint as if it were pristine.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.