vault-summarize

Extracts raw vault sources into tagged concept-level summary notes via parallel subagents.

Updated Sep 8, 2026
One-click install
npx skills add https://github.com/salomepoulain/makery-stations --skill vault-summarize-salomepoulain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vault-summarize
Source: https://github.com/salomepoulain/makery-stations/tree/main/stations/claude/workbench/pantry/skills/vault-summarize
Command: npx skills add https://github.com/salomepoulain/makery-stations --skill vault-summarize-salomepoulain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning long source materials like books and PDFs into searchable, concept-level notes is slow and error-prone when done manually, and a single-pass summary often misses niche material. This Skill deep-reads each raw source in a knowledge vault and produces richly tagged, per-concept summary notes that future questions can resolve directly. ## Core Features & Use Cases - Parallel subagent extraction: Dispatches one agent per source to read the entire document (including large PDFs page-by-page) and write one note per distinct concept into wiki/summaries/. - Schema-driven vault rules: Reads the vault's schema file first to respect its layers, frontmatter format, and hard rules such as no AI writes to wiki/atomic/ and no unconfident writeback. - Strict folder guardrails and failure recovery: Confines each subagent to its assigned source and output files, and resumes or relaunches agents after rate-limit failures without restarting completed work. - Use Case: After running /vault-inbox to create raw stubs for three new books, run this Skill to generate dozens of tagged summary notes per book, then update the vault index and log centrally. ## Quick Start Run /vault-summarize on all raw sources in my vault that do not yet have summary notes.

Frequently Asked Questions about vault-summarize

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I summarize PDF sources into a knowledge vault automatically?

Run /vault-summarize after raw stubs exist; it dispatches one subagent per source to read the full PDF (up to 20 pages per Read call) and write one tagged note per concept into wiki/summaries/. Each note links back to its raw stub with page ranges.

What is the difference between vault-inbox and vault-summarize?

vault-inbox creates the raw stubs in the vault's raw/ layer, while vault-summarize deep-extracts those stubs into concept-level notes in wiki/summaries/. Run vault-inbox first; vault-summarize expects the stubs to already exist.

Does vault-summarize work without an existing .vault directory?

No. The skill stops immediately if no .vault/ directory exists at the repo root and asks how to proceed. Scaffolding a vault is a separate concern handled by the vault makery station, not this skill.

What happens when a summarization subagent hits a rate limit?

The skill first tries SendMessage to resume the agent where it left off. If the transcript expired, it relaunches a fresh agent that lists existing notes for that source and continues from there, never restarting completed work.

Can subagents access files outside their assigned source?

No. Each subagent is restricted to its assigned raw source file, its raw stub, and its own wiki/summaries/ output notes. It must not browse other folders, drives, or the web, and must report inadequate sources instead of substituting files.