Skip to content
Back to skills

Vault Synthesis

ASecurity

Use when answering "what do I know about X" from the whole vault — a grounded, cited topic synthesis across all notes regardless of type, with contradictions and gaps named.

  • 2 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added September 4, 2026
ai-agents

Works with

  • claude code
  • cli
  • mcp

Security analysis

A100/100

Scanned September 24, 2026

npx -y skills add cavi-ai/obsidian-agent --skill vault-synthesis --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Vault Synthesis?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Vault Synthesis
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/cavi-ai-vault-synthesis/badge)](https://www.skillsdirectory.com/skills/cavi-ai-vault-synthesis)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: vault-synthesis
description: Use when answering "what do I know about X" from the whole vault — a grounded, cited topic synthesis across all notes regardless of type, with contradictions and gaps named.
---

# Vault synthesis

Answer a question from the vault itself — grounded, cited, honest about gaps and
contradictions. Not a general-knowledge essay.

**REQUIRED SUB-SKILL:** obsidian-agent:vault-grounding

## Process

1. **Gather.** Run
   `obsidian vault=<vault> search query=<topic> format=json`. Read the most
   relevant hits in full with `obsidian vault=<vault> read path=<path>`, then
   follow `obsidian vault=<vault> backlinks path=<path> format=json` and
   `obsidian vault=<vault> links path=<path>` to find connected notes the
   search missed. Read those notes before using them.
2. **Extract claims, attributed.** As you read, collect each claim with its
   source note. Every claim carries a `[[Source Note]]` citation.
3. **Dedupe and group.** Merge claims that repeat across notes; group by theme.
4. **Surface contradictions.** When notes disagree, say so explicitly with both
   citations — don't silently pick one. Contradictions are signal.
5. **Name the gaps.** State what the vault does *not* cover on this topic.
6. **Output.** Return portable Markdown, leading with the single most important
   takeaway. Every claim stays cited to its note.

## Hard requirements

- No claim about the topic without a `[[note]]` citation behind it.
- If the vault is thin on the topic, say so — do not pad with outside knowledge.
- A "Contradictions" and a "Gaps" section whenever either exists.

## Common mistakes

- Answering from training knowledge instead of the vault.
- Only reading search hits, never following links/backlinks.
- Uncited claims; silently resolving conflicting notes.

## Companion bridge (optional)

If tools from the `obsidian-vault` MCP server are available (Claude Code
shows them as `mcp__obsidian-vault__<tool>`), use them for the steps below;
otherwise follow the CLI steps above. Never require them.

- Gather (search): `vault_search` query=<topic> — replaces the initial `search` call in step 1.
- Gather (widen): `related_notes` path=<path>, limit 15 — supplements the backlinks/links follow-up in step 1.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.