agentleFS
baberarjumandbaberarjumand/agentic_markdown_memory_agent-skill/.agents/skills/memory-audit/SKILL.md

memory-audit

Skill0 starsChanged 35 days agoMITView on GitHub

Audits a project's markdown memory (AGENTS.md, docs/, knowledge/, sources/, tasks/, memory/, SCRATCHPAD.md, HANDOFF.md) for size budgets, stale or contradictory entries, broken links, index drift, orphan files, missing frontmatter, unsafe content, and always-on token cost. Reports findings and proposes fixes. Use when asked to check, clean up, or review agent memory, or when AGENTS.md has grown large.

14 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, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Run node <this-skill-dir>/scripts/audit.mjs --json from the project root (or pass --root <dir>).

    line 16
  2. Distinctive:

    After approved fixes, re-run the audit and report what changed.

    line 19
  3. Distinctive:

    Check ids and fixes: references/checks.md

    line 35

“Common” is measured: kept by at least 6 in 10 of the 11 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

Memory audit

Requirements

Requires a local filesystem. If you cannot list and edit the project, stop and say so.

Procedure

  1. Run node <this-skill-dir>/scripts/audit.mjs --json from the project root (or pass --root <dir>). If Node is unavailable, do the checks manually from references/checks.md.
  2. Report findings grouped by severity: error, warn, info.
  3. Propose fixes as a table: file, check id, problem, proposed change. Apply nothing without confirmation. Never delete content. Archive by setting status: archived or moving to docs/archive/YYYY-MM-DD/.
  4. After approved fixes, re-run the audit and report what changed.

Useful flags

FlagMeaning
--checkCI mode: exit non-zero on errors or stale generated blocks; write nothing
--write-indexRegenerate text between index markers only
--write-tocRegenerate TOC blocks
--report-tokensPrint always-on cost estimate
--include-archivedInclude archived files in index generation

Exit codes: 0 clean, 1 warnings only, 2 errors.

References

  • Check ids and fixes: references/checks.md
  • Layout and practices copies (when synced): references/layout.md, references/practices.md

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.