inbox-triage
Skill617 starsChanged 10 months agoMITView on GitHub
Review an inbox, propose a safe triage plan, and apply only the email actions the user approves
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 40 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
List before reading: Use message metadata to identify likely high-value threads.
- Distinctive: line 22
Apply the chosen batch: Only after the user chooses, apply labels, archive, or mark spam to the exact messages approved.
- Distinctive: line 28
Never permanently delete during ordinary triage.
- Distinctive: line 29
Never infer that a newsletter is spam or that silence means approval.
- Distinctive: line 32
If the account is disconnected or a provider action is unavailable, preserve the proposed plan and give the exact connection or manual next …
“Common” is measured: kept by at least 6 in 10 of the 40 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
Inbox Triage
Reduce inbox load while keeping classification, replies, and destructive actions under the user's control. Use email-digest instead when the user wants only a summary or memory ingestion.
Workflow
- Set scope. Confirm the account when more than one is connected, then honor the requested folder, query, date range, or message limit. Default to a small recent inbox sample rather than scanning all mail.
- List before reading. Use message metadata to identify likely high-value threads. Read only enough candidate messages to classify them accurately; do not bulk-read the whole mailbox.
- Classify with reasons. Group messages into: reply needed, task or deadline, waiting/reference, safe archive, likely spam, and uncertain. Include message IDs or unambiguous sender/subject labels so the proposed actions are inspectable.
- Show the plan first. Present counts and the proposed action for each thread. Keep uncertain messages out of action batches and ask about them.
- Apply the chosen batch. Only after the user chooses, apply labels, archive, or mark spam to the exact messages approved. Report successes and failures per message.
- Handle replies separately. Draft a reply, show recipients, subject, and body, then send only after explicit approval. A request to triage is not permission to send.
- Capture tasks deliberately. Suggest tasks for real commitments. Create them in the local backlog, Todoist, or Asana only after the user chooses the destination and content.
Control and Failure Boundaries
- Never permanently delete during ordinary triage. Use trash only after an explicit request; permanent deletion requires unmistakable, message-specific authorization.
- Never infer that a newsletter is spam or that silence means approval. Archive, spam, labels, replies, and tasks are separate choices.
- Respect the configured Gmail memory policy. Do not store email-derived content when it says
forget; ask before storage when it saysask; summarize rather than storing raw bodies. - Gmail connection is not autonomous permission. This skill is chat-only and runs because the user asked now.
- If the account is disconnected or a provider action is unavailable, preserve the proposed plan and give the exact connection or manual next step. Do not discard the useful read-only work.
Other versions47 projects use a version of this.
Word for word · 1
- QuixiAI/Hexis★ 617100% same
Edited · 0
None found.
Wrote their own version · 46
- gnekt/My-Brain-Is-Full-Crew★ 3.9ksame name
- aeonfun/aeon★ 782same name
- aaronjmars/aeon★ 776same name
- microsoft/cat-agent-skills★ 95same name
- latour-ai/skills★ 69same name
- kesslernity/awesome-copilot-cowork-skills★ 34same name
- GTMify/aigtm★ 25same name
- aaronjmars/miroshark-aeon★ 18same name
- Hassaan146/claude-skills★ 18same name
- MiroShark/miroshark-aeon★ 18same name
36 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.
Used alongsideProjects with it also use branded-deck-builder, cmo-reviewer 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.
kesslernitySkillbranded-deck-builder
Builds PowerPoint decks on the user's own company template and checks every slide against written brand rules (colours with hex codes, fonts, logo placement, banned visuals). Use when the user asks for a branded, on-brand, CI-compliant or corporate-template presentation, or wants a deck that follows company design guidelines. Confirms an outline first, then builds slide by slide and saves a DRAFT deck to OneDrive.
Also in 4 projects that use this
- kesslernitySkill
cmo-reviewer
Reviews a proposal, business case, deck or plan in character as a Chief Marketing Officer archetype, producing a structured DRAFT review document with a verdict, findings cited to specific passages, risks and five interrogation questions. Use when the user asks for a CMO review, a marketing executive's read on a document, or wants to pressure-test positioning, messaging, pricing or a launch plan before a real executive review.
Also in 4 projects that use this
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
- +9 more from kesslernity
In this repository42 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- audio-analysisSkill
- calendarSkill
- code-executionSkill
- connector-action-authorizationSkill
- core-memorySkill
- cost-reportSkill
- councilSkill
- crm-lookupSkill
- daily-briefingSkill
- delegationSkill
- email-digestSkill
- expense-captureSkill
- github-issuesSkill
- gmail-actionsSkill
- gmail-connector-setupSkill
- home-assistantSkill
- host-nodeSkill
- humanizerSkill
- image-genSkill
- integration-connector-setupSkill
- knowledge-ingestSkill
- meeting-follow-upSkill
- meeting-prepSkill
- memory-exchangeSkill
- notionSkill
- operationsSkill
- outreachSkill
- personal-notesSkill
- researchSkill
- self-inspectionSkill
- self-reflectionSkill
- skill-authoringSkill
- speechSkill
- spotifySkill
- travel-prepSkill
- trelloSkill
- twitter-x-actionsSkill
- twitter-x-connector-setupSkill
- weatherSkill
- weekly-reviewSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.