Files
obsidian-claude-pkm/vault-template/.claude/skills/obsidian-vault-ops/SKILL.md
Bill Allred 78a822a3df v2.0: Add hooks, agents, skills, rules, and plugin structure
Major modernization to leverage latest Claude Code features:

Plugin Foundation:
- Add .claude-plugin/plugin.json manifest for distribution
- Add .claude/settings.json with permissions and hooks config

Hooks (automatic behaviors):
- SessionStart: Initialize vault environment variables
- PostToolUse: Auto-commit changes after Write/Edit operations

Custom Agents (4):
- note-organizer: Vault organization and link maintenance
- weekly-reviewer: Facilitate weekly review aligned with goals
- goal-aligner: Check daily/weekly alignment with long-term goals
- inbox-processor: GTD-style inbox processing

Skills (3):
- obsidian-vault-ops: Read/write vault files, manage wiki-links
- goal-tracking: Track progress across goal cascade
- daily-workflow: Morning/midday/evening routines

Modular Rules (3):
- markdown-standards: File naming, tags, frontmatter conventions
- productivity-workflow: Goal cascade, daily/weekly planning
- project-management: Project structure and status tracking

Other:
- Add statusline.sh for terminal vault stats display
- Add CLAUDE.local.md.template for personal overrides
- Update CLAUDE.md with new features documentation
- Update all docs with v2.0 features and upgrade guide

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2025-12-19 18:57:48 -08:00

2.6 KiB

name, description, allowed-tools
name description allowed-tools
obsidian-vault-ops Read and write Obsidian vault files, manage wiki-links, process markdown with YAML frontmatter. Use when working with vault file operations, creating notes, or managing links. Read, Write, Edit, Glob, Grep

Obsidian Vault Operations Skill

Core operations for reading, writing, and managing files in an Obsidian vault.

Vault Structure

vault-root/
├── CLAUDE.md           # Main context (always read first)
├── Daily Notes/        # YYYY-MM-DD.md format
├── Goals/              # Goal cascade files
├── Projects/           # Project folders with CLAUDE.md
├── Templates/          # Reusable note structures
└── Archives/           # Completed/inactive content

File Operations

Reading Notes

  • Use Glob to find files: *.md, Daily Notes/*.md
  • Read CLAUDE.md first for vault context
  • Check for wiki-links to related notes

Creating Notes

  1. Check if note already exists
  2. Use appropriate template if available
  3. Add YAML frontmatter with date and tags
  4. Insert wiki-links to related notes

Editing Notes

  • Preserve YAML frontmatter structure
  • Maintain existing wiki-links
  • Use consistent heading hierarchy
  • Apply standard tag format
[[Note Name]]                    # Simple link
[[Note Name|Display Text]]       # Link with alias
[[Note Name#Section]]            # Link to section

YAML Frontmatter

Standard frontmatter structure:

---
date: 2024-01-15
tags: [tag1, tag2]
status: active
---

Template Variables

When processing templates, replace:

  • {{date}} - Today's date (YYYY-MM-DD)
  • {{date:format}} - Formatted date
  • {{date-1}} - Yesterday
  • {{date+1}} - Tomorrow
  • {{time}} - Current time

Common Patterns

Daily Note Creation

  1. Calculate today's date in YYYY-MM-DD format
  2. Check if Daily Notes/{date}.md exists
  3. If not, read Templates/Daily Template.md
  4. Replace template variables
  5. Write to Daily Notes/{date}.md
  1. Extract key terms from current note
  2. Search vault for matching content
  3. Suggest wiki-links to related notes

Tag Operations

  • Priority: #priority/high, #priority/medium, #priority/low
  • Status: #active, #waiting, #completed, #archived
  • Context: #work, #personal, #health, #learning

Best Practices

  1. Always check CLAUDE.md for vault-specific conventions
  2. Preserve existing structure when editing
  3. Use relative paths for internal links
  4. Add frontmatter to new notes
  5. Link to relevant goals when creating tasks