Inbox Triage
Process freeform notes and dropped files in {VAULT_PATH}/Inbox.md and {VAULT_PATH}/Inbox_Files/ — classify each item and file it into the correct place in the vault. Use when the user says "process my inbox," "sort my notes," or /inbox-triage.
Install
$ agentstack add skill-cormff-claude-code-playbook-inbox-triage ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-cormff-claude-code-playbook-inbox-triage) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Inbox Triage
An inbox exists so that a fleeting thought or a dropped file doesn't have to be filed correctly at the moment it's captured. This skill does the filing later, in a batch.
Step 1 — Read the Inbox
Read Inbox.md (freeform text notes) and list the contents of Inbox_Files/ (dropped documents, audio, images, links).
Step 2 — Classify Each Item
For each item, decide:
- Which area/project it belongs to (see [
vault-format](../../layer-0-foundation/vault-format/SKILL.md) for the area/project structure). - What kind of note it becomes — an addition to an existing note, a new topic note, a new project, or a task (route tasks to the source file used by [
task-list](../task-list/SKILL.md)). - Whether it needs pre-processing before it can be filed — e.g. a recorded audio file needs a transcript/summary before it's useful as a note; a long document needs a summary rather than being pasted in whole.
Step 3 — File It
Move or write the content into the correct location following vault-format conventions (frontmatter, naming, navigation link, hub update). Once filed, remove the raw item from the Inbox — the inbox should end each triage pass empty or holding only genuinely unresolved items.
Step 4 — Confirm
Give a short summary of what was filed where, so anything mis-classified can be corrected immediately rather than discovered later.
Ambiguous items
If an item's destination genuinely isn't clear (not enough context to tell which project it belongs to), ask rather than guessing — a wrongly-filed note is often harder to find later than one left in the inbox.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: cormff
- Source: cormff/claude-code-playbook
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.