steward
Skill0 starsChanged 3 months agoMITView on GitHub
Keep the vault true. Two jobs in one skill: capture (fold anything from the inbox or a finished run into the right wiki pages) and health-check (hunt contradictions, stale claims, orphan pages, and propose pruning). Run when the user says "file this", "add this to the vault", "process the inbox", "clean up the vault", "health-check my notes", or when bank, research, or recall hand something over for filing. A vault nobody maintains becomes a graveyard nobody trusts.
19 other projects use a version of this.
Adopted by
Most recently taken up by
- btraceio/btracetheir own version, first seen Nov 16, 2026
- fworks-tech/agenthoodtheir own version, first seen Nov 16, 2026
- ForeactLabs/OpenExecutivetheir own version, first seen Nov 15, 2026
- 5thlayer/skillworkstheir own version, first seen Nov 8, 2026
- ElcanoTek/fleettheir own version, first seen Nov 8, 2026
- jmagly/kintsugi-usbtheir own version, first seen Nov 8, 2026
Used with
Projects with it also use release.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillrelease
Use ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version. Performs an outward action — bumps the version in apps/desktop/package.json, commits + annotated-tags vX.Y.Z, and pushes the branch + tag. That tag push auto-builds the macOS/Windows installers and publishes a GitHub Release. Provides `status`, `bump`, `tag-push`, and a one-command `run` (bump → tag-push).
Also in 3 projects that use this
Other versions19 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 19
- btraceio/btrace★ 6ksame name
- ForeactLabs/OpenExecutive★ 5.8ksame name
- SenteLabsAI/OpenExecutive★ 5.8ksame name
- richlander/dotnet-inspect★ 166same name
- mendixlabs/mxcli★ 139same name
- yschimke/compose-ai-tools★ 127same name
- antiv/mate★ 111same name
- michelbr84/GarraRUST★ 19same name
- jmagly/kintsugi-usb★ 18same name
- jmagly/carbonyl-agent★ 16same name
9 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 1 is distinctive, and 4 are very specific to this project.
0
Common
Most of the 18 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 33
Before choosing a mode, read references/CONVENTIONS-core.md.
- Very specific: line 39
Run the shared contract's Universal preflight.
- Very specific: line 71
Before a claim is folded or carried forward, run the shared durable claim admission gate: reopen and quote its source passage, recompute it …
- Distinctive: line 77
Ask before you assert: never present a quantity, duration, sample size, date, or causal motive in prose before asking the founder for it or …
- Very specific: line 98
Treat the lint as a linked-graph sweep, not a folder checklist.
“Common” is measured: kept by at least 6 in 10 of the 18 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.
Files
steward: the vault stays true or it stops mattering
Humans abandon wikis because maintenance grows faster than value. Here the AI does the maintenance, under two disciplines that decide everything: pages get REWRITTEN to current truth, never appended into sediment, and something must regularly DELETE, or the vault becomes a junk drawer recall can't trust.
raw/inbox/ ──> [ CAPTURE ] discuss -> fold -> reconcile -> tag -> index
|
wiki/ <── rewritten pages, one truth per topic
|
weekly ──> [ HEALTH-CHECK ] contradictions, stale, orphans, graveyard
|
a short proposed diff, founder approves, then it happensRetrieval stays the environment's file search plus index.md (per the shared contract: rg or grep
where present, listing and reading otherwise). No databases, no embeddings: at vault scale,
search is not the problem, truth is.
Before choosing a mode, read references/CONVENTIONS-core.md. This resolves from
the installed skill directory to the plugin's shared contract, independent of the founder's
working folder. Its receipts, filing, and dedupe rules govern this workflow.
Step 0: Preflight
Run the shared contract's Universal preflight. A Fresh, Partial, or Wrong-folder result stops and runs the co-founder-setup skill before anything else (re-sync for Partial), without moving inbox files or editing the vault. On Ready, read the charter's path map before choosing Capture or Health-check.
Done when: the founder system is Ready and every proposed mutation has one mapped destination.
Mode A: Capture
Runs on anything in raw/inbox/, anything pasted for filing, and queue items explicitly
marked not-yet-filed. At mode open, read pending queue.md entries addressed to steward;
their stable IDs are the idempotency key for queued work. Bank and research file their OWN
outputs; a queue item that already carries file paths and a log row gets no re-filing and no
ingest row, per the shared filing-ownership rule.
- Check the ledger before reading deeply. A pasted source first lands as an immutable file
in
raw/inbox/. Compute the raw file's SHA-256 fingerprint and searchinbox-ledger.md. Same fingerprint: report "already processed" with the recorded output paths and stop with no file or log changes. Same path with changed contents is a new fingerprint and may proceed. - Read the source. It stays in
raw/untouched;raw/is the evidence locker. - Discuss the takeaways with the founder, one question at a time with a recommended answer: what matters here, and where does it file? A queue item from another skill that already settled this skips straight to folding.
- Fold, never append. A real source touches several pages: update each affected page in place so it reads as ONE current truth. New information gets integrated into the sentence where it belongs; a page with "Update (July):" stapled to its bottom has already started rotting.
- Reconcile contradictions on contact, per the shared dedupe rule: the page gets rewritten to the current truth, the old claim preserved as superseded and why. A contradiction that clears the 3-test bar (hard to reverse, surprising, real tradeoff) becomes a decision row too. Hoarding both versions and shrugging is the failure mode.
- Tag every claim with confidence (
stated/high/low) and money-link where real numbers exist. New pages carry the base-five frontmatter and areview_afterdate. Before a claim is folded or carried forward, run the shared durable claim admission gate: reopen and quote its source passage, recompute it from named inputs, or label itFounder-stated: unverified. A confidence tag never repairs a missing receipt. Apply the shared parameter gate to inferred corridors, ceilings, costs, and patterns. Ask for confirmation or preserve an unverified hypothesis; steward never canonicalizes an inference to make the vault look resolved. Ask before you assert: never present a quantity, duration, sample size, date, or causal motive in prose before asking the founder for it or citing a receipt for it. - Show the patch, then close the books. Existing pages about to change: present the
short proposed patch first (pages created and updated, contradictions reconciled, index
and fixed-hub changes) and get the yes; the founder's memory never mutates silently in capture
any more than in health-check. A plain "file this" that creates new pages and changes no
existing claim proceeds directly. Approval covers those exact lines. A later discovery starts
a new diff and waits for a new yes; without it, leave the item flagged and report NOT CLEAN.
Then: update
index.md(every touched page, one line each), link the right fixed hub, append## [date] ingest | <source>tolog.md, and run the findability test on anything new: which future search should surface this, and would it? For raw work, add the source fingerprint, outputs, and log row toinbox-ledger.md. For queued work, mark the same queue item IDdonewith its output paths after the files are durable.
Done when: the source's knowledge lives in rewritten pages, the catalog knows them, the ledger proves raw-source processing is idempotent, and any queue entry is done.
Mode B: Health-check
Runs weekly (review hands over its stale flags), or on demand.
Treat the lint as a linked-graph sweep, not a folder checklist. Seed it with every canonical file
changed since the latest lint row, every active initiative, the current offer, published or
approved content, due claims, and pending queue items. For each seed, follow explicit links and the
shared linked-state projections until no new node appears. Record each hit as: seed; linked
surfaces checked; contradiction; proposed resolution.
Sweep the vault for exactly these, citing files for every hit:
- Contradictions: two pages asserting incompatible things. Propose the reconciliation.
- Stale claims:
review_afterdates past due, and claims newer pages have quietly superseded. Propose the rewrite or the re-verification. - Orphans: pages absent from their fixed hub and unlinked by every other page. Propose the link, or the merge into a page that earns one.
- Graveyard notes: low-confidence, never-cited, no-longer-true pages. Propose deletion. Something must delete; a pruning pass that removes nothing should be rare and said with evidence, not comfort.
- Gaps: questions the vault keeps almost-answering. Propose the research run that would close them.
- Lifecycle projections: initiative state versus its hub bucket, index summary and roadmap count, baton, completion evidence, and queue status; content publication state versus index, serving roadmap, publication metrics, and voice samples; offer state and known constraints versus its customer-facing close, linked initiative, and metrics. A checked box whose evidence is absent is a contradiction; evidence that satisfies an unchecked completion condition is a stale projection.
Deliver the whole sweep as ONE short proposed diff: what changes, what gets deleted, what
gets flagged, each line with its reason. The founder approves before anything mutates;
silent maintenance of someone's memory is not maintenance, it is editing history. Then
execute the approved lines, append ## [date] lint | <summary> to log.md.
Approval is scoped to those exact lines. Anything discovered after the yes becomes a new proposed diff and waits for a new yes; it is never folded into the approved batch. Without the second approval, leave the new item untouched and flagged, then report NOT CLEAN.
Then rerun the graph from every changed node to a fixed point. Any surviving direct contradiction
ends with NOT CLEAN: <n> unresolved contradictions and their paths. It cannot be summarized as
clean or "nothing to fix."
An honestly clean vault gets a two-line "checked, nothing to fix" and no theater.
Mandatory filing gate
- Capture mode runs
scripts/graph-auditwith every touched durable file. Health mode runs it without a file list so it scans the complete durable vault. - Fix every violation covered by the approved diff, then rerun the validator.
- A remaining violation blocks queue completion and a clean declaration. Report its exact output and use a new approval diff for any repair not already authorized.
Done when: the approved diff is applied, the log row exists, and every change traces to an approved line.
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
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.

