agentleFS
Sign inStart free
Slava-codeSlava-code/college-kb/.claude/skills/kb-garden/SKILL.md

kb-garden

Skill0 starsChanged 32 days agoMITView on GitHub

Use when the student asks for KB maintenance, gardening, a lint or link cleanup, "tidy up the KB", or an end-of-semester cleanup; on demand only, never scheduled. Runs the checks, makes mechanical fixes, and proposes the rest.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Run scripts/rebuild-indexes.py, scripts/kb-lint.py, scripts/wikilink-check.py, scripts/reminder-ledger-check.py, and …

    line 11
  2. Very specific:

    Keep commits small: gardener: fix <summary> YYYY-MM-DD.

    line 15

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

kb-garden

AGENTS.md is canonical; this is only a thin task pointer. The full procedure, with every safety gate, is runs/prompts/gardener.md. Read it and follow it exactly; it wins over this summary.

  1. Gates first: CLAUDE.local.md hostname match; runs/PAUSE absent; clean git status --short; git pull --rebase (when a remote exists); diff caps from THRESHOLDS.md.
  2. Run scripts/rebuild-indexes.py, scripts/kb-lint.py, scripts/wikilink-check.py, scripts/reminder-ledger-check.py, and scripts/gitleaks-smoke-test.sh.
  3. Review: runs/retrieval-failures.md, stale status: active pages (STALE_ACTIVE_DAYS), finished semesters (ARCHIVE_STALE_MONTHS), past-date reminder bullets still open, missing glossary aliases, oversized or tiny pages (OVERSIZED_LINES, MIN_LINES), DEMO files left beside real pages.
  4. Fix mechanical things directly (descriptions, glossary appends, obvious broken links), each edit updating updated: and description:.
  5. Judgment calls (archive, split, merge, supersede) go as proposals in runs/gardener/YYYY-MM-DD-gardener.md (type: report; see runs/gardener/README.md). Never delete pages, process the inbox, open raw/, or rewrite decisions.
  6. Keep commits small: gardener: fix <summary> YYYY-MM-DD. Push only if asked or kb.autopush is on.

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.

Check your setup, free