Inbox triage
Sort a mailbox, channel or queue into what needs a person today, this week, or never, with a reason and a suggested action for each.
In Lobstack: Skills › Library › Add
What your agent will do.
Email, messages or tickets have piled up and somebody wants to know what actually needs them.
- 01
Fix the scope before reading: which inbox or channel, and since when. Default to unread items from the last three working days, and say so.
- 02
Read each item far enough to know who is asking for what. The ask is often in the last paragraph, not the subject line.
- 03
Put every item in one bucket:
- Today: a direct question, a deadline within two days, a customer or manager waiting, money or access at stake.
- This week: needs a reply, but nothing breaks if it waits.
- FYI: worth knowing, no action.
- Ignore: newsletters, notifications, threads you are only copied on.
- 04
For Today and This week, one line each: who, what they want, and the reply or action you suggest.
- 05
Report Ignore as counts by kind of sender. Nobody needs sixty lines saying "ignore".
- 06
Offer to draft replies for the Today bucket. Draft, never send, and never archive, label or delete without asking — a triage that silently files mail is worse than none.
Short enough to read in two minutes, most urgent first.
The whole SKILL.md: 35 lines of Markdown.
Add it in the app from Skills › Library, or copy it and paste it into Skills › Add a skill.
---name: inbox-triagedescription: "Sort a mailbox, channel or queue into what needs a person today, this week, or never, with a reason and a suggested action for each."metadata: title: "Inbox triage" category: personal tags: [email, triage]--- ## When to use this Email, messages or tickets have piled up and somebody wants to know whatactually needs them. ## How 1. Fix the scope before reading: which inbox or channel, and since when. Default to unread items from the last three working days, and say so.2. Read each item far enough to know who is asking for what. The ask is often in the last paragraph, not the subject line.3. Put every item in one bucket: - Today: a direct question, a deadline within two days, a customer or manager waiting, money or access at stake. - This week: needs a reply, but nothing breaks if it waits. - FYI: worth knowing, no action. - Ignore: newsletters, notifications, threads you are only copied on.4. For Today and This week, one line each: who, what they want, and the reply or action you suggest.5. Report Ignore as counts by kind of sender. Nobody needs sixty lines saying "ignore".6. Offer to draft replies for the Today bucket. Draft, never send, and never archive, label or delete without asking -- a triage that silently files mail is worse than none. Short enough to read in two minutes, most urgent first.
- Personal
Meeting notes to action items
Turn a meeting transcript or rough notes into decisions, owned actions with dates, and open questions, and nothing else.
SKILL.md · App - Personal
Daily brief
A short morning brief: what needs the person today, what changed overnight, and what the agents finished — each with a link.
SKILL.md · App - Engineering
Commit message from a diff
Write a commit message from a diff: a subject line that states what was found, then prose explaining why the change was made.
SKILL.md · App - Engineering
Triage a failing build
Triage a red CI run: find the first real failure, attribute it to a change, and say whether the code is wrong or the runner was.
SKILL.md · App - Engineering
Review what a linter cannot
Review a change for what a linter cannot see: whether it is correct, what it breaks elsewhere, and which parallel list it forgot to update.
SKILL.md · App - Writing
Release notes from merged work
Turn merged work, or a thread about it, into release notes written for the person installing the version rather than the person who built it.
SKILL.md · App