
Obsidian Automation
Automate Obsidian note creation, linking, templates, and vault search through MCP so your agent maintains a living PKM while you build.
Overview
Obsidian Automation is an agent skill most often used in Build (also Idea, Grow) that automates Obsidian note creation, linking, templates, and vault search via MCP.
Install
npx skills add https://github.com/claude-office-skills/skills --skill obsidian-automationWhat is this skill?
- MCP tools: obsidian_create_note, obsidian_search, obsidian_link, obsidian_template
- Built-in daily note and meeting note YAML templates with date navigation links
- Knowledge linking and graph-oriented workflows from search and link patterns
- Pairs with related office skills: notion-automation, deep-research, meeting-notes
- Supports template application and structured PKM automation in English
- Ships daily note and meeting note YAML template patterns in the skill readme
Adoption & trust: 2.5k installs on skills.sh; 196 GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your research, specs, and meeting notes sit in Obsidian but updating templates, links, and daily notes by hand breaks your shipping rhythm.
Who is it for?
Indie builders who already use Obsidian as a vault of record and run Claude or GPT with MCP to notes.
Skip if: Teams standardized on Notion-only wikis with no Obsidian vault, or builders who do not want MCP filesystem/network access to local notes.
When should I use this skill?
Automate Obsidian knowledge management, note linking, and personal knowledge base workflows.
What do I get? / Deliverables
Agents create and link markdown notes from templates and queries so your PKM stays current while you focus on product work.
- Created markdown notes
- Applied templates with links
- Search results and link graph updates
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Documentation and structured notes are anchored in Build, where specs, ADRs, and runbooks accumulate—even though the same vault supports earlier research and later content. Docs is the primary shelf for markdown knowledge bases, daily notes, and meeting capture tied to the product.
Where it fits
Spin up structured competitor scrape notes with backlinks from a single search query.
Apply the meeting note template after a standup and link decisions to the feature spec.
Maintain a dated daily note with tasks and reflections without opening Obsidian manually.
Create content-calendar entries from a template and link them to launch checklists.
Append incident retrospectives and link them to monitoring runbooks in the vault.
How it compares
An Obsidian-specific MCP workflow skill—not a generic markdown writer or a hosted Notion integration.
Common Questions / FAQ
Who is obsidian automation for?
Solo builders and small content-heavy products who keep specs, research, and journals in Obsidian and want agent-driven note and link maintenance.
When should I use obsidian automation?
In Build/docs for ADRs and runbooks; in Idea/research when capturing competitor and audience notes; in Grow/content when templating editorial or lifecycle notes—all inside the same vault.
Is obsidian automation safe to install?
It can create and link notes via MCP against your vault; review the Security Audits panel on this Prism page and scope MCP permissions before connecting production or sensitive notes.
SKILL.md
READMESKILL.md - Obsidian Automation
# Obsidian Automation Automate Obsidian knowledge management and personal knowledge base workflows. ## Core Capabilities ### Note Creation ```yaml note_templates: daily_note: filename: "{{date:YYYY-MM-DD}}" folder: "Daily Notes" template: | # {{date:dddd, MMMM D, YYYY}} ## Morning Intentions - [ ] ## Tasks - [ ] ## Notes ## Evening Reflection --- [[{{date:YYYY-MM-DD|-1d}}|← Yesterday]] | [[{{date:YYYY-MM-DD|+1d}}|Tomorrow →]] meeting_note: filename: "Meeting - {{title}} - {{date}}" folder: "Meetings" template: | --- date: {{date}} attendees: {{attendees}} tags: meeting --- # {{title}} ## Agenda ## Notes ## Action Items - [ ] ## Follow-ups [[Meetings MOC]] ``` ### Smart Linking ```yaml auto_linking: rules: - pattern: "[[Person/{{name}}]]" trigger: "@{{name}}" create_if_missing: true - pattern: "[[Project/{{project}}]]" trigger: "#proj/{{project}}" backlink_suggestions: enabled: true min_mentions: 2 alias_support: - "[[Machine Learning|ML]]" - "[[Artificial Intelligence|AI]]" ``` ### Dataview Queries ```yaml dataview_examples: tasks_due_today: query: | ```dataview TASK WHERE !completed AND due = date(today) SORT due ASC ``` recent_meetings: query: | ```dataview TABLE date, attendees FROM "Meetings" WHERE date >= date(today) - dur(7 days) SORT date DESC LIMIT 10 ``` project_dashboard: query: | ```dataview TABLE status, due, priority FROM #project WHERE status != "completed" SORT priority ASC ``` ``` ### Templates ```yaml templates: zettelkasten: filename: "{{date:YYYYMMDDHHmmss}}" content: | --- id: {{date:YYYYMMDDHHmmss}} tags: links: --- # {{title}} ## Idea ## Source ## Connections - Related to: ## References book_note: filename: "Book - {{title}}" content: | --- author: {{author}} finished: rating: tags: book --- # {{title}} by {{author}} ## Summary ## Key Ideas ## Highlights ## My Thoughts ## Action Items ``` ## Workflow Automations ### Web Clipper ```yaml web_clipper: trigger: browser_extension actions: - extract_content: title: "{{page.title}}" url: "{{page.url}}" content: "{{selection}}" - create_note: folder: "Clippings" template: web_clip - add_tags: ["web-clip", "{{domain}}"] ``` ### Research Workflow ```yaml research_workflow: steps: - create_topic_note: filename: "Research - {{topic}}" folder: "Research" - gather_sources: search: "{{topic}}" link_to_note: true - generate_questions: ba