Inbox Triage
Process all notes in 00-Inbox/: scan, classify by content, route to correct vault...
Install
npx skills add gnekt/My-Brain-Is-Full-Crew --skill inbox-triage -g -a claude-code -y- Repository
- gnekt/My-Brain-Is-Full-Crew3.9k
- Category
- Writing
- Updated
- 4mo ago
- License
- See repository
- Context cost
- Mediumabout 2,944 tokens
- Runs scripts
- No, instructions only
What it does
Process all notes in 00-Inbox/: scan, classify by content, route to correct vault location, update MOCs, extract action items, and generate a daily digest. Triggers: EN: "triage the inbox", "clean up the inbox", "sort my notes", "empty inbox", "file my notes", "process the inbox". IT: "smista l'inbox", "svuota l'inbox", "ordina le note", "triage dell'inbox", "processa l'inbox". FR: "trier la boite de réception", "vider l'inbox", "classer mes notes". ES: "clasificar la bandeja de entrada", "vaciar el inbox", "ordenar mis notas". DE: "Inbox sortieren", "Inbox leeren", "Notizen einordnen". PT: "triagem da inbox", "esvaziar a inbox", "organizar minhas notas".
Vault Path Resolution
Read Meta/vault-map.md (always this literal path) to resolve folder paths. Parse the YAML frontmatter: each key is a role, each value is the actual folder path. Substitute only the vault-role tokens listed in the table below, do NOT substitute other {{...}} patterns (like {{date}}, {{Name}}, {{YYYY}}, {{MM}}, {{N}}, {{ISO timestamp}}, etc.), which are template placeholders.
If vault-map.md is absent: warn the user once, "No vault-map.md found, using default paths", then use these defaults:
| Token | Default |
|---|---|
{{inbox}} | 00-Inbox |
{{projects}} | 01-Projects |
{{areas}} | 02-Areas |
{{resources}} | 03-Resources |
{{archive}} | 04-Archive |
{{people}} | 05-People |
{{meetings}} | 06-Meetings |
{{moc}} | MOC |
{{meta}} | Meta |
If vault-map.md is present but a role is missing: warn the user, "vault-map.md does not define [role]. What folder should I use?", and wait for their answer before proceeding.
Inbox Triage, Intelligent Inbox Processing & Filing
Always respond to the user in their language. Match the language the user writes in.
Process all notes sitting in {{inbox}}/, classify them, move them to the correct vault location, create wikilinks, and update relevant MOC files. This is the daily housekeeping workflow that keeps the vault clean and navigable.
User Profile
Before processing any notes, read {{meta}}/user-profile.md to understand the user's context, active projects, and preferences. Use this to make better filing decisions.
Inter-Agent Coordination
You do NOT communicate directly with other agents. The dispatcher handles all orchestration.
When you detect work that another agent should handle, include a ### Suggested next agent section at the end of your output. The dispatcher reads this and decides whether to chain the next agent.
