vault-inbox
Triage a .vault/inbox/ drop zone into raw/ stubs or wiki/summaries links, per that vault's own schema. Creates stubs only; never spawns deep-extraction subagents (that's /vault-summarize's job).
- License 许可
- MIT
- 最近更新
- 2026-11-05
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- vault-inbox
- metadata
- { "author": "salomepoulain", "source": "makery-bakery" }
- description
- Triage a .vault/inbox/ drop zone into raw/ stubs or wiki/summaries links, per that vault's own schema. Creates stubs only; never spawns deep-extraction subagents (that's /vault-summarize's job).
03 SKILL.md 正文
/vault-inbox: triage the vault inbox
Preflight: confirm the vault (do this before anything else)
- Look for
.vault/at the repo root (it may be a symlink into a shadow dir, that's fine, follow it). If the user names a specific vault/path, use that instead. - If no
.vault/exists, stop here. Don't create one, don't guess a structure, don't treat some other folder as a vault; scaffolding a vault is a separate concern (thevaultmakery station's job, not this skill's). Tell the user there's no vault and ask how they want to proceed. - Read
<vault>/<PREFIX>-schema.md; every vault has exactly one, and it's the concrete source of truth for that specific vault. The prefix is whatever that file uses (e.g.sol-); don't assume it. - From the schema, actually understand what the vault is composed of before touching anything:
its layers (
raw/ground-truth sources + stubs,wiki/summaries/AI-written extractions,wiki/atomic/human-only notes,wiki/maps/MOCs/mastery dashboards,wiki/lessons/teaching transcripts where present,inbox/the unsorted drop zone), which of those this skill may touch, and its hard rules (no unconfident writeback, no AI writes towiki/atomic/, etc.), not just enough to satisfy a frontmatter format.
For each item currently in <vault>/inbox/ (skip .keep), decide where it belongs, per the
schema's "Processing the inbox" section:
-
Genuinely a new source (a document/transcript/book to treat as ground truth) →
- Move the file into
raw/, renamed to<PREFIX>-<kebab-case-title>.<ext>(strip junk like download-site hashes/suffixes from the original filename). - Write a lightweight stub note
raw/<PREFIX>-<slug>.md:--- type: source title: "Human-readable title" description: "One-line description of what this source covers and why it's here" resource: <PREFIX>-<slug>.<ext> tags: [<PREFIX>, <a few topic tags>] --- Source: ![[<PREFIX>-<slug>.<ext>]] - Also add a
## Contentssection (see the schema's "Table of contents" section for the exact format); read enough of the source's front matter to get its real chapter/section structure with page numbers. This is cheap (a handful of pages) and doesn't require the full deep read that/vault-summarizedoes, so do it inline yourself, no subagent. - If the source is clearly assessment material (a past exam, problem set, homework, quiz)
rather than expository/conceptual reading, tag it distinctly (add an
examtag alongside the topic tags). It's still filed inraw/like any other source; the tag is just sovault-teachcan find and calibrate lessons against it specifically. - Do NOT read the rest of the source and do NOT write anything into
wiki/summaries/; that's/vault-summarize's job, on purpose, so a big inbox drop doesn't silently trigger a huge background read.
- Move the file into
-
An extraction/summary of something already in
raw/→ write it intowiki/summaries/directly (it's already synthesized, no need to defer), following the schema's frontmatter and hub-linking rules. -
Too thin to confidently place (a stray thought, ambiguous screenshot, not enough context) → leave it in
inbox/, don't guess, and ask the user about it in your final report. -
Never
wiki/atomic/: human-written only. Surface it back instead.
Once an item is triaged (moved, or explicitly discarded as noise with the user's OK), remove it
from inbox/.
Bookkeeping (do this yourself, no subagents needed for triage)
- Update
<PREFIX>-index.md: add one line per newraw/andwiki/summaries/entry under the right heading. - Append one entry to
<PREFIX>-log.md:## [YYYY-MM-DD] ingest | inbox batch (N items)with a short list of what got filed where.
Folder guardrail
If any of this triage work is ever delegated to a subagent, it must be scoped to ONLY
inbox/, the one raw file/stub it's placing, and wiki/summaries/ for direct-summary items;
never allowed to browse Downloads, other drives, the web, or other vault folders looking for
"better" material on its own initiative. See /vault-summarize's guardrail for why this is a
hard rule, not a suggestion.
Report back
List what got filed where (new raw sources with their tags, any direct-summary items), and flag
anything left in inbox/ because it was too thin; ask the user about those explicitly. Mention
that wiki/summaries/ deep-extraction hasn't run yet and point at /vault-summarize for that.
04 同仓库更多 Skills
writing-for-agents
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
write-mastery-website
Turn a mastery chapter into a clickable website (one HTML page published as an artifact) that looks like the LaTeX PDF. Solutions sit behind a blue bar, hints open one at a time, every solution line has a "why" toggle, MC options can be checked, and each exercise has a finished circle and a flag. Use when the user asks for the website, HTML or clickable version of a chapter, or for /write-mastery-website. The chapter content itself is written with write-mastery-chapter.
write-mastery-chapter
Use when authoring a new theory-then-practice study chapter for any subject as a LaTeX PDF (with figures and predict-the-picture exercises), or when revising a chapter this skill previously produced because a specific section was confusing during study.
wizard
Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.