agentleFS
Sign inStart free
fakechrisfakechris/obsidian_vault_pipeline/skills/when-to-consult/SKILL.md

when-to-consult

Skill165 starsChanged 4 months agoApache-2.0View on GitHub

Decide when to consult the OVP vault via MCP versus answering from model memory. Prefer ask/find/search/claim/theme-page for vault-grounded facts.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to choose the right OVP MCP surface — or to skip the vault when it cannot help.

    line 8
  2. Very specific:

    When ask already returned honest empty coverage — do not fabricate vault citations

    line 27
  3. Very specific:

    Run ovp2 mcp --vault-root "$OVP_VAULT_ROOT" (see root mcp.json)

    line 32
  4. Very specific:

    After content changes, operators may need ovp2 index before search/ask quality recovers

    line 33
  5. Very specific:

    Keep ops conventions in skills + docs/ops/.

    line 34

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

When to Consult OVP

Use this skill to choose the right OVP MCP surface — or to skip the vault when it cannot help.

Prefer the vault (call MCP)

NeedSkill / tool
Natural-language answer with verified receiptsask
Structured inventory (kind/tag/date/entity)find
Keyword / phrase huntsearch
Audit a [claim:…] citationclaim
Wiki-style theme narrativetheme-page
Pipeline pulsestatus
Health / index problemsdoctor
Save a note into the vault safelycapture-drop

Answer without the vault

  • Pure coding / repo questions about this Rust workspace (use AGENTS.md, crates, tests)
  • General knowledge unrelated to the operator’s notes
  • When ask already returned honest empty coverage — do not fabricate vault citations

Hygiene

  • Set OVP_VAULT_ROOT (example: /path/to/your/vault); never embed secrets in MCP config
  • Run ovp2 mcp --vault-root "$OVP_VAULT_ROOT" (see root mcp.json)
  • After content changes, operators may need ovp2 index before search/ask quality recovers
  • Keep ops conventions in skills + docs/ops/; do not casually delete operator docs

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free