Use this skill whenever working with the Obsidian vault, including: - Writing, creating, or saving notes to Obsidian - Searching for documentation or knowledge - Finding information in the vault - Documenting configurations, guides, or references - Creating how-tos, runbooks, or technical documentation - Capturing knowledge from conversations - Any operation involving the knowledge base Trigger phrases: "write to Obsidian", "save to vault", "create note", "document in Obsidian", "search vault", "find in Obsidian", "knowledge base"
This skill defines mandatory behaviors and standards for ALL Obsidian vault operations.
<vault-config> <!-- CUSTOMIZE: Update path to your Obsidian vault location --> <!-- See README for iCloud hosting instructions --> <path>{{VAULT_PATH}}</path> <search-command>/search-obsidian-vault</search-command> <index-command>/reindex-obsidian-vault</index-command> </vault-config> <mandatory-behaviors> <behavior name="search-first" priority="critical"> <description>Before ANY vault operation, search for existing notes with relevant keywords.</description> <applies-to> <operation>Creating new notes</operation> <operation>Finding information</operation> <operation>Updating content</operation> <operation>Cross-linking</operation> </applies-to> <workflow> <step>Search vault for relevant keywords</step> <step>Review results for duplicates and related notes</step> <step>Proceed only after reviewing search results</step> </workflow> </behavior> <behavior name="duplicate-check" priority="high"> <description>Before creating ANY new note, search for existing notes on the same topic.</description> <workflow> <step>Search for existing notes on the topic</step> <step>If similar note exists: Update it or link to it</step> <step>If no match: Proceed with creation</step> <step>Report findings to user</step> </workflow> </behavior> <behavior name="auto-cross-link" priority="high"> <description>When creating or updating notes, identify and include related notes.</description> <requirements> <requirement>Use search results to identify related notes</requirement> <requirement>Include minimum 2-3 cross-links with explanations</requirement> <requirement>Consider bidirectional linking</requirement> <requirement>Never create orphaned notes</requirement> </requirements> </behavior> <behavior name="tag-validation" priority="high"> <description>Validate all tags against existing vault taxonomy before applying.</description> <requirements> <requirement>Check existing vault taxonomy via search</requirement> <requirement>Use hierarchical format: category/subcategory/specific</requirement> <requirement>Prefer existing tags over creating new ones</requirement> <requirement>Validate against standard categories</requirement> </requirements> </behavior> <behavior name="para-placement" priority="high"> <description>Confirm correct PARA location before writing any file.</description> <workflow> <step>Determine correct PARA location using decision tree</step> <step>Confirm with user if ambiguous</step> <step>Follow PARA methodology strictly</step> </workflow> </behavior> </mandatory-behaviors> <workflow-enforcement> <phase name="search-first" order="1"> <action>Search vault for relevant keywords</action> <action>Review results for duplicates and related notes</action> </phase> <phase name="validate-before-writing" order="2"> <action>Check for duplicate content</action> <action>Identify notes to cross-link</action> <action>Validate proposed tags</action> <action>Confirm PARA placement</action> </phase> <phase name="write-with-standards" order="3"> <action>Apply all documentation standards</action> <action>Include proper frontmatter</action> <action>Use hierarchical tags</action> <action>Add cross-links with explanations</action> </phase> <phase name="verify-after-writing" order="4"> <action>Confirm file created at correct path</action> <action>Verify links resolve</action> <action>Report status to user</action> </phase> </workflow-enforcement> <documentation-standards> <frontmatter-requirements> <required-fields> <field name="tags" type="list"> <description>2-8 hierarchical tags</description> <format>category/subcategory/specific</format> </field> <field name="date" type="datetime"> <description>ISO 8601 timestamp of creation</description> <format>YYYY-MM-DD HH:MM:SS</format> </field> <field name="type" type="enum"> <description>Document classification</description> <values> <value name="how-to">Step-by-step instructions</value> <value name="reference">Technical reference material</value> <value name="concept">Conceptual explanation</value> <value name="project">Project documentation</value> <value name="runbook">Operational procedures</value> </values> </field> </required-fields> <optional-fields> <field name="context" type="enum"> <values>work, personal, shared</values> </field> <field name="status" type="enum"> <values>active, complete, archived, draft</values> </field> <field name="related" type="list"> <description>Wiki-style links to related notes</description> </field> </optional-fields> <example> ```yaml ---