When to Consult OVP

SkillSearch

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.

Use When to Consult OVP in Claude, ChatGPT or Ahel Desktop

Free. Sign in, add When to Consult OVP and connect your AI. About a minute.

Then ask your AI: use the When to Consult OVP skill

Details

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Account requirements not reviewed. Check the skill instructions before use; Ahel provides instructions and does not run this skill.

No other account needed.

Add Ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.

When to Consult OVPStart free

The instructions your AI receives, as published by fakechris/obsidian_vault_pipeline in skills/when-to-consult/SKILL.md and read by Ahel’s review.

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

Need	Skill / tool
Natural-language answer with verified receipts	`ask`
Structured inventory (kind/tag/date/entity)	`find`
Keyword / phrase hunt	`search`
Audit a `[claim:…]` citation	`claim`
Wiki-style theme narrative	`theme-page`
Pipeline pulse	`status`
Health / index problems	`doctor`
Save a note into the vault safely	`capture-drop`

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

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

Advanced