Skip to content
Skills Library
Personal productivity · Learning & explanation

vault-workflow

/vault-workflow

Use when the user asks you to search, read, or reason about notes in their markdown vault — guides when to use which vault tool and how to chain them for good results.

Licence
MIT
Last repository change
27.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when the user asks you to search, read, or reason about notes in their markdown vault — guides when to use which vault tool and how to chain them for good results.

Original author description

Use when the user asks you to search, read, or reason about notes in their markdown vault — guides when to use which vault tool and how to chain them for good results.

How it works

  1. Search strategy
  2. Reading and context
  3. Link-graph questions
  4. Writes (only if read-only mode is disabled)
  5. Do not
Original SKILL.md headings · 49 lines, 305 words
SKILL.md preview
---
name: vault-workflow
description: Use when the user asks you to search, read, or reason about notes in their markdown vault — guides when to use which vault tool and how to chain them for good results.
---

# Working effectively with the markdown vault

When the user mentions "my vault", "my notes", or asks a question that could
be answered from their knowledge base, use the markdown-vault-mcp tools as
follows.

## Search strategy

- **Default to `search` with `mode="hybrid"`** — combines BM25 keyword and
  embedding similarity, gives the best recall for conceptual questions.
- Fall back to `mode="keyword"` only when the user gives an exact phrase or
  tag they want matched literally.
- If hybrid returns nothing and the query is a proper noun, retry with
  `mode="keyword"` — embeddings miss exact names.

## Reading and context

- After finding a relevant note with `search`, call `get_context` on the top
  hit before reading the full body. Context returns backlinks, outlinks,
  similar notes, folder peers, and tags in one call — usually enough to
  answer without reading the file.
- Only call `read` when the user asks for the text itself or when
  `get_context` does not give enough signal.

## Link-graph questions

- "What notes reference X?" → `get_backlinks`.
- "What does this note link to?" → `get_outlinks`.
- "How are these two notes connected?" → `get_connection_path`.
- "What is orphaned?" → `get_orphan_notes`.
- "What is most cited?" → `get_most_linked`.

## Writes (only if read-only mode is disabled)

- Prefer `edit` over `write` for targeted changes — `edit` fails safely if
  the old text is not unique, preventing accidental overwrites.
- Use `rename(update_links=True)` for moves, never `write` to a new path plus
  `delete` of the old path — the `update_links` flag repairs internal
  references.
- Never call `reindex` after writes; the server updates its index inline.

## Do not

- Do not use `list_documents` as a search substitute — it is a flat
  enumeration, not ranked.
- Do not read a note and then re-search for it; remember the path from the
  first result.

Versions

The database has no other skills named vault-workflow.

Database snapshot: 13.11.2026 · package version 140406c885b5 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90vault
    Search, read, write, and manage files in the Kept conversation vault. Use when the user asks about past conversations, wants to save notes, needs to find specific content, or wants to organize their vault.
  • 100vault-knowledge
    This skill should be used when working on any project to understand how to effectively interact with the Obsidian knowledge vault. It teaches when to capture knowledge, what to capture, how to format vault notes, and how to search effectively. Use when you need to "save to…
  • 100vault-setup
    Use when the markdown-vault MCP server is down or misconfigured — vault not set up yet, vault directory moved or renamed, git token expired — or when the user asks to set up, connect, or repair their markdown vault. Runs a guided discover → validate → write-config → restart flow.
  • 85obsidian-second-brain
    Use an Obsidian vault as the agent's persistent second brain. Use when the user asks to set up their second brain, Obsidian memory or a notes vault, asks to save or recall project knowledge, or when starting/ending a work session and a vault is configured (a LAYOUT.md exists in…
  • 100obsidian-vault
    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.
  • 100scout-vault
    Trace vault wikilinks, inventory notes, or explore code definitions and call chains. Use when finding related notes, references, or scouting a vault. Read-only.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.