kb-capture
Skill0 starsChanged 31 days agoMITView on GitHub
Use when the student says "put/save/add this in the KB", "remember this", "note this down", or dictates a quick thought, link, or deadline to keep; makes a verbatim inbox/ drop via scripts/kbdrop.sh.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- pfeff/claude-skillstheir own version, first seen Nov 1, 2026
- paslavskyi/llm-wikitheir own version, first seen Oct 15, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- pfeff/claude-skills★ 3same name
- paslavskyi/llm-wiki★ 1same name
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.
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- course-setupSkill
- exam-prepSkill
- kb-gardenSkill
- kb-ingest-sourceSkill
- kb-secretsSkill
- kb-triageSkill
- kb-writeSkill
- setupSkill
- whats-dueSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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 10
If the student names a sibling KB (a club, lab or startup KB listed in CLAUDE.local.md), capture there instead, using that repo's own …
- Very specific: line 11
If the content was already analyzed in this conversation and has a clear destination page, write that page with kb-write instead of hiding …
- Distinctive: line 19
Do not classify, fetch, dedupe, schedule or ask follow-ups at capture time unless the student asked for immediate action ("and remind me", …
- Very specific: line 20
Never put a secret value in a drop.
- Very specific: line 21
Check the result: the script prints the new file path and commits inbox: add <timestamp-slug>.
≈ “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.
Files
kb-capture
AGENTS.md is canonical (§Capture); this is only a thin task pointer. This is the fast path: do not read INDEX.md, GLOSSARY.md, folder READMEs or existing pages.
- If the student names a sibling KB (a club, lab or startup KB listed in
CLAUDE.local.md), capture there instead, using that repo's own capture path. Unqualified "KB" means this repo. - If the content was already analyzed in this conversation and has a clear destination page, write that page with
kb-writeinstead of hiding finished work in the inbox. - Otherwise capture verbatim, preserving the student's wording and any source (URL, sender, course):
Pass multi-line or quote-heavy text through stdin so the shell does not mangle it.scripts/kbdrop.sh "<text or url>" # multi-line: printf '%s\n' "<text>" | scripts/kbdrop.sh - - Do not classify, fetch, dedupe, schedule or ask follow-ups at capture time unless the student asked for immediate action ("and remind me", "add it to DEMO 101's page now").
- Never put a secret value in a drop. If the text contains a password, token or recovery code, stop and point to
kb-secrets. - Check the result: the script prints the new file path and commits
inbox: add <timestamp-slug>. Confirm withgit log -1 --oneline. Pushing happens only ifkb.autopushis on; otherwise do not push unless asked. - Reply in one line: the drop's path, and that triage (
kb-triage) will file it.
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.

