agentleFS
mahumadadmahumadad/quarry/skills/core/data-retention/SKILL.md

data-retention

Skill1 starsChanged 2 days agoMITView on GitHub

Apply the engagement's data retention policy — archive, redact, or destroy per contractual terms

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never destroy the sealed custody chain or final report.

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Data Retention

Apply retention policy after evidence sealing.

Process

  1. Read retention terms — Check scope.json for retention_days and retention_policy (archive / redact / destroy). Default: archive for 90 days, then offer destruction.
  2. Classify data —
    • Keep: Sealed custody chain, final report, finding summaries
    • Redact: Raw HTTP responses containing PII, database dumps, credential material (already handled by credential-hygiene)
    • Destroy: Temporary scan output, working notes, draft reports
  3. Execute —
    • Archive: compress engagement directory, store with sealed chain
    • Redact: replace sensitive values with [REDACTED] in archived copies
    • Destroy: secure-delete (shred or platform equivalent) working files
  4. Document — Log retention actions in the closeout checklist with what was kept, redacted, and destroyed.

Rules

  • Never destroy the sealed custody chain or final report.
  • Retention periods are contractual — follow the client's terms, not defaults.
  • Log all destruction actions before executing them.

Download now (ZIP)

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.