obsidian-vault-ops

The obsidian-vault-ops skill provides a comprehensive suite of tools for maintaining and interacting with an Obsidian Personal Knowledge Management (PKM) vault. Designed for users who rely on the 'Goal-Project-Daily' cascade, this skill enables the agent to act as a system librarian and automated executor. It is specifically tailored for environments where file structure, metadata consistency, and inter-note connectivity via wiki-links are paramount to productivity and accountability.

• File System Management: Supports robust glob-based searching and directory-wide file operations to navigate structured vaults containing Daily Notes, Projects, Goals, and Archives.

• Metadata and Frontmatter: Automatically maintains YAML frontmatter integrity, ensuring consistent tagging (e.g., #active, #priority/high) and status tracking for tasks and projects.

• Intelligent Templating: Performs dynamic variable substitution for date-based notes (YYYY-MM-DD), time-stamping, and relative date calculation (date-1, date+1) based on template files.

• Wiki-Link Maintenance: Handles complex internal linking, including standard [[Note]], aliased [[Note|Display]], and section-specific [[Note#Section]] links to preserve the graph-like structure of the vault.

• Contextual Awareness: Prioritizes reading the CLAUDE.md vault context file to adhere to user-defined conventions before executing write or edit operations.

• Automated Hygiene: Facilitates vault maintenance tasks such as fixing broken links, consolidating duplicate notes, and ensuring standard heading hierarchies are preserved during edits.

• Practical Tips: Always verify the existence of a template before note creation to ensure frontmatter compliance. Use the skill in conjunction with project-specific CLAUDE.md files to respect directory-level organizational rules.

• Inputs/Outputs: Accepts file paths, search strings, and template identifiers. Returns processed markdown content, file status confirmation, or diagnostic information regarding link integrity.

• Constraints: Strictly adheres to relative file paths to ensure compatibility with cross-platform Obsidian installations. Designed for Markdown-based storage with no external database dependencies.