Mmcp.market

wiki-builder skill

by rohitg00·rohitg00/pro-workflow·2.9k stars

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.

A100/100content scan

Is the wiki-builder skill safe?

Clean: nothing in its files matched our rules. We read 14 files in the folder on 2026-09-28.

No findings.

Install the wiki-builder skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description. 

git clone --depth 1 https://github.com/rohitg00/pro-workflow.git /tmp/pro-workflow
mkdir -p ~/.claude/skills
cp -r /tmp/pro-workflow/skills/wiki-builder ~/.claude/skills/wiki-builder
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

Wiki Builder

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

When to use

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

Locations

  • Global: ~/.pro-workflow/wikis// — default, never committed
  • Project: /.claude/wikis// — pass --scope project, committable

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

Flavors

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:

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.

More skills from rohitg00/pro-workflow

  • Aagent-teamsCoordinate multiple Claude Code sessions as a team — lead + teammates with shared task lists, mailbox messaging, and file-lock claiming. Patterns for team sizing, task decomposition, and when to use teams vs sub-agents vs worktrees.
  • Aauto-setupAuto-configure quality gates, hooks, and settings for a new project. Detects project type and sets up appropriate tooling. Use when onboarding a new codebase.
  • Abatch-orchestrationDecompose large-scale changes into independent units and spawn parallel agents in isolated worktrees. Use for migrations, refactors, codemods, and any change touching 10+ files with the same pattern.
  • Cbug-captureCapture a user-reported defect as a durable GitHub issue written in the project's own domain language. Explores the codebase in parallel for context but never leaks file paths or line numbers into the issue. Use when the user reports a bug conversationally, runs a QA pass, or says "file an issue", "log this as a bug", "capture this".
  • Acompact-guardSmart context compaction with state preservation. Saves critical files, task progress, and working state before compaction, restores after. Use before manual compact or when auto-compact triggers.
  • Acontext-engineeringMaster the four operations of context engineering — Write, Select, Compress, Isolate. Manage token budgets, compaction strategies, and context partitioning to keep AI sessions sharp and efficient.
  • Acontext-optimizerOptimize token usage and context management. Use when sessions feel slow, context is degraded, or you're running out of budget.
  • Acost-trackerTrack session costs, set budget alerts, and optimize token spend. Use to check costs mid-session or set spending limits.
  • Adesign-engineeringApply interface craft when building or reviewing UI - motion, easing, timing, springs, component feel, and visual foundations. Use when building a component, animation, transition, hover or press state, modal, drawer, toast, or when polishing an interface so it feels right. Says "make this feel better", "add an animation", "polish the UI", "review this component".
  • AdeslopRemove AI-generated code slop, unnecessary comments, and over-engineering from the current branch diff. Cleans up boilerplate, simplifies abstractions, strips defensive code, and in skill-file mode lints SKILL.md files for quality. Use when cleaning up code, simplifying, removing boilerplate, before committing, or when reviewing a skill before promoting it.
  • Adomain-modelingBuild the project's shared language and bounded contexts before writing code, so names stay consistent and the agent stops paraphrasing domain concepts. Produces a CONTEXT.md glossary and decision records. Use at the start of a project or feature, or when the codebase and the people describing it speak different languages.
  • Afile-watcherConfigure file watching hooks to auto-react to config changes, env file updates, and dependency modifications. Use to set up reactive workflows.

All agent skills → · MCP servers