CtrlK
BlogDocsLog inGet started
Tessl Logo

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

2.24x
Quality

90%

Does it follow best practices?

Impact

83%

2.24x

Average score across 4 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

obsidian-graph.mdreferences/

Obsidian graph view setup

Configure the graph so only synthesis-layer pages show (wiki/ minus wiki/sources), and color the four remaining page categories distinctly. Source pages are excluded because they're hub nodes connected to everything — including them clutters the graph without adding insight.

Decision tree

  • Case A — target is itself a vault (<target>/.obsidian/ exists): edit <target>/.obsidian/graph.json to set the search filter and colorGroups. If graph.json doesn't exist yet, create it with the minimal body below; Obsidian fills in remaining defaults on next launch.
  • Case B — target sits inside an ancestor vault (an ancestor has .obsidian/, but the target itself does not): do NOT auto-edit the ancestor's graph.json — that would change the graph for the user's other notes. Instead, tell the user the queries to apply manually:
    • Filter: path:"<target-relative-to-vault>/wiki/" -path:"<target-relative-to-vault>/wiki/sources"
    • Add four groups under "Groups" with queries like path:<target-relative-to-vault>/wiki/entities, picking colors via the colour wheel.
  • Case C — no .obsidian/ anywhere: skip silently. Not an Obsidian vault.

Color group palette

Decimal RGB values, computed from hex with echo $((0x<HEX>)). Adjust if the user wants a different palette.

Page categoryHexDecimal RGB
path:wiki/entities#E8825D (warm coral)15237725
path:wiki/concepts#3BB4C1 (teal)3912897
path:wiki/topics#6BAE5C (green)7056988
path:wiki/synthesis#E5A82B (gold)15050795

Minimal graph.json

Use this when the file doesn't exist:

{
  "search": "path:\"wiki/\" -path:\"wiki/sources\"",
  "collapse-filter": false,
  "collapse-color-groups": false,
  "colorGroups": [
    { "query": "path:wiki/entities",  "color": { "a": 1, "rgb": 15237725 } },
    { "query": "path:wiki/concepts",  "color": { "a": 1, "rgb": 3912897 } },
    { "query": "path:wiki/topics",    "color": { "a": 1, "rgb": 7056988 } },
    { "query": "path:wiki/synthesis", "color": { "a": 1, "rgb": 15050795 } }
  ]
}

Order matters: the first matching group wins. Since the four paths don't overlap, the order is just convention (matches the order in index.md).

references

obsidian-graph.md

SKILL.md

tile.json