agentleFS
creanlabcreanlab/agent-genome-lab/.agents/skills/repo-auditor/SKILL.md

repo-auditor

Skill2 starsChanged 4 months agoMITView on GitHub

Audit repo structure, memory health, compatibility, and security

  • Reads credentials

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    After migration or structural change

    line 13
  2. Distinctive:

    Verify these paths exist:

    line 19

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

Repo Auditor

Performs structural audit of the Evolution Tamagotchi repository.

When to Use

  • At session start (lightweight check)
  • After migration or structural change
  • Periodically to check for drift

Procedure

1. Structure Check

Verify these paths exist:

AGENTS.md
.agents/rules/*.md (7 files)
.agents/workflows/*.md (11 files)
.agents/skills/*/SKILL.md (5 skills)
.evolution/incidents/
.evolution/experience_units/
.evolution/failure_genomes/
docs/backlog_tama.md
docs/research.md
docs/POMDP_framework.md
schemas/failure-genome.schema.json

2. Memory Health

Count files in .evolution/incidents/
Count files in .evolution/experience_units/
Count files in .evolution/failure_genomes/
Check for orphans (EU without matching INC)
Check staleness (days since last incident)

3. Compatibility Check

Verify web/index.html exists (dashboard)
Verify TAMA_start/ exists (starter kit)
Verify 5 wrapper workflows exist
Verify web/vision.html or vision_legacy.html exists

4. Security Scan

grep for API key patterns in tracked files
Check .gitignore includes: .env, gcp-key.json
Check .evolution/exports/ for unredacted data

Output

Save to .evolution/audits/AUDIT-YYYYMMDD.json

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.