Initialize an Obsidian vault with the agent-ready Zettelkasten system — creates directory structure, templates, CLAUDE.md, MCP config, and hooks
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Run the init script to scaffold a complete vault in the current directory:
bash "${CLAUDE_SKILL_DIR}/scripts/init-vault.sh"
If CLAUDE.md already exists and the user wants to overwrite:
bash "${CLAUDE_SKILL_DIR}/scripts/init-vault.sh" --force
The script handles everything: directories, templates, CLAUDE.md, .mcp.json, hooks, .gitignore, example notes, and git init.
After the script completes, tell the user:
Vault initialized! Next steps:
1. Open this folder in Obsidian
2. Install recommended community plugins:
- Dataview (recommended — powers Spaces dashboards)
- Obsidian Linter (recommended — auto-formatting)
3. In Obsidian Settings → Core Plugins → Templates:
- Set "Template folder location" to "templates"
4. Start using the vault:
- /process — Process a source note (try the example post!)
- /recall — Review session with spaced repetition
- /synthesize — Cross-domain synthesis
- /research — Research a new topic
- /youtube — Create notes from a YouTube video
$ARGUMENTS
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Analyze a book (EPUB/PDF) and generate detailed chapter-by-chapter notes with extracted key concepts. Use when given a book file path to process.
The English summary is being prepared. Showing the original description.
Process an online course into detailed vault notes — one per lecture, with slides and transcripts synthesized. Use this skill whenever the user shares a course URL, syllabus page, or lecture playlist and wants structured notes from it. Also triggers on "process this course", "take notes on these lectures", "course notes", any university course page, or when someone pastes a link to a course with multiple lectures/sessions. Even if the user just says "check out this course" or drops a .edu link with a schedule — use this skill.
The English summary is being prepared. Showing the original description.
Deep, iterative, multi-source research that explores a topic from multiple perspectives, detects contradictions, and produces a comprehensive vault note with fact-level citations and a confidence map. Use this skill whenever the user says /deep-research, "deep research X", "research X thoroughly", "investigate X deeply", "I need to really understand X", or wants research that goes beyond a quick web search. Also use when the user wants to understand a complex, contested, or multi-faceted topic, compare competing approaches with evidence, or build a comprehensive mental model they can trust for decisions. This is heavier than /research — it searches web, academic papers, Reddit, and the vault, then loops through exploration and critique rounds until the evidence base is solid. When in doubt between /research and /deep-research, prefer this one if the topic is complex, contested, or the user wants depth over speed.
The English summary is being prepared. Showing the original description.
Extract transcript and key slides from a local video file, then create a vault-formatted lecture note. Use this skill whenever a user provides a local video file (.mp4, .mov, .mkv, .avi, .webm) and wants notes from it. Triggers on "lecture", "take notes", "I have a recording of", "class video", "transcribe this presentation", "process this video for notes", or /lecture. Works with any language — auto-detects transcript language.
The English summary is being prepared. Showing the original description.
Use when searching for academic papers related to a topic, finding papers similar to one already in the vault, or discovering research gaps. Triggers on "find papers", "related papers", "paper search", "literature", "what papers should I read about X".
The English summary is being prepared. Showing the original description.
CORE learning workflow — use this whenever the user has a source note open (paper, post, book, lecture, course, clipping) and wants to extract knowledge, understand what they just read, or build it into their vault. Triggers on "process this note", "process this paper", "extract concepts", "what can I learn from this", "atomize this", "add this to my vault", "what's important here", or when the user shares a note and asks for help understanding it. Do NOT wait for an explicit /process command — if the user is engaging with a source note and wants to go deeper, this skill applies.
The English summary is being prepared. Showing the original description.