kb-recap
Skill1 starsChanged 33 days agoMITView on GitHub
Use on request to summarize what changed in the knowledge base over a time range or area ("what did we do today", "what changed about users") — a read-only narrative from git history. Saves nothing.
In this repository11 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- kb-captureSkill
- kb-dashboardSkill
- kb-elicitSkill
- kb-evolveSkill
- kb-goalSkill
- kb-orientSkill
- kb-planSkill
- kb-recallSkill
- kb-sanitizeSkill
- kb-visualizeSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Run node tools/session-delta.mjs with those flags → facts (added / updated / deleted notes under knowledge/, optionally area-filtered).
- Distinctive: line 20
Write the narrative: what was added, changed, deprecated, and any new open questions in that range.
- Distinctive: line 24
If the range is empty: "No changes in that period."
- Distinctive: line 27
Read-only. Never write notes, never commit, never create a journal file.
≈ “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.
Files
kb-recap — optional, read-only history recap
Goal: answer a user's question about recent changes with a narrative built from git facts. Persistence is automatic and separate — recap never saves anything.
Steps
- Parse the requested range from the user:
- time: "today" / "this week" →
--since "<date>" - area: "about users" / a domain →
--area <folder> - "since last commit" →
--ref <ref>
- time: "today" / "this week" →
- Run
node tools/session-delta.mjswith those flags → facts (added / updated / deleted notes under knowledge/, optionally area-filtered). - For richer narrative, you MAY read a few of the changed notes' summaries via
kb-recall(index-first) — do not read the whole tree. - Write the narrative: what was added, changed, deprecated, and any new open
questions in that range.
debug: include ids.autonomous: plain language, no ids/mechanics.
- If the range is empty: "No changes in that period."
Rules
- Read-only. Never write notes, never commit, never create a journal file.
- Index-first if you open anything; never read the whole knowledge tree.
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.

