maria/setup-llm-wiki
Bootstrap a new LLM-maintained wiki at a chosen folder, following the llm-wiki.md pattern (a three-layer memex - raw sources, LLM-generated wiki pages, and a CLAUDE.md or AGENTS.md schema that tells the LLM how to ingest and maintain the wiki). Creates the directory layout, writes a tailored schema file, plus index.md and log.md with a bootstrap entry. Use this skill when the user asks to "set up an llm-wiki", "create an LLM wiki", "bootstrap a wiki", "instantiate the llm-wiki pattern", or invokes /setup-llm-wiki. The skill asks the user about target folder, domain (research deep-dive / personalised work wiki / personal knowledge base / business-team wiki / reading a book / combination), source types (web articles, academic PDFs, meeting/podcast transcripts, own notes), image handling, optional search tooling (qmd), schema filename (CLAUDE.md or AGENTS.md), and optional symlinks to sibling folders if the target sits inside an Obsidian vault.
87
90%
Does it follow best practices?
Impact
83%
2.24xAverage score across 4 eval scenarios
Advisory
Suggest reviewing before use
task.mdevals/scenario-4/
Expanding an Existing Research Wiki
Problem/Feature Description
A researcher set up a nutrition science wiki several months ago at existing-wiki/ in the current directory. They've been actively using it — ingesting papers, building out concept pages, and maintaining their log. Now they want to refresh the wiki setup: they've decided to add web articles as a new source type and want the schema updated to reflect that.
They'd like you to bootstrap the wiki configuration again at existing-wiki/ to incorporate the new source type alongside their existing papers and notes. The domain remains research deep-dive. No image handling, no search tooling, no Obsidian vault involved. Schema filename should remain the default.
Output Specification
Attempt to bootstrap the wiki at existing-wiki/. Write a setup-log.md in the current working directory that documents: which files already existed at the target path, what action was taken for each (overwritten, skipped, or conflict reported), and the final state of each of CLAUDE.md, index.md, and log.md (present/unchanged, present/modified, or newly created).