inbox-triage
Skill2 starsChanged 4 months agoMITView on GitHub
Process 01 Inbox: discard, park as pending, or file into the PARA structure.
52 other projects use a version of this.
Adopted by
Most recently taken up by
- chatmaxima-com/chatmaxima-skillstheir own version, first seen Nov 8, 2026
- itsryanarmani/skillstheir own version, first seen Nov 8, 2026
- reply-team/jason-aitheir own version, first seen Nov 8, 2026
- pooriaarab/skillstheir own version, first seen Nov 7, 2026
- digitalgym/aipathway-standardstheir own version, first seen Nov 4, 2026
- kesslernity/awesome-copilot-cowork-skillstheir own version, first seen Nov 3, 2026
Used with
Projects with it also use aeon-update, auto-workflow and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
aaronjmarsSkillaeon-update
Pull framework updates from the upstream Aeon repo into this instance - 3-way merges canon's new commits into a PR, never clobbering operator config.
Also in 4 projects that use this
- aaronjmarsSkill
auto-workflow
Two-mode aeon.yml workflow builder - analyze inspects URLs and emits a tiered, signal-verified skill-enablement plan plus an aeon.yml diff; enable flips slugs to enabled:true and opens a PR.
Also in 4 projects that use this
- +10 more from aaronjmars
Other versions52 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 52
- gnekt/My-Brain-Is-Full-Crew★ 3.9ksame name
- aaronjmars/aeon★ 789same name
- aeonfun/aeon★ 789same name
- QuixiAI/agi-memory★ 623same name
- QuixiAI/Hexis★ 623same name
- microsoft/cat-agent-skills★ 101same name
- latour-ai/skills★ 69same name
- kesslernity/awesome-copilot-cowork-skills★ 45same name
- GTMify/aigtm★ 25same name
- aaronjmars/miroshark-aeon★ 20same name
42 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- daily-noteSkill
- vault-healthSkill
- vault-inventorySkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 5 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 45 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use this skill whenever 01 Inbox/ has one or more notes waiting to be processed — at the start of a session, when the user asks to clean up …
- Distinctive: line 17
If the user chooses discard: confirm the exact file, then delete it.
- Very specific: line 18
If the user chooses pending: rename the file to Pending - <topic>.md and restructure it with three sections: ## Source (where the idea came …
- Distinctive: line 21
After processing all notes in the batch, commit the changes with a short, descriptive message and push.
- Distinctive: line 25
Never delete a note without asking the user first, even if it looks obviously obsolete.
- Very specific: line 26
Never automatically move a processed note into 06 Archive/ — archiving always requires an explicit, separate request from the user.
- Distinctive: line 27
Never file a note into a PARA folder without the user's confirmation of the destination.
- Distinctive: line 28
Keep each note atomic: if a single inbox note contains multiple unrelated ideas, split it before filing.
“Common” is measured: kept by at least 6 in 10 of the 45 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
When to use
Use this skill whenever 01 Inbox/ has one or more notes waiting to be processed — at the start of a session, when the user asks to clean up the inbox, or any time a quick capture needs to find a permanent home.
Steps
- List every file currently in
01 Inbox/. - For each note, read its content, then ask the user what to do with it. Offer exactly three options:
- Discard — the note is no longer needed.
- Pending — the idea is worth keeping but isn't ready to be filed yet.
- File — the note is ready to move into the PARA structure (
02 Projects,03 Areas, or04 Resources).
- If the user chooses discard: confirm the exact file, then delete it.
- If the user chooses pending: rename the file to
Pending - <topic>.mdand restructure it with three sections:## Source(where the idea came from),## Analysis(what it is and why it matters),## Next step(the concrete next action). Leave it in01 Inbox/. - If the user chooses file: move the note into the correct destination folder, and set its YAML frontmatter (
tags,status,date) to match the target area's conventions. When the destination is a project or area folder, the note needs that folder's tag alongside its type tag — take the tag from the register inAGENTS.mdinstead of deriving one from the folder name, and add a row to that register if the folder has no entry yet. - Whatever the choice (pending or file), retrofit any missing frontmatter (
tags,status,date) — quick captures often arrive without any. - After processing all notes in the batch, commit the changes with a short, descriptive message and push.
Rules
- Never delete a note without asking the user first, even if it looks obviously obsolete.
- Never automatically move a processed note into
06 Archive/— archiving always requires an explicit, separate request from the user. - Never file a note into a PARA folder without the user's confirmation of the destination.
- Keep each note atomic: if a single inbox note contains multiple unrelated ideas, split it before filing.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.