
from llm-obsidian-wiki12
Implements Karpathy's LLM Wiki pattern: an LLM-maintained Obsidian vault that captures sources, synthesizes typed notes, and provides citation-backed queries fo
LLM Obsidian Wiki turns an LLM into a persistent researcher by maintaining a structured Obsidian vault. The skill automates capture of URLs, PDFs, GitHub content and transcripts, ingests raw sources into typed markdown pages (concepts, decisions, comparisons), and keeps the vault current with cross-links and confidence scores. Agents can then answer queries by reading the compiled wiki instead of re-scraping sources.
Use when you need durable, auditable memory for long-running projects: engineering ADRs, competitive research, annotated bibliographies, team knowledge bases, or any workflow where repeated context must be preserved and reused. It triggers on instructions to scaffold a vault, capture URLs/PDFs, ingest sources, or query the wiki.
Designed for Claude Code / Claude-like plugin environments and any agent that can manage a local filesystem and run the included utilities. It favors file-based workflows (Obsidian) over remote services.
Implements Karpathy's LLM Wiki pattern as a Claude Code plugin with four agent personas (Researcher, Advisor, Curator, Scribe) maintaining a structured Obsidian vault. 27 shell scripts cover capture (git log, GitHub, PDF, text, URL, YouTube), vault management (init, create page, promote draft, update index/hubs/hot), health checks (orphans, stale pages, contradictions, source drift, tree topology), and search/browse. Scripts are well-written with consistent error handling, umask 077, SSRF protection, and privacy-first defaults. Failed to run in audit env due to missing lib/ sourced files and external tool dependencies — expected for interactive vault tools.
obsidian-cliyt-dlpdefuddle-clipandoctrafilaturagh-cliImpressively comprehensive skill with strong security practices (umask 077 everywhere, SSRF validation, GraphQL injection prevention, no hardcoded creds, privacy-first defaults). Scripts are well-structured and portable (BSD/GNU date handling). The main limitation is tight coupling to Obsidian CLI and the lib/ shared modules — not a quality issue but affects portability.