kb-management
Skill2 starsChanged 26 days agoApache-2.0View on GitHub
Maintaining the story knowledge base: creating, updating, and organizing wiki-style reference pages in kb/. Use when capturing finalized story knowledge, updating character profiles, documenting world mechanics, or restructuring the kb.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Abdullokh-N/proza-rutheir own version, first seen Aug 27, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Abdullokh-N/proza-ru★ 0same 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 repository33 other files it gives its agents.
- character-simSkill
- cold-readSkill
- creative-researchSkill
- creative-writing-craftSkill
- creative-writing-modesSkill
- creative-writing-museSkill
- demolitionSkill
- exportSkill
- gatesSkill
- grill-with-docsSkill
- information-hierarchySkill
- intent-modelingSkill
- kb-integritySkill
- knowledge-layersSkill
- llm-writingSkill
- md-validationSkill
- project-setupSkill
- qi-layerSkill
- reader-simSkill
- reflectSkill
- series-bibleSkill
- seriesSkill
- shared-daoSkill
- story-ledgersSkill
- story-memorySkill
- story-planningSkill
- story-reviewSkill
- structured-artifactSkill
- style-guardrailsSkill
- voiceSkill
- writing-principlesSkill
- writing-staffingSkill
- zoom-outSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 35
Series scope (optional): when the book is linked to a series library, the kb is still the book's memory — but series canon lives in the …
- Distinctive: line 49
When a doc covers two unrelated topics, split it.
- Distinctive: line 88
Write pages that work in isolation:
- Distinctive: line 94
Current: update when the story invalidates or extends what's here
- Distinctive: line 98
Use vocab pages when terms matter across agents: magic names, faction labels, place names, titles, relationship labels, invented words, …
- Distinctive: line 122
Split: when a page grows past ~200 lines or covers multiple unrelated concepts.
- Very specific: line 131
Use /story-memory for routine fact extraction from completed chapters.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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 Management
The knowledge base (kb/) is the project's durable memory. Every agent reads
from it for context. This skill covers how to maintain it well.
Layers
Canon: established facts the story has committed to. Once a chapter is published/finalized, the facts it establishes are canon. Contradicting canon breaks reader trust.
Wiki: synthesized reference pages. How the magic system works, character relationships, faction politics. Living documents that evolve as the story develops.
Styles: voice reference files derived from prose samples. The writer and critic agents depend on these for voice consistency.
Vocab: canonical story terms, aliases, and exclusions. Project-wide terms
live in kb/vocab.md; domain terms live beside the domain they govern, such as
kb/world/vocab.md.
Issues: tracked writing problems that span multiple chapters (recurring tics, pacing patterns, continuity errors). See the story-memory skill.
Series scope (optional): when the book is linked to a series library,
the kb is still the book's memory — but series canon lives in the
library's series/bible.json and is written only by the engine. Never
hand-edit bible state, never add a canon: mirror to a kb page; a joined
entity page carries only the opt-in series-id: frontmatter key, and
editing that page deliberately makes its series exemptions stale
(re-firing their findings) so the change is re-reviewed. See
/series-bible for the schema and /series for the command surface.
Page Conventions
One Concept Per Document
Each doc covers one coherent topic: one character, one location, one system. When a doc covers two unrelated topics, split it. When two docs explain the same thing from different angles, merge or cross-reference.
Name files by what they describe (fire-magic.md, protagonist.md), not
when they were written (session-3-notes.md).
Organization
kb/
characters/
<name>.md # one file per character
vocab.md # project-wide canonical terms
world/
vocab.md # worldbuilding terms when needed
<topic>.md # locations, factions, systems
<domain>/
vocab.md # subdomain terms when needed
<topic>.md # nest when a domain has many pages
timeline/
<arc-or-period>.md # chronological entries
canon/
<chapter-or-arc>.md # hard facts per chapter/arc
styles/
<style-name>.md # voice reference files
issues/
<issue-name>.md # tracked writing problemsThe project's CLAUDE.md may customize this. Read it first.
Linking
Link to related pages with relative paths. Cross-reference instead of duplicating: one source of truth per concept. A character page links to the location page for their home, the timeline entry for their arc, etc.
Readability
Write pages that work in isolation:
- Self-contained: enough context that a reader doesn't need three other pages first
- Scannable: headers, bullets, tables. Bold key terms on first use.
- Concrete: specific quotes, chapter references, scene citations
- Current: update when the story invalidates or extends what's here
Vocab Pages
Use vocab pages when terms matter across agents: magic names, faction labels, place names, titles, relationship labels, invented words, recurring in-world phrases, and genre terms with project-specific meanings.
Each entry should include:
- Canonical name: the form agents should use
- Definition: one to three sentences, including what the term is not when ambiguity is likely
- Aliases: names the author, characters, drafts, or older kb pages actually use
- Source: where the usage was established or decided
Resolve conflicts early. If two terms seem to name the same thing, pick the canonical form with the author or flag it in the report instead of carrying both forward silently.
When to Create vs Update
Create a new page when a concept is finalized enough to be referenced by other agents. Don't create pages for things still in story-planning.
Update an existing page when new chapters establish facts about it, when the author makes decisions that change it, or when a page has become stale.
Split when a page grows past ~200 lines or covers multiple unrelated concepts.
What Belongs in KB vs Work
- Finalized knowledge →
kb/ - Draft iterations, brainstorm captures, critique reports →
work/ - Promoted facts after a draft completes →
kb/canon/or relevant wiki page
Use /story-memory for routine fact extraction from completed chapters.
Direct kb edits are for the author or muse when capturing decisions
interactively.
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.

