Skip to main content
skill CX Codex

wiki-builder — Claude Code skill: build a searchable research wiki

wiki-builder is a Claude Code skill that creates a structured knowledge base from Markdown pages and an FTS5 index in SQLite. It persists between sessions and is queryable by the agent.

MIT ★ 2,966 updated 2026-09-29

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add rohitg00/pro-workflow
/plugin install pro-workflow@pro-workflow
Open on GitHub

What wiki-builder does

wiki-builder organizes research in one place. Tell it to start a wiki on machine learning or add a paper to your project wiki — it creates a folder with raw/ (source material), wiki/ (processed pages), and derived/ (summaries or charts). Each page is linked to its source in sources.md.

Pick a wiki flavor to match your goal: research for open-ended exploration, paper for deep reading of a single work, product for tool documentation, person for a researcher profile, codebase for code navigation. The skill keeps an index in SQLite, so your next session the agent recalls what was in the wiki and can answer questions about it.

Wikis live in ~/.pro-workflow/wikis/ by default, but you can bind one to your project (use --scope project), and it goes into .claude/wikis/ — then you can commit it. All changes get logged in logs/maintenance-log.md.

What it helps with

  • organize research material on a single topic and retrieve it across sessions
  • structure papers, notes and links around one area of study
  • extract key insights from raw sources and build a navigable KB
  • tie claims to their sources and keep the reasoning chain intact

Example prompts for the agent

  • Start a research wiki on LLM architecture and add three papers to it
  • Add this PDF to the optimization wiki and write a concept page summarizing the method
  • What does the project wiki contain? Who and which companies are mentioned in it?

How to install wiki-builder

1Plugin marketplace

/plugin marketplace add rohitg00/pro-workflow
/plugin install pro-workflow@pro-workflow

This installs the whole pro-workflow plugin with all its skills

2Skills CLI (Vercel)

npx skills add rohitg00/pro-workflow --skill wiki-builder -a claude-code

3Manually: put the files in place

~/.claude/skills/wiki-builder/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/wiki-builder/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about wiki-builder

How do I install wiki-builder in Claude Code?

Run these commands in order: /plugin marketplace add rohitg00/pro-workflow, then /plugin install pro-workflow@pro-workflow, then npx skills add rohitg00/pro-workflow --skill wiki-builder -a claude-code. After that, open ~/.claude/skills/wiki-builder/SKILL.md.

What does wiki-builder do?

It creates a folder structure for source material, processed pages, and artifacts. It indexes everything in SQLite so the agent can search and answer questions about your wiki across sessions. Every page links to its source.

Can I store a wiki in my project instead of a global folder?

Yes. Use the --scope project flag when creating it. The wiki will live in .claude/wikis/ instead of ~/.pro-workflow/wikis/ and you can commit it to version control.

Source text

SKILL.md · MIT
---
name: wiki-builder
description: Start, structure, and grow a persistent research wiki indexed in pro-workflow's SQLite knowledge base. Each wiki is a folder of markdown pages with provenance, plus a shadow FTS5 index so any session can recall it. Use when the user says "start a wiki", "add to wiki", "compile a page", "wiki on X", or wants a long-lived knowledge base on a topic, paper, product, person, project, or codebase.
user-invocable: true
---

# Wiki Builder

Persistent knowledge base for any topic. Markdown on disk + SQLite FTS5 shadow index.

## When to use

- "Start a wiki on <topic>"
- "Add this paper / link / note to the <slug> wiki"
- "Compile a concept page on X in <slug>"
- "What does the <slug> wiki say about Y?" (delegates to wiki-query)
- "List my wikis"

## Locations

- **Global**: `~/.pro-workflow/wikis/<slug>/` — default, never committed
- **Project**: `<project>/.claude/wikis/<slug>/` — pass `--scope project`, committable

Both register in the same `~/.pro-workflow/data.db`.

## Flavors

| Flavor | Use for |
|--------|---------|
| `research` | ongoing topic exploration |
| `paper` | one-paper deep dive |
| `domain` | broad subject area |
| `product` | product/tool KB |
| `person` | researcher/founder dossier |
| `organization` | company/lab profile |
| `project` | internal project KB |
| `codebase` | symbol/file-aware KB tied to a repo |
| `incident` | post-mortem KB |

## Layout

```
<slug>/
├── wiki.config.md         # purpose, audience, page types, style, auto_research block
├── raw/                   # untouched source material (PDFs, scrapes, transcripts)
├── wiki/
│   └── index.md           # entry point, hand-curated TOC
├── derived/               # generated artifacts (surveys, charts, summaries)
├── prompts/               # per-task prompts (compile-page, lint, query)
├── logs/maintenance-log.md
└── sources.md             # one row per source: id | url | title | hash | fetched_at
```

Flavor adds folders: `wiki/papers`, `wiki/concepts`, `wiki/people`, `wiki/products`, `wiki/timelines`, `wiki/questions`.

## CLI surface

```
node $SKILL_ROOT/scripts/wiki-cli.js init <slug> --title "X" --flavor research [--scope project] [--root <path>]
node $SKILL_ROOT/scripts/wiki-cli.js list
node $SKILL_ROOT/scripts/wiki-cli.js page <slug> <rel-path> --title "X" [--type concept|paper|person|...] [--from-file path]
node $SKILL_ROOT/scripts/wiki-cli.js reindex <slug>
node $SKILL_ROOT/scripts/wiki-cli.js info <slug>
```

`init` runs `init_wiki.sh` (mirrors dair layout) AND registers the wiki in SQLite. `page` writes markdown + upserts FTS row.

## Workflow when invoked

1. Resolve action (init / ingest / compile / list / reindex / info).
2. Read `wiki.config.md` of the target wiki before any compile.
3. Every claim that lands in `wiki/` must cite a row in `sources.md` (one citation = one source row).
4. After page write, call `wiki-cli.js page` so FTS index stays in sync.
5. Append a one-line entry to `logs/maintenance-log.md` per change.
6. Update `wiki/index.md` if new top-level page.

## Quality bar

- First page useful immediately, not stub.
- Stable slug filenames (`tool-use-benchmarks.md`, not `2026-05-08-notes.md`).
- Separate raw source from compiled interpretation.
- Cross-link related pages in same wiki via relative links.
- Mark speculation with `> SPECULATION:` block.
- No duplicate summaries — link existing page instead.
- Generated pages stay navigable for future agents.

## Privacy

Wikis with `private: true` in config never get fetched from web sources by `wiki-research-loop`. Local raw/ only.

## Auto-research opt-in

Phase 3.3.0 ships builder + query only. Loop arrives in 3.3.1. To prep, `wiki.config.md` may include:

```yaml
auto_research:
  enabled: false        # flip in 3.3.1
  max_pages_per_run: 5
  max_depth: 3
  budget_usd: 0.50
  fetchers: [web, arxiv, github]
```

## Templates

See `templates/` for `wiki.config.md`, `index.md`, prompt files. `init_wiki.sh` copies these into the new wiki root.

© Rohit Ghumare · MIT · rohitg00/pro-workflow

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set83

The whole set →
plan-interrogate The plan-interrogate skill probes a plan before implementation by mapping its decisions and asking about them one at a time. Use it to clarify unresolved design choices. CX Codex +1 ★ 2,966repo stars bug-capture bug-capture is a Claude Code skill that turns reported defects into GitHub issues using the project’s own terms. It activates after a conversational bug report, a QA pass, or a request to file an issue. CX Codex +1 ★ 2,966repo stars context-optimizer context-optimizer controls token consumption and frees context in Claude Code. Use it when agent sessions slow down, forget instructions, or approach budget limits. CX Codex +1 ★ 2,966repo stars deslop deslop trims unnecessary code from the current branch diff and checks SKILL.md files. Run it before committing or reviewing a skill for release. CX Codex +1 ★ 2,966repo stars token-efficiency token-efficiency cuts conversational fluff, caps tool executions per task, and stops Claude Code from repeatedly editing working implementations. CX Codex +1 ★ 2,966repo stars wiki wiki is a Claude Code command that builds and maintains persistent research wikis. It stores markdown files, indexes them in SQLite FTS5, and retrieves context via BM25. CX Codex +1 ★ 2,966repo stars wiki-viewer wiki-viewer writes a pro-workflow wiki out as a single HTML file with pages, sources, claims, a seed queue, a link graph and search. Useful for handing research state to someone else. CX Codex +1 ★ 2,966repo stars llm-council llm-council runs multi-model deliberation in three stages: parallel drafts, anonymous peer rankings, and final synthesis by a designated chairman. CX Codex +1 ★ 2,966repo stars

Project sponsors

Companies that keep this analytics open