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.
What this skill does
# 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.
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.