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-3/
Research Wiki Inside Obsidian Vault
Problem/Feature Description
A researcher uses Obsidian to manage all their notes and has an existing vault at my-vault/ in the current directory. They want to set up an LLM-maintained wiki directly inside this vault so they can browse wiki pages alongside their other notes in the Obsidian graph view. The vault already contains some notes in a research-notes/ folder.
The researcher reads web articles and writes their own notes. They don't need image handling or search tooling at this stage. The schema file should use the default name. After setup, they want the Obsidian graph view to only show their wiki pages in a meaningful way — not the raw sources.
Output Specification
Set up the wiki at my-vault/ for a research deep-dive wiki focused on articles and notes. Write all files to disk. If the vault requires graph configuration, apply it. Produce a setup-log.md in the current working directory that documents: the graph configuration action taken (what was written or what was recommended), the full content of any graph.json written, the source types configured, and the final directory tree created.