kblisted
Install: claude install-skill vadbosh/kb
# kb
A Markdown knowledge base per work stream: one `00-overview.md` acting as a map,
plus numbered topic files. The index table is **generated** from each file's
front matter, so it cannot drift from the files it describes.
## Which branch do you need
| The user wants | Read |
|---|---|
| to load the notes, orient, see what changed — "kbrestore", "прочитай kb", start of a session | `references/restore.md` |
| to write down what was learned — "kbsave", "запиши в kb", end of a task | `references/save.md` |
| **one named command** — `/kb check`, `/kb status`, `/kb brief`, `/kb list`, `/kb verify`, `/kb outline`, `/kb sync`, `/kb streams`, `/kb route`, `/kb local` | neither; see below |
| a `⚠` line about the entry point, from any command that printed one | `references/entry-point.md`, in addition |
Read only the one that applies. Everything each half needs beyond this page is
in that file — the kinds, the writing rules, the briefing format.
**Saving has one rule that holds even if that file never loads: never conclude
there is nothing to save without looking on disk first.** "Nothing new",
"nothing changed since last time", "already saved above" are the same judgement
made from memory, and memory does not know that a note was deleted an hour ago.
A stream with no `kb/` and a session that did work has nothing written down
anywhere — that is the opposite of nothing to save. Looking means `ls` in that
stream's own directory, not a search of the filesystem: a note outside its