llm-wiki
Build a persistent compounding wiki from raw sources using the LLM Wiki pattern
Skill by jellydn
Chalk Labs
Need help deploying llm-wiki?
Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/jellydn-llm-wiki
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: ml
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md and code. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/llm-wiki
What's inside
- Skill 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
- Metadata
- audience: all · workflow: knowledge-management
- Instructions
- 141 lines in SKILL.md · view on GitHub
Files (4)
- SKILL.md
- index.md · templates/
- log.md · templates/
- schema.md · templates/
SKILL.md (first lines)
# LLM Wiki 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. ## Usage `/llm-wiki <ACTION> [ARGUMENTS]` ## Actions - **init [DIRECTORY]** - Initialize a new wiki (default: `wiki/`) - **ingest <SOURCE>** - Process a source file and integrate it into the wiki - **query <QUESTION>** - Answer a question using the wiki as the knowledge base - **lint** - Health-check the wiki for contradictions, orphan pages, and stale content - **status** - Show a summary of the wiki's current state --- ## Architecture ``` 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/`. --- ## For "init [DIRECTORY]": 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. --- ## For "ingest <SOURCE>": 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. --- ## For "query <QUESTION>": 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. --- ## For "lint": Scan the entire wiki and report on each of the following: - **Contradictions** — conflicting claims across pages - **Stale content** — pages superseded by newer ingested material - **Orphan pages** — pages with no inbound links - **Missing pages** — concepts mentioned on multiple pages but lacking their own page - **Broken links** — `[[Page Name]]` links pointing to non-existent pages - **Data gaps** — areas a targeted source or web search could fill 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. --- ## For "status": 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. --- ## Index and log **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: ```bash grep "^## \[" wiki/log.md | tail -5 # last 5 operations grep "^## \[.*\] ingest" wiki/log.md # all ingests grep "^## \[.*\] query" wiki/log.md # all queries ``` ---
From jellydn/my-ai-tools, MIT.
More from jellydn/my-ai-tools
- 0.722score
babysit-pr
jellydn
Use when monitoring an open GitHub PR for CI failures, review feedback, mergeability, and safe retries or fixes.
SkillAFreshness: A★ 123Claude Code +9 - 0.722score
visual-pr
jellydn
Posts a concise visual outline as a GitHub pull request comment.
SkillAFreshness: A★ 123Claude Code +9 - 0.716score
codemap
jellydn
Create a seven-document architecture map when the user asks to map a codebase.
SkillAFreshness: A★ 123Claude Code +9 - 0.716score
draft-pull-request
jellydn
Draft pull requests with structured descriptions using gh CLI
SkillAFreshness: A★ 123Claude Code +9 - 0.714score
diagnosing-bugs
jellydn
Build a tight, red-capable feedback loop before diagnosing failures, then minimize, test ranked hypotheses, and lock the fix with a regression test.
SkillAFreshness: A★ 123Claude Code +9 - 0.713score
pr-review
jellydn
Fix PR review comments by implementing requested changes
SkillAFreshness: A★ 123Claude Code +9 - 0.711score
code-review
jellydn
Review a branch, PR, or worktree diff for repository conventions and stated intent.
SkillAFreshness: A★ 123Claude Code +9 - 0.711score
pr
jellydn
Write a fast-to-review pull request body with a visual summary, before/after evidence, and merge-risk analysis.
SkillAFreshness: A★ 123Claude Code +9 - 0.711score
implementation-logger
jellydn
Log implementation decisions — tracks deviations from plan and captures rationale
SkillAFreshness: A★ 123Claude Code +9 - 0.711score
plannotator-setup-goal
jellydn
Turn ideas into executable goal packages with guided interviews and codebase analysis
SkillAFreshness: A★ 123Claude Code +9 - 0.711score
blindspot-pass
jellydn
Inspect history and architecture for hidden constraints before risky cross-cutting changes.
SkillAFreshness: A★ 123Claude Code +9 - 0.711score
implement-spec
jellydn
Implement a complete spec from its ticket graph, using isolated workers and one integration branch.
SkillAFreshness: A★ 123Claude Code +9
Signals
- Stars
- 123
- Forks
- 12
- Open issues
- 3
- Last commit (this folder)
- Aug 14, 2026 (2 months ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- Repository
- github.com/jellydn/my-ai-tools
- Website
- ai-tools.itman.fyi/
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
Same skill elsewhere
Copies of this SKILL.md published by others; search shows only one of them.
More from jellydn
- 0.722score
babysit-pr
jellydn
Use when monitoring an open GitHub PR for CI failures, review feedback, mergeability, and safe retries or fixes.
SkillAFreshness: A★ 123Claude Code +9 - 0.722score
visual-pr
jellydn
Posts a concise visual outline as a GitHub pull request comment.
SkillAFreshness: A★ 123Claude Code +9 - 0.716score
draft-pull-request
jellydn
Draft pull requests with structured descriptions using gh CLI
SkillAFreshness: A★ 123Claude Code +9 - 0.716score
codemap
jellydn
Create a seven-document architecture map when the user asks to map a codebase.
SkillAFreshness: A★ 123Claude Code +9 - 0.714score
diagnosing-bugs
jellydn
Build a tight, red-capable feedback loop before diagnosing failures, then minimize, test ranked hypotheses, and lock the fix with a regression test.
SkillAFreshness: A★ 123Claude Code +9 - 0.713score
pr-review
jellydn
Fix PR review comments by implementing requested changes
SkillAFreshness: A★ 123Claude Code +9
Done for you
Rather not set it up yourself?
Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.
See how we build AI agents →Read the case studies
Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.
- launches shipped
- 50+
- launches shipped
- media placements
- 500+
- media placements
- founders on every account
- 2
- founders on every account
Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block
Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.
Get llm-wiki running in your business
Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.
Cite this page
llm-wiki skill. Agent Mart. https://agentmart.dev/skills/jellydn-llm-wiki (last updated 2026-10-24)