agentleFS
QuarktexQuarktex/qcobrain/.claude/skills/curator/SKILL.md

curator

Skill4 starsChanged 4 months agoMITView on GitHub

Slow evolution loop — run weekly. Re-resolves every src citation, finds drift / stale quotes / orphans / broken links, regenerates INDEX.md and digests/ deterministically, burns down inbox/ older than 14 days, then consolidates — merges near-duplicates, supersedes stale notes, archives spent ones. Invariants — never delete (archive only to archives/), only ever touch origin:agent-generated notes, pinned:true is immune, never edit a source to match a note. Appends to runtime/curator-log.md. Trigger on "run curator", "weekly cleanup", or the weekly cadence. Documented cron-able later.

2 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

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:

    Supersede stale: when a newer note states current truth, set the old one status: superseded

    line 37
  2. Very specific:

    Every mutation is reversible: supersede/archive, never delete.

    line 68

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

Inherits references/kernel.md (the provenance contract). Reads references/wiki-spec.md for schema.

What this is

The slow half of the metabolism (the fast half is /review). Where /review adds, the curator consolidates. It is /wiki-doctor on a schedule plus the judgment-call mutations /wiki-doctor deliberately leaves to a human — but constrained by hard invariants so it can run with autonomy without rotting the brain. In v1 you invoke it weekly; it is cron-able later (see runtime/README.md).

The invariants (non-negotiable — the curator invariants from kernel §3)

  • Never delete → archive only. A spent note moves to archives/, never rm.
  • Only touch origin: agent-generated. user-directed notes are off-limits.
  • pinned: true is immune to every operation here.
  • Never edit a source to match a note — if a quote drifted, fix the note, never the source.

Execution

1 — Integrity sweep (read-only — the same checks as /wiki-doctor)

  • Recompute each sources/ file hash (shasum -a 256 <f> | cut -c1-12); compare to sources/_sources.md. Drift → mark its last_verified stale and check dependent notes.
  • Re-resolve every src block quote verbatim (whitespace-normalized) against its source file. Anything that no longer resolves → STALE (record note id + source-key + failing quote).
  • Find orphans (no inbound/outbound [[wikilinks]]), broken links ([[...]]/links: ids with no wiki/ file), circular provenance (a src whose source is a wiki/ id — flag loudly), and near-duplicates (near-identical titles/tags).

2 — Consolidate (mutations — agent-generated + unpinned ONLY)

  • Merge near-duplicates: fold the weaker/younger agent-generated note into the canonical one (move its src blocks over), set the merged-away note status: superseded + superseded_by: <id>, and move it to archives/.
  • Supersede stale: when a newer note states current truth, set the old one status: superseded
    • superseded_by; never delete.
  • Archive spent: agent-generated notes that are stale-beyond-repair (source gone, quote unrecoverable) → archives/ with a one-line reason. Their source file stays in sources/.
  • Anything user-directed or pinned: true → list it under "needs your call", do NOT act on it.

3 — Inbox burn-down

  • inbox/ drafts older than 14 days → resolve (source it via /capture → wiki/) or archive. The inbox is a quarantine, not a graveyard.

4 — Regenerate the derived files (deterministic)

  • Rebuild INDEX.md from wiki/ frontmatter — NOTES, SUPERSEDED (from superseded_by), HEALTH. Preserve hand-curated ALIASES; append obvious new ones. Never leave INDEX.md diverged from disk.
  • Regenerate digests/ (product.md, goals.md, recent-decisions.md, user-profile.md) from context/ + decisions/log.md + wiki/. Each digest line keeps its (→ note-id) provenance pointer.

5 — Log the run

Append to runtime/curator-log.md (header if it doesn't exist yet), newest on top:

## <date> — curator
merged: <n>   superseded: <n>   archived: <n>   inbox burned: <n>
stale fixed: <n>   drift: <n>   index+digests: regenerated
needs your call: [id — reason]

6 — Report

A health summary plus the list of judgment calls left for you — the pinned/user-directed items the curator refused to touch.

Guardrails (hard)

  • Every mutation is reversible: supersede/archive, never delete. archives/ is the undo log.
  • A note is touchable only if origin: agent-generated AND pinned: false. Anything else → report, don't act.
  • Derived files (INDEX.md, digests/) are rebuilt from source-of-truth, never hand-patched into staleness.
  • The integrity sweep is read-only; it never "repairs" a quote by rewriting the source.

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.