accountable-engineerin…
Use explicit human checkpoints for architecture, security, rollout, or operational decisions.
Build a persistent compounding wiki from raw sources using the LLM Wiki pattern
$ npx -y skills add jellydn/my-ai-tools --skill llm-wiki --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/llm-wikiContext preview
The summary Claude sees to decide when to auto-load this skill.
Build a persistent compounding wiki from raw sources using the LLM Wiki pattern
name: llm-wiki description: "Build a persistent compounding wiki from raw sources using the LLM Wiki pattern" license: MIT compatibility: cline, claude, opencode, amp, codex, gemini, cursor, pi hint: Use when building a personal knowledge base, researching a topic over time, or maintaining a structured wiki from raw documents user-invocable: true metadata: audience: all workflow: knowledge-management
Build and maintain a persistent, compounding knowledge wiki from raw sources.
Based on [Karpathy's LLM Wiki pattern](https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f): the LLM incrementally integrates each new source into a structured wiki of markdown files — updating entity pages, flagging contradictions, strengthening cross-references. Synthesis is compiled once and kept current, not re-derived on every query.
`/llm-wiki <ACTION> [ARGUMENTS]`
---
your-wiki/ ├── raw/ # Immutable source documents — you add, LLM never modifies │ └── assets/ # Downloaded images referenced by sources ├── wiki/ # LLM-generated and maintained pages │ ├── index.md # Catalog of all pages with one-line summaries │ ├── log.md # Append-only record of all operations │ ├── overview.md │ ├── entities/ # People, places, organizations │ ├── concepts/ # Ideas, topics, themes │ └── sources/ # One summary page per source └── CLAUDE.md # Schema: wiki conventions and per-operation workflows
Templates for all three layers are in `$SKILL_PATH/templates/`.
---
1. Create the directory structure: `raw/`, `wiki/`, `wiki/entities/`, `wiki/concepts/`, `wiki/sources/` 2. Copy `$SKILL_PATH/templates/schema.md` to `CLAUDE.md` (or `AGENTS.md`) 3. Create `wiki/index.md` from `$SKILL_PATH/templates/index.md` 4. Create `wiki/log.md` from `$SKILL_PATH/templates/log.md` 5. Create a starter `wiki/overview.md` stating the wiki's domain and purpose 6. Tell the user to add sources to `raw/` and run `/llm-wiki ingest <file>` next
**Done when:** all five files and directories exist and the user has been told the next step.
---
1. Read the source file; share key takeaways and ask the user what to emphasize 2. Create `wiki/sources/<slug>.md` with a structured summary 3. Update `wiki/overview.md` if the source shifts the big picture 4. Create or update entity pages in `wiki/entities/` for key people, places, organizations 5. Create or update concept pages in `wiki/concepts/` for key ideas and themes 6. Add a contradiction note on any existing page where this source conflicts with current content 7. Update `wiki/index.md` — every new or modified page must appear with a one-line summary 8. Append to `wiki/log.md`: `## [YYYY-MM-DD] ingest | <Source Title>`
**Done when:** every affected page is updated, every new or changed page appears in `index.md`, and the log entry is appended. A single ingest typically touches 5–15 pages.
---
1. Read `wiki/index.md` to identify the most relevant pages 2. Read those pages in full 3. Synthesize an answer with citations to specific wiki pages 4. If the answer is a valuable synthesis (comparison, analysis, discovered connection), offer to file it as a new wiki page; if filed, update `wiki/index.md` and append to `wiki/log.md`
**Done when:** the question is answered with citations, and any filing decision (page created or skipped) is resolved.
---
Scan the entire wiki and report on each of the following:
Suggest new questions and sources. Ask before making any fixes.
Append to `wiki/log.md`: `## [YYYY-MM-DD] lint | health check`
**Done when:** all six issue types are checked and reported, suggestions are given, and the log entry is appended.
---
Report: source count in `raw/`, wiki page count, last 10 entries in `wiki/log.md`, and any obvious health issues (orphan pages, missing index entries).
**Done when:** all four items are reported.
---
**wiki/index.md** — content catalog, updated on every ingest. Every page with a link and one-line summary, organized by category. The LLM reads this first when answering queries.
**wiki/log.md** — append-only operation log. Entry format: `## [YYYY-MM-DD] <operation> | <title>`. Grep-parseable:
grep "^## \[" wiki/log.md | tail -5 # last 5 operations grep "^## \[.*\] ingest" wiki/log.md # all ingests grep "^## \[.*\] query" wiki/log.md # all queries
---
For larger wikis, add [qmd](https://github.com/tobi/qmd) — local hybrid BM25/vector search with an MCP server:
bun install -g @tobilu/qmd qmd collection add ./wiki --name my-wiki qmd embed qmd query "how does X relate to Y" -c my-wiki
---
Portable, source-controlled configuration for AI coding assistants. my-ai-tools installs one consistent set of agent guidelines, skills, commands, hooks, MCP servers, and tool settings across supported AI coding assistants.
Use explicit human checkpoints for architecture, security, rollout, or operational decisions.
Record architecture decisions with ADRs — captures why, alternatives considered, and consequences
Use when monitoring an open GitHub PR for CI failures, review feedback, mergeability, and safe retries or fixes.
Inspect history and architecture for hidden constraints before risky cross-cutting changes.
Build an interactive report or experiment when the user asks to explore model capabilities.
Audit a diff for structural maintainability and unnecessary complexity.