kb-write
Skill0 starsChanged 30 days agoMITView on GitHub
Use when the student states a durable fact, correction, or decision ("my advisor is...", "the midterm moved", "I decided to drop DEMO 101"), or asks to create or update a page (course, person, project, decision, career); the read-integrate-commit loop.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- dimitar-radenkov/Pointframetheir own version, first seen Oct 20, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- dimitar-radenkov/Pointframe★ 15same 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-captureSkill
- kb-gardenSkill
- kb-ingest-sourceSkill
- kb-secretsSkill
- kb-triageSkill
- setupSkill
- whats-dueSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 1 is distinctive, and 5 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.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Gate: Read CLAUDE.local.md and confirm hostname matches it.
- Very specific: line 11
Orient: Read INDEX.md, GLOSSARY.md, and the target folder's README.md.
- Very specific: line 12
Find before creating: Search for the entity by name and aliases (GLOSSARY.md, aliases: frontmatter, grep -ril).
- Distinctive: line 14
Re-read the whole target page: before editing.
- Very specific: line 20
If this settles an open thread elsewhere, add Resolved YYYY-MM-DD → [[this/page]]: one line there in the same commit.
- Very specific: line 22
Frontmatter: Update updated: (today) and description: (≤ 120 characters, a rule-like summary) in the same edit.
≈ “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-write
AGENTS.md is canonical (§Write); this is only a thin task pointer.
- Gate. Read
CLAUDE.local.mdand confirmhostnamematches it; if missing or mismatched, stop and ask. If a remote exists and this is the session's first write,git pull --rebase; on conflict, stop. - Orient. Read
INDEX.md,GLOSSARY.md, and the target folder'sREADME.md. - Find before creating. Search for the entity by name and aliases (
GLOSSARY.md,aliases:frontmatter,grep -ril). Update the existing page when there is one. - New page only if earned: at least
NEW_PAGE_MIN_SENTENCES(seeTHRESHOLDS.md) meaningful sentences now; otherwise enrich an existing page or capture an inbox drop. Start from the matching template inschema/templates/(itsREADME.mdmaps each template to itstype:, folder and file name, e.g.course.md,decision.md,person.md,plan.md); the folder→type map is inscripts/kb-schema.json. Read the DEMO page the README names when the template alone is unclear, and never copy DEMO facts. - Re-read the whole target page before editing.
- Integrate.
- Rewrite Compiled Truth to the new current state; append a dated line to Timeline (never edit old Timeline lines).
- Facts that can rot or be acted on (deadlines, grading weights, office hours, policies, offer terms) get
[Source: who/context/YYYY-MM-DD]. Conflicting sources: record both, do not pick one silently. - Plans and explorations ("thinking about a minor", "might study abroad") go on their own silo page linked by wikilink; never phrase them as settled facts on entity pages, in
GLOSSARY.md, or indescription:. - Course pages: keep the course's AI-use and collaboration policy current and follow it. Organize the student's notes; do not produce graded work.
- If this settles an open thread elsewhere, add
**Resolved YYYY-MM-DD → [[this/page]]:** one linethere in the same commit. - New recurring names (a TA, a club, a course nickname): append a
GLOSSARY.mdentry.
- Frontmatter. Update
updated:(today) anddescription:(≤ 120 characters, a rule-like summary) in the same edit. Never editINDEX.mdby hand. - No secrets. Store password-manager pointers only (
kb-secrets). - Check.
python3 scripts/kb-lint.pyandpython3 scripts/wikilink-check.py; fix what they report. - Commit by explicit path with
<scope>: <verb> <slug>(scopes and verbs in AGENTS.md §Commit format), e.g.school: update demo-101,decisions: add 2099-09-24-choose-a-minor. The pre-commit hook rebuilds and stagesINDEX.md. Push only if the student asks orkb.autopushis on.
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.

