agentleFS
mfollmfoll/second-brain-template/.agents/skills/review-vault-health/SKILL.md

review-vault-health

Skill1 starsChanged 22 days agoMITView on GitHub

Assess vault usefulness, current state and retrieval in the selected deployed vault; recommend maintenance priorities, read-only by default.

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.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the vault rules and Procedure completely before acting.

    line 18
  2. Distinctive:

    Default to read-only and inventory canonical notes only.

    line 22
  3. Distinctive:

    Use compactness metrics as evidence, not a reason to shorten cold Sources or Events.

    line 26
  4. Distinctive:

    Prefer a few high-value recommendations and propose broad changes before applying them.

    line 27

≈ “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

Review Vault Health

Assess whether the vault remains useful, current and easy to navigate. Recommend a few high-value improvements, read-only by default.

For mechanical defects, use lint-vault. Health review interprets some of the same audit evidence; a structurally valid vault can still contain stale summaries or buried decisions.

Source of truth

  • Vault rules: AGENTS.md
  • Complete workflow: procedures/review-vault-health.md
  • Helper: .agents/skills/lint-vault/scripts/compactness_audit.py

Read the vault rules and Procedure completely before acting.

Guardrails

  • Default to read-only and inventory canonical notes only.
  • Inspect entry points, Types, active Projects and Responsibilities, views, Questions, synthesis, Procedures, ADRs, and skills.
  • Judge low counts rather than enforcing quotas.
  • Distinguish lint findings from strategic issues such as overloaded entry notes, append-only writeback, weak resumption, or hidden knowledge.
  • Use compactness metrics as evidence, not a reason to shorten cold Sources or Events.
  • Prefer a few high-value recommendations and propose broad changes before applying them.

Select this package by the requested vault role, not its name alone. Reuse rules and the complete Procedure already read in this session while they remain current; reread after a relevant change.

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.