Scaffold a new LLM-maintained markdown wiki — ask what it is about, then write CLAUDE.md, the wiki skeleton, and the first commit. Use when the user asks to start, bootstrap, or set up a new wiki or knowledge base.
Create one wiki in its own repo. Two layers and a contract, nothing else:
raw/ holds immutable sources, wiki/ is yours to maintain, CLAUDE.md says
how.
That is the whole interview. Do not offer options nobody asked for.
raw/ and wiki/{sources,entities,concepts,comparisons,synthesis,questions},
each with a .gitkeep. Add any extra page types the user chose.CLAUDE.md from references/templates/CLAUDE.md.tmpl: fill in the
name and subject line, fill or delete the Code section, keep the page
types chosen, delete the guidance angle-brackets. Remove the optional
Lint section unless a reviewed lint script actually exists.index.md.tmpl, log.md.tmpl, overview.md.tmpl, and
contradictions.md.tmpl from references/templates/ into wiki/, without
the .tmpl suffix. Fill dates, remove instructional placeholders, and
record the bootstrap in log.md. Keep an empty wiki's overview explicitly
unsupported; do not invent findings..gitignore entries for .DS_Store, .obsidian/workspace*,
.env, .env.*, !.env.example, *.key, and *.pem. Never replace an
existing ignore file.git status and the staged
diff, then stage only the files created or changed by this bootstrap using
explicit paths. Never use git add ., git add -A, or git commit -a.
If unrelated changes are already staged, leave them intact and ask before
committing. Check the diff for secrets, then commit: kb: bootstrap <name>.
If Git identity or permissions prevent a commit, leave the scaffold and
report the unfinished commit; do not change global Git settings.raw/
and run /kb-ingest.b1cf2db
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.