obsidian
Obsidian vault mechanics - wiki links, .obsidian/ config, daily notes, plugins. Use when working with Obsidian vaults or structured markdown.
Install
npx skills add https://github.com/technicalpickles/pickled-claude-plugins/tree/main/plugins/second-brain/skills/obsidian
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install technicalpickles-pickled-claude-plugins@llmmart
git clone https://github.com/technicalpickles/pickled-claude-plugins.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole technicalpickles/pickled-claude-plugins collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
Obsidian Skill
Tool-specific mechanics for working with Obsidian vaults.
Vault Detection
A directory is an Obsidian vault if it contains .obsidian/ folder.
Wiki Links
Syntax: [[Note Title]] or [[path/Note Title]]
- Obsidian resolves by title match
- Can include path for disambiguation
- Aliases:
[[Note Title|display text]]
.obsidian/ Configuration
Obsidian stores settings in .obsidian/ at vault root:
| File | Purpose |
|---|---|
daily-notes.json |
Daily note folder and template |
templates.json |
Templates folder location |
zk-prefixer.json |
Zettelkasten/inbox settings |
app.json |
General settings (new file location, attachments) |
plugins/ |
Installed plugin data |
Parsing Config
// daily-notes.json
{
"folder": "Fleeting",
"template": "Templates/daily"
}
// templates.json
{"folder": "Templates"}
// zk-prefixer.json
{
"folder": "📫 Inbox",
"template": "Templates/frontmatter"
}
// app.json
{
"newFileFolderPath": "📫 Inbox",
"attachmentFolderPath": "🖇 Attachments"
}
Daily Notes
Finding today's note:
- Read
.obsidian/daily-notes.jsonfor folder - Use format
YYYY-MM-DD.md(Obsidian default) - Path:
{folder}/{YYYY-MM-DD}.md
Template application:
- Obsidian applies template on note creation
- Template path from
daily-notes.json
Glossary Integration
If Glossary.md exists at vault root:
- Contains known transcription corrections
- Maps common errors to correct terms
- Used by process-daily command
Vault CLAUDE.md
Vaults should have a CLAUDE.md at root describing:
- Folder structure
- Routing rules
- Naming conventions
- References to methodology (PARA, Zettelkasten)
- Disambiguation rules for semantically similar areas
See ../../templates/vault-claude-md.md for template.
Disambiguation Rules
When a vault has areas with semantic overlap (e.g., "tool sharpening" vs "software engineering"), the vault CLAUDE.md can include ### Disambiguation: sections that guide routing decisions.
The routing algorithm checks for:
- Key questions - Decision heuristics for each area
- Category tables - Lists of tools/topics per area
- Edge case mappings - Explicit rules for ambiguous cases
See references/routing.md for the full disambiguation format and how to build custom rules.
References
For methodology (tool-agnostic):
references/para.md- PARA organizational systemreferences/zettelkasten.md- Naming conventionsreferences/note-patterns.md- Note templatesreferences/routing.md- Routing algorithm with disambiguation supportreferences/daily-linking.md- Linking captured notes to daily notereferences/pipeline.md- Processing pipeline stages and status flowreferences/routing-memory.md- Routing correction and learning loop
Files (pickled-claude-plugins)
-
references
-
connecting.md 10.2 KB
Loading… -
daily-linking.md 4.4 KB
Loading… -
johnny-decimal.md 4.2 KB
Loading… -
note-patterns.md 4.2 KB
Loading… -
para.md 3.1 KB
Loading… -
pipeline.md 3.8 KB
Loading… -
routing-memory.md 3 KB
Loading… -
routing.md 14.9 KB
Loading… -
sb-cli.md 3.7 KB
Loading… -
zettelkasten.md 1.3 KB
Loading…
-
-
SKILL.md 3 KB
--- name: obsidian description: Obsidian vault mechanics - wiki links, .obsidian/ config, daily notes, plugins. Use when working with Obsidian vaults or structured markdown. --- # Obsidian Skill Tool-specific mechanics for working with Obsidian vaults. ## Vault Detection A directory is an Obsidian vault if it contains `.obsidian/` folder. ## Wiki Links **Syntax:** `[[Note Title]]` or `[[path/Note Title]]` - Obsidian resolves by title match - Can include path for disambiguation - Aliases: `[[Note Title|display text]]` ## .obsidian/ Configuration Obsidian stores settings in `.obsidian/` at vault root: | File | Purpose | |------|---------| | `daily-notes.json` | Daily note folder and template | | `templates.json` | Templates folder location | | `zk-prefixer.json` | Zettelkasten/inbox settings | | `app.json` | General settings (new file location, attachments) | | `plugins/` | Installed plugin data | ### Parsing Config ```json // daily-notes.json { "folder": "Fleeting", "template": "Templates/daily" } // templates.json {"folder": "Templates"} // zk-prefixer.json { "folder": "📫 Inbox", "template": "Templates/frontmatter" } // app.json { "newFileFolderPath": "📫 Inbox", "attachmentFolderPath": "🖇 Attachments" } ``` ## Daily Notes **Finding today's note:** 1. Read `.obsidian/daily-notes.json` for folder 2. Use format `YYYY-MM-DD.md` (Obsidian default) 3. Path: `{folder}/{YYYY-MM-DD}.md` **Template application:** - Obsidian applies template on note creation - Template path from `daily-notes.json` ## Glossary Integration If `Glossary.md` exists at vault root: - Contains known transcription corrections - Maps common errors to correct terms - Used by process-daily command ## Vault CLAUDE.md Vaults should have a `CLAUDE.md` at root describing: - Folder structure - Routing rules - Naming conventions - References to methodology (PARA, Zettelkasten) - **Disambiguation rules** for semantically similar areas See `../../templates/vault-claude-md.md` for template. ### Disambiguation Rules When a vault has areas with semantic overlap (e.g., "tool sharpening" vs "software engineering"), the vault CLAUDE.md can include `### Disambiguation:` sections that guide routing decisions. The routing algorithm checks for: - **Key questions** - Decision heuristics for each area - **Category tables** - Lists of tools/topics per area - **Edge case mappings** - Explicit rules for ambiguous cases See `references/routing.md` for the full disambiguation format and how to build custom rules. ## References For methodology (tool-agnostic): - `references/para.md` - PARA organizational system - `references/zettelkasten.md` - Naming conventions - `references/note-patterns.md` - Note templates - `references/routing.md` - Routing algorithm with disambiguation support - `references/daily-linking.md` - Linking captured notes to daily note - `references/pipeline.md` - Processing pipeline stages and status flow - `references/routing-memory.md` - Routing correction and learning loop
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.