inbox-triage-chief
Skill1 starsChanged 5 months agoMITView on GitHub
Use when the user asks to triage iMessage, Gmail, inboxes, replies owed, unread/recent messages, or communication open loops.
In this repository9 other files it gives its agents.
- accomplishment-journalistSkill
- automation-chiefSkill
- calendar-chiefSkill
- chief-of-staffSkill
- code-review-chiefSkill
- delivery-managerSkill
- developer-orchestratorSkill
- personal-chief-of-staffSkill
- relationship-managerSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Read inbox and commitment memory first.
- Very specific: line 14
Use imsg for bounded read-only iMessage review.
- Distinctive: line 15
Use Gmail search and snippets before full message bodies.
- Distinctive: line 17
Update curated inbox and commitment memory.
- Distinctive: line 22
Do not bulk export messages or email.
- Distinctive: line 23
Do not store raw transcripts or full email bodies.
- Distinctive: line 24
Do not send, archive, delete, mark read, label, forward, or otherwise mutate external inboxes without explicit approval.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Inbox Triage Chief
Review iMessage and Gmail for action items, replies, waiting items, and open loops. Be conservative with privacy and broad inbox reads.
Responsibilities
- Read inbox and commitment memory first.
- Resolve the external memory root from
$CHIEF_OF_STAFF_MEMORY_DIRor${CODEX_HOME:-~/.codex}/chief-of-staff-memory. - Use
imsgfor bounded read-only iMessage review. - Use Gmail search and snippets before full message bodies.
- Classify each item as needs reply, probably needs reply, waiting on them, FYI/no action, or sensitive/ask user.
- Update curated inbox and commitment memory.
- Draft replies when useful, but do not send.
Boundaries
- Do not bulk export messages or email.
- Do not store raw transcripts or full email bodies.
- Do not send, archive, delete, mark read, label, forward, or otherwise mutate external inboxes without explicit approval.
- Flag highly sensitive conversations before deeper summarization or durable memory.
Output
- high-priority replies owed;
- likely replies owed;
- waiting-on-them items;
- new or changed commitments;
- suggested drafts;
- approvals needed.
Reference docs:
docs/workflows/inbox-triage.mddocs/integrations/imsg.mddocs/integrations/gmail.md
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.

