
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.
This repo packages a second-brain workflow around the LLM Wiki pattern. You drop raw sources into `raw/`, the agent turns them into wiki pages, and you browse the result in Obsidian. The pack includes setup, ingest, query, and lint skills so the same schema stays consistent as the wiki grows.
Builders who want Claude Code, Codex, Cursor, or Gemini CLI to maintain an Obsidian knowledge base.
You can keep a personal wiki updated from raw sources without re-structuring everything by hand.
`/second-brain` walks you through naming the vault, choosing a location, and picking tools.
`/second-brain-ingest` reads files from `raw/` and writes structured wiki pages with links and summaries.
`/second-brain-query` lets you ask questions against the wiki contents.
`/second-brain-lint` checks index consistency and broken wikilinks, and can fix mismatches.
The generated vault is shaped for Obsidian browsing with folders for sources, entities, concepts, synthesis, and logs.
npx skills add NicholasSpisak/second-brain
An LLM-maintained personal knowledge base built on the LLM Wiki pattern. Drop raw sources into a folder, let the LLM compile them into a structured wiki, and browse it all in Obsidian.

You feed raw material (articles, papers, notes, transcripts) into a raw/ folder. The LLM reads everything, writes structured wiki pages, creates cross-references, and maintains an index. You browse the results in Obsidian — following links, exploring the graph view, and asking questions.
The LLM is the librarian. You're the curator.
npx skills add NicholasSpisak/second-brain
This installs four skills into your AI agent (Claude Code, Codex, Cursor, Gemini CLI, and 40+ others):
| Skill | What it does |
|---|---|
/second-brain | Set up a new vault (guided wizard) |
/second-brain-ingest | Process raw sources into wiki pages |
/second-brain-query | Ask questions against your wiki |
/second-brain-lint | Health-check the wiki |
/second-brain in your AI agent — it walks you through naming, location, domain, and toolingraw/ folderraw/, then run /second-brain-ingest — the LLM will discuss key takeaways and build wiki pages[[wikilinks]], explore the graph view, check wiki/index.md/second-brain-query to ask questions, /second-brain-lint to health-checkyour-vault/
├── raw/ # Your inbox — drop sources here
│ └── assets/ # Images and attachments
├── wiki/ # LLM-maintained wiki
│ ├── sources/ # One summary per ingested source
│ ├── entities/ # People, orgs, products, tools
│ ├── concepts/ # Ideas, frameworks, theories
│ ├── synthesis/ # Comparisons, analyses, themes
│ ├── index.md # Master catalog of all pages
│ └── log.md # Chronological operation record
├── output/ # Reports and generated artifacts
└── CLAUDE.md # Agent config (varies by agent)
The wizard offers to install these. All optional but recommended:
The wizard failed or I need to re-run setup.
Run /second-brain again — the onboarding script is idempotent. It won't overwrite existing files, so your data is safe. If you need a fresh start, delete the vault folder and re-run.
I accidentally modified a file in raw/.
That's OK. The wiki was built from the original content. If you need the original back, check your git history (if the vault is a git repo) or re-clip the source. The wiki pages are unaffected.
wiki/index.md is out of sync with actual pages.
Run /second-brain-lint — it checks index consistency and offers to fix mismatches.
Wikilinks are broken after renaming a page.
Run /second-brain-lint — it scans for broken [[wikilinks]] and reports which files need updating.
The wiki is getting large and queries are slow.
Install qmd (npm i -g @tobilu/qmd). The query skill uses it automatically when available. It provides fast hybrid search across your wiki files.
Can I use this with multiple AI agents? Yes. The wizard generates config files for each agent you select. They all follow the same wiki schema, so multiple agents can work on the same vault.
How do I handle images in clipped articles?
In Obsidian, set Settings → Files and links → Attachment folder path to raw/assets/. After clipping an article, use "Download attachments for current file" to save images locally.
How often should I lint? After every 10 ingests or monthly — whichever comes first. Also run it before any major query or synthesis work.
Want to learn how to build projects like this with AI? Join the Build With AI community.
Sign in to join the discussion.
No comments yet. Be the first to say what this is good for.

Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.
Topic in, narrated explainer video out. A Claude Code / Codex skill that turns any topic into a black-canvas motion-graphics explainer video with TTS voiceover, subtitles and a chapter progress bar. Chinese or English; every frame drawn in code with Remotion.
Public repository for Agent Skills
Open-source AI job search: scan job portals, evaluate listings into a structured A-H report with a global 1-5 score, tailor your CV, track applications — runs locally in your AI coding CLI (Claude Code, Codex, OpenCode, Antigravity…)
Agent skill for beautiful, verifiable architecture, workflow, sequence, data-flow, and lifecycle diagrams—self-contained HTML with motion and crisp export.
A skill to stop your coding agent from burying the answer. ADHD-friendly output.