Build and Maintain Structured Research Wikis

A skill for creating and maintaining configurable research wikis (dair-ai/dair-academy-plugins, MIT), where each wiki is a standalone folder with its own sources, compiled pages, derived artifacts, prompts, and local configuration. Wikis default to ~/dair-wikis/<wiki-slug>, overridable via WIKI_ROOT or --root, using lowercase kebab-case slugs. New wikis start from a fixed layout: wiki.config.md, raw/, wiki/index.md, derived/, five bundled prompts/*.md files for compiling index, source, and concept pages, querying-and-filing, and linting, a logs/maintenance-log.md, and sources.md, with common additional folders like wiki/papers, wiki/concepts, wiki/people, or wiki/timelines added only when the wiki's config needs them. New wikis are scaffolded via a bundled init_wiki.sh script:

bash "${CLAUDE_PLUGIN_ROOT}/skills/wiki-builder/scripts/init_wiki.sh" <slug> --title "Readable Title" --flavor research

with seven supported flavors - research, paper, domain, product, person, organization, project, with research as the default when unsure - followed by a five-step setup: edit wiki.config.md to the user's real goal, place source material in raw/, record provenance in sources.md, generate pages under wiki/, and log major maintenance actions. Its five-step operating workflow resolves whether the task is to start, ingest, compile, query, restructure, lint, or export a wiki; reads the wiki's own local config, wiki.config.md, sources.md, and custom prompts/, before touching anything, since local config always beats generic defaults; preserves provenance by never converting loose claims into wiki facts without a source, with sources.md entries requiring at minimum a title, source path or URL, date added, and a short contribution note; compiles durable wiki pages with a concise overview, source-grounded key points, related-page links, open questions, and update notes rather than one-off summaries; and maintains the wiki by updating wiki/index.md, relevant maps, and the maintenance log whenever many pages change, updating wiki.config.md first if the wiki's purpose or structure itself changes. A companion references/wiki-flavors.md gives suggested page types per flavor. Its quality bar requires the first page to be useful immediately, explicit filenames and stable slugs, raw source material kept separate from compiled interpretation, related pages linked, speculation and unknowns clearly marked, and no duplicate rewriting of the same source summary across pages.

Use it when the user asks to start a new wiki or knowledge base, create a wiki for research notes, papers, products, people, organizations, domains, projects, or events, ingest source material into an existing wiki, generate wiki pages such as source, concept, map, timeline, brief, or index pages, query a wiki and file the answer back in, refactor or evolve a wiki's structure, or maintain provenance and update logs. The skill is intentionally general - it explicitly warns not to hard-code every wiki into an AI-papers-specific structure, and to treat each wiki's own wiki.config.md as the source of truth for purpose, audience, page types, style rules, and update workflow rather than generic defaults.

Input is a request to start, ingest into, compile, query, or restructure a wiki, plus source material such as papers, web pages, transcripts, notes, or repository files. Output is a scaffolded or updated wiki folder under ${WIKI_ROOT:-$HOME/dair-wikis}/<wiki-slug> with compiled, source-linked pages, an updated sources.md, and a maintenance log entry.

Built around a bundled init_wiki.sh scaffolding script and five bundled compilation, query, and lint prompt templates, plus a references/wiki-flavors.md reference for choosing page structures per wiki type; resolves its own install path via CLAUDE_PLUGIN_ROOT.

Researchers and coding agents maintaining a durable, provenance-tracked knowledge base for papers, products, people, or domains that needs to stay navigable for future agents and humans, not a pile of one-off summaries.