agentleFS
getcargohqgetcargohq/cargo-manifest/.agents/skills/context-hygiene/SKILL.md

context-hygiene

Skill12 starsChanged 18 days agoMITView on GitHub

Audit and repair the context layer. Use when asked to clean up context, before a quarterly review, or when the knowledge graph feels stale. Finds missing frontmatter, broken references, orphan files, and stale content, then fixes them file by file.

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Mechanical lint: Run npm run lint:context. Fix every error (missing title/description, broken references: entries, broken wikilinks or …

    line 13
  2. Very specific:

    Contradictions: Read global/ and icp/ together and flag claims that conflict (two different ICPs, outdated competitor claims in …

    line 26
  3. Very specific:

    Never invent facts to fill a template.

    line 37

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “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

Context hygiene pass

The context layer is only useful if agents can trust it. Run this audit periodically or when onboarding a new team member.

Steps

  1. Mechanical lint. Run npm run lint:context. Fix every error (missing title/description, broken references: entries, broken wikilinks or relative links). Errors block CI; do these first.
  2. Orphans. The linter warns about files nothing references. For each orphan, decide: link it from the file that should own the relationship, or delete it if it no longer earns its place. Do not leave orphans standing.
  3. Staleness. The linter warns about files untouched for more than 90 days. For each, check it against reality: recent won/lost deals in context/client/, current pricing, live positioning. Update the file or add a dated note explaining why it is still accurate.
  4. Contradictions. Read global/ and icp/ together and flag claims that conflict (two different ICPs, outdated competitor claims in alternative/). Surface contradictions to the team in the PR description rather than silently picking a side.
  5. Ship it. One PR titled context: hygiene pass YYYY-MM-DD, with a summary table: files fixed, orphans resolved, stale files refreshed, contradictions flagged.

Rules

  • Never invent facts to fill a template. An honest gap beats a plausible lie; leave the section empty with a TODO(owner): marker.
  • Preserve frontmatter fields you do not understand.

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.