vault-inbox

Triages a vault inbox drop zone into raw source stubs and wiki summaries per the vault schema.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Unsorted drop zones in a personal knowledge vault accumulate files with no clear home, and filing them by hand is tedious and error-prone. This Skill reads the vault's own schema and files each inbox item into the correct layer without guessing or overstepping. ## Core Features & Use Cases - Schema-driven triage: Reads the vault's <PREFIX>-schema.md first and follows its rules for layers, naming, and hard constraints (e.g., never writing to wiki/atomic/). - Source filing with stubs: Moves genuine new sources into raw/, renames them to <PREFIX>-<slug> form, and writes lightweight stub notes with frontmatter and a table of contents. - Direct summary placement: Writes already-synthesized extractions straight into wiki/summaries/ per the schema's frontmatter and hub-linking rules. - Bookkeeping and reporting: Updates the vault index and log, then reports what was filed and flags ambiguous items left in the inbox. - Use Case: After dropping a batch of downloaded PDFs, transcripts, and stray notes into .vault/inbox/, run this Skill to have each item filed, stubbed, tagged, and logged, with uncertain items surfaced back for your decision. ## Quick Start Triage everything currently in my vault's inbox according to its schema and tell me what you filed where.

Frequently Asked Questions about vault-inbox

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

FAQPage Schema
How do I organize an Obsidian vault inbox automatically?

Point the Skill at your vault's inbox folder and it reads the vault's schema file, then files each item into raw/ with a stub note or into wiki/summaries/ for already-synthesized extractions. Ambiguous items stay in the inbox and are reported back to you.

What happens if there is no .vault directory in my repo?

The Skill stops immediately and tells you no vault exists. It does not create a vault, guess a structure, or treat another folder as a vault, since scaffolding a vault is a separate concern handled elsewhere.

Does vault-inbox read and summarize full source documents?

No. It only reads enough front matter to build a table of contents for the stub note. Deep extraction into wiki/summaries/ is deliberately deferred to the separate /vault-summarize skill so large inbox drops stay cheap.

Can the Skill write notes into wiki/atomic/?

No. The vault schema marks wiki/atomic/ as human-written only, and the Skill treats that as a hard rule. Content that belongs there is surfaced back to the user instead of being filed automatically.

How are exam or assessment files handled during triage?

Assessment material such as past exams, problem sets, and quizzes is still filed in raw/ like any other source, but it receives an additional exam tag so downstream teaching workflows can find and calibrate against it.