Claude Code Skill

Knowledge that compounds,
doesn't disappear

Turn Claude into a wiki maintainer for your projects. Instead of losing insights in chat history, build a structured knowledge base that grows with every document you add and every question you ask.

View on GitHub Install now
The Problem

What happens to all that knowledge?

Every conversation with Claude produces valuable insights. Summaries, decisions, analyses, connections between ideas. But when the chat ends, it all vanishes. Next time, you start from zero.

Without wiki-skill

You ask Claude about your project. It reads your files, gives a great answer, and the conversation closes. Tomorrow you ask a related question — Claude has to re-discover everything. Nothing accumulates. Every session starts from scratch.

With wiki-skill

Claude builds a structured wiki inside your project. Every document, decision, and insight gets filed, cross-referenced, and maintained. Tomorrow, Claude reads the wiki first — it already knows the context. Knowledge compounds over time.

How It Works

Three layers, one command to start

The wiki sits between you and your raw documents. Claude reads, synthesizes, and maintains everything. You curate and explore.

1

Install & initialize

Add the skill to Claude Code and type /wiki init. Claude scans your project, auto-detects the project type (research, reading, business, etc.), creates the wiki structure, and configures everything. No setup questions unless truly needed.

2

Feed it documents

Drop files into raw/inbox/ or paste content directly, then type /wiki ingest. Claude reads each document, writes a summary page, identifies entities and concepts, creates cross-references, and flags contradictions with existing knowledge.

3

Query & maintain

Ask questions with /wiki query — Claude answers from the wiki with citations, and you can save good answers as new wiki pages. Run /wiki update to sync the wiki with your latest work, or /wiki lint to catch gaps and contradictions.

Commands

Five commands, everything you need

Type these in any Claude Code session. The wiki does the rest.

/wiki init

Initialize

Auto-detects your project and creates the wiki structure. Configures CLAUDE.md so every future session knows about the wiki.

/wiki ingest

Add knowledge

Processes documents into structured wiki pages. Summaries, entities, concepts, and cross-references — all created automatically.

/wiki query

Ask questions

Search your knowledge base. Claude reads relevant pages and synthesizes answers with citations. Save good answers as wiki pages.

/wiki lint

Health check

Find orphan pages, missing cross-references, contradictions between sources, stale content, and knowledge gaps.

/wiki update

Stay in sync

Checks your recent git commits, file changes, and decisions against the wiki. Updates what's fallen out of date.

Domains

Works for any kind of project

The skill ships with templates for four project types, auto-detected from your file structure.

🔬

Research

Papers, datasets, experiments, findings. Track your evolving thesis across sources.

📚

Reading

Books, chapters, characters, themes. Build a companion wiki as you read.

💼

Business

Meetings, decisions, requirements, stakeholders. A living project record.

🌱

Personal

Goals, journals, habits, reflections. A structured picture of your growth.

Installation

Up and running in 30 seconds

Choose whichever method works for you. Full install includes domain templates and extended documentation.

Full install (recommended)
git clone https://github.com/bellins14/wiki-skill ~/.claude/skills/wiki
Minimal install (just the skill file)
mkdir -p ~/.claude/skills/wiki
curl -sSL https://raw.githubusercontent.com/bellins14/wiki-skill/main/SKILL.md \
  -o ~/.claude/skills/wiki/SKILL.md
Or simply tell Claude Code
# In a Claude Code session, say:
"Install the wiki skill from github.com/bellins14/wiki-skill"

Then open a project and type /wiki init to get started.

Credits

Standing on the right shoulders

🧠

This skill is a direct implementation of the LLM Wiki pattern by Andrej Karpathy. The core insight — that LLMs should maintain a persistent knowledge base instead of rebuilding context from scratch every time — comes from his work. Read the original document: LLM Wiki — Karpathy's Gist.