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

mcp-integrations.mdassets/fragments/

MCP integrations available

When the user asks for material from external systems, pull directly without manual export when possible:

  • Granola — meeting transcripts and notes (mcp__claude_ai_Granola__*)
  • Linear — issues, projects, documents (mcp__claude_ai_Linear__*)
  • Slack — channel/thread messages (mcp__claude_ai_Slack__*)
  • Notion — pages, databases (mcp__claude_ai_Notion__*)
  • Gmail / Calendar / Drive — when authenticated

When pulling from these, save the relevant content to raw/ (transcripts, notes, etc.) so the wiki has a stable artifact to reference, then ingest as normal. Mention only the integrations the user actually has connected.

assets

fragments

image-handling.md

mcp-integrations.md

search-tooling.md

SKILL.md

tile.json