Best PromptsObsidian Vault Skill
Give an agent working rules for an Obsidian vault: naming conventions, wikilink discipline, index notes, and shell workflows for search and backlinks.
--- name: obsidian-vault description: Search, create, and manage notes in the Obsidian vault with wikilinks and index notes. Use when user wants to find, create, or organize notes in Obsidian. --- # Obsidian Vault ## Vault location `/mnt/d/Obsidian Vault/AI Research/` Mostly flat at root level. ## Naming conventions - **Index notes**: aggregate related topics (e.g., `Ralph Wiggum Index.md`, `Skills Index.md`, `RAG Index.md`) - **Title case** for all note names - No folders for organization - use links and index notes instead ## Linking - Use Obsidian `[[wikilinks]]` syntax: `[[Note Title]]` - Notes link to dependencies/related notes at the bottom - Index notes are just lists of `[[wikilinks]]` ## Workflows ### Search for notes ```bash # Search by filename find "/mnt/d/Obsidian Vault/AI Research/" -name "*.md" | grep -i "keyword" # Search by content grep -rl "keyword" "/mnt/d/Obsidian Vault/AI Research/" --include="*.md" ``` Or use Grep/Glob tools directly on the vault path. ### Create a new note 1. Use **Title Case** for filename 2. Write content as a unit of learning (per vault rules) 3. Add `[[wikilinks]]` to related notes at the bottom 4. If part of a numbered sequence, use the hierarchical numbering scheme ### Find related notes Search for `[[Note Title]]` across the vault to find backlinks: ```bash grep -rl "\\[\\[Note Title\\]\\]" "/mnt/d/Obsidian Vault/AI Research/" ``` ### Find index notes ```bash find "/mnt/d/Obsidian Vault/AI Research/" -name "*Index*" ```
How to use
A template, not a drop-in: the vault path is Matt's own machine, so replace it and the conventions with yours. What transfers is the shape: pin the vault location, state the naming and linking rules, and give concrete shell commands for search, backlinks, and index discovery so the agent operates the vault the way you do instead of inventing its own filing system. Save as .claude/skills/obsidian-vault/SKILL.md, or install Matt's full MIT-licensed set (github.com/mattpocock/skills) with 'claude plugins install mattpocock-skills'.
More skill prompts
--- name: writing-documentation description: Write or update documentation from the code. Use when the user asks for a README, API reference, guide, docstrings, or says the docs are out of date. --- # Writing Documentation Documentation is a claim about behavior. Every claim must be checked against the code before it ships, because a wrSKILL.md
Documentation Skill
A skill that documents what the code does rather than what it should do: read first, examples from tests, unverifiable claims marked.
--- name: security-review description: Review code for security defects. Use before merging changes that touch authentication, authorization, user input, file handling, secrets, or external requests, or when the user asks for a security review. --- # Security Review Find defects an attacker could actually use. A finding without an attacSKILL.md
Security Review Skill
A skill that reviews changes for exploitable defects, follows untrusted input to where it lands, and reports only findings with an attack path.
--- name: accessibility-review description: Audit UI code for accessibility defects against WCAG. Use when building or changing components, forms, modals, or navigation, or when the user asks about accessibility, a11y, screen readers, or keyboard support. --- # Accessibility Review Judge the interface by whether a person can complete thSKILL.md
Accessibility Skill
A skill that audits UI against WCAG by keyboard, semantics, and state, reporting who is blocked rather than listing rule numbers.