wiki-builder
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.
Profile →npx skills add rohitg00/pro-workflow --skill wiki-builder --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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
What does the wiki-builder skill do?
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.
How do I install it?
Run `npx skills add rohitg00/pro-workflow --skill wiki-builder --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From rohitg00/pro-workflow, a repository with 2,760 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.