← ClaudeAtlas

obsidianlisted

Use when unsure which Obsidian command to use, or when someone says "obsidian help", "log something to Obsidian", "what obsidian commands are there", "obsidian?". Routes to the correct skill based on intent. Also use as a fallback when an Obsidian operation does not clearly map to capture, log, daily, search, or brief.
chuckplayer/claude-agent-pack · ★ 2 · AI & Automation · score 75
Install: claude install-skill chuckplayer/claude-agent-pack
# Obsidian Help The Obsidian skill family writes and reads Claude session context directly into your Obsidian vault — captures, session logs, daily activity notes, and search across everything Claude has logged. Every note written follows a consistent folder layout under `Claude/` so the vault stays clean and navigable. ## The five skills | Skill | Use when | |---|---| | `/obsidian-brief` | Loading project context before starting work — synthesizes recent notes without a search query | | `/obsidian-capture` | Saving a note, decision, or thought to the vault right now | | `/obsidian-log` | Writing a session log entry for the current Claude Code session | | `/obsidian-daily` | Viewing today's Claude activity note | | `/obsidian-search` | Finding past session logs or captures by keyword | ## 1. Identify intent Ask the user one question: **"What are you trying to do?"** Listen for these patterns: - "brief", "catch me up", "context", "what have we been working on", "load context" → `/obsidian-brief` - "capture", "save", "note", "jot", "quick note", "save this" → `/obsidian-capture` - "log", "session", "log this session", "what did we do", "record session" → `/obsidian-log` - "today", "daily", "what did I do today", "daily note" → `/obsidian-daily` - "find", "search", "look up", "what did I log about" → `/obsidian-search` ## 2. Route and hand off Once intent is clear, tell the user which skill handles it and invoke it. For example: "That's a session log — starting `/obsidi