obsidian-vault-workflow
Skill17 starsChanged 4 months agoMITView on GitHub
Use this skill when a user asks an agent to inspect, organize, summarize, or update an Obsidian vault through this MCP server. Ask the agent: Generate a daily status report for my Projects folder. Include recently touched notes, open checkbox tasks, completed checkbox count, and top tags. Preview it first. If approved, write it to: Ask the agent: Review the top-level vault structure and suggest 5 cleanup actions. Do not edit anything yet. Ask the agent: Search the vault for…
1 other project uses a version of this.
Adopted by
Most recently taken up by
- ntaffzii/Skill-Agentstheir own version, first seen Sep 2, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- ntaffzii/Skill-Agents★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repositoryOne other file it gives its agents.
- release-note-captainSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
17 rules. About 0 are common, 10 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 3
Use this skill when a user asks an agent to inspect, organize, summarize, or update an Obsidian vault through this MCP server.
- Distinctive: line 7
Treat the vault as the user's source of truth.
- Distinctive: line 8
Prefer read-only exploration before editing.
- Distinctive: line 9
Use vault-relative paths only.
- Distinctive: line 10
Never delete notes unless the user explicitly asks for deletion.
- Very specific: line 12
When writing existing notes, recommend OBSIDIAN_BACKUP_ON_WRITE=true.
- Distinctive: line 13
Keep generated notes concise and link-friendly.
- Very specific: line 17
Use get_folder_structure to understand the top-level vault layout.
- Very specific: line 18
Use list_notes for the relevant folder rather than scanning the whole vault when the user gives a scope.
- Very specific: line 19
Use search_notes for terms, tags, and project names.
- Very specific: line 20
Use get_note before modifying any existing note.
- Very specific: line 21
Use get_note_links and get_backlinks when the task depends on relationships between notes.
- Very specific: line 26
Read the current note with get_note.
- Distinctive: line 29
After writing, read the note again or summarize the changed path and content.
- Distinctive: line 39
If approved, write it to:
- Distinctive: line 59
Use note paths in backticks.
- Distinctive: line 61
Keep status reports skimmable.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Obsidian Vault Workflow
Use this skill when a user asks an agent to inspect, organize, summarize, or update an Obsidian vault through this MCP server.
Principles
- Treat the vault as the user's source of truth.
- Prefer read-only exploration before editing.
- Use vault-relative paths only.
- Never delete notes unless the user explicitly asks for deletion.
- For broad edits, make a short plan and name the affected folder or note set.
- When writing existing notes, recommend
OBSIDIAN_BACKUP_ON_WRITE=true. - Keep generated notes concise and link-friendly.
Discovery Flow
- Use
get_folder_structureto understand the top-level vault layout. - Use
list_notesfor the relevant folder rather than scanning the whole vault when the user gives a scope. - Use
search_notesfor terms, tags, and project names. - Use
get_notebefore modifying any existing note. - Use
get_note_linksandget_backlinkswhen the task depends on relationships between notes.
Safe Editing Flow
- Confirm the exact target path.
- Read the current note with
get_note. - Make the smallest useful update.
- Preserve frontmatter unless the user asks to change it.
- After writing, read the note again or summarize the changed path and content.
Useful Prompts
Daily Project Status
Ask the agent:
Generate a daily status report for my
Projectsfolder. Include recently touched notes, open checkbox tasks, completed checkbox count, and top tags. Preview it first.
If approved, write it to:
Reports/Daily Project Status.mdVault Triage
Ask the agent:
Review the top-level vault structure and suggest 5 cleanup actions. Do not edit anything yet.
Project Catch-Up
Ask the agent:
Search the vault for notes about
<project name>, then summarize the current status, open tasks, and important linked notes.
Output Style
- Use note paths in backticks.
- Separate findings from proposed edits.
- Keep status reports skimmable.
- Mention when no edit was made.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.