obsidian-read-context
Analyze Obsidian vault documentation to understand current knowledge state. Use when exploring documentation structure, identifying gaps, or planning documentation consolidation.
npx skills add majiayu000/claude-skill-registry --skill obsidian-read-context --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Obsidian Read Context Skill Understand the current state of knowledge in an Obsidian vault by analyzing markdown files. > **See also**: [Shared Conventions](../shared/CONVENTIONS.md) | [Safety Guidelines](../shared/SAFETY.md) ## Purpose Scan and analyze Obsidian vault contents to identify topics, detect overlaps, find gaps, and suggest canonical document targets for consolidation. ## Background Knowledge ### What is an Obsidian Vault? An Obsidian vault is a folder containing Markdown files that form a knowledge base. Key characteristics: - **Markdown files**: Plain text with `.md` extension - **Wikilinks**: Internal links using `[[double brackets]]` syntax - **Frontmatter**: Optional YAML metadata at file start - **Folders**: Organize notes by category or status (e.g., `_inbox`, `specs`, `design`) ### Common Vault Structures ``` vault/ ├── _inbox/ # Unprocessed notes, quick captures ├── specs/ # Technical specifications ├── design/ # Design documents ├── notes/ # General notes ├── templates/ # Obsidian templates └── README.md # Vault overview ``` ### Reading Modes | Mode | Purpose | Depth | |------|---------|-------| | `skim` | Quick overview of structure and topics | Read titles
- Purpose
- Background Knowledge
- What is an Obsidian Vault?
- Common Vault Structures
- Reading Modes
- Input Sources
- Output Contract
- Workflow
- 1. Identify Vault Boundary
- 2. Gather File List
- 3. Skim Mode Analysis
- 4. Deep Mode Analysis
- 5. Detect Topics and Patterns
- 6. Generate Suggestions
Check for .obsidian folder (indicates vault root)
ls -la /path/to/vault/.obsidian 2>/dev/null && echo "Vault confirmed"
List top-level structure
ls -la /path/to/vault/
List all markdown files
find /path/to/vault -name "*.md" -type f
Count files per directory
find /path/to/vault -name "*.md" -type f | xargs -I{} dirname {} | sort | uniq -c
Extract headings from a file
grep -E "^#+ " /path/to/file.mdWhat does the obsidian-read-context skill do?
Analyze Obsidian vault documentation to understand current knowledge state. Use when exploring documentation structure, identifying gaps, or planning documentation consolidation.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill obsidian-read-context --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.