Individual skill
inbox-zero
Triage a user inbox across email, Slack, LinkedIn, and Swan. Use for inbox sweeps where the agent should archive obvious noise, draft replies, and return a single summary of items needing attention.
skills/ido-goldberg/inbox-zero/SKILL.md
Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 237
- Repository last updated
- Oct 20, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 5,247 bytes
Read excerpt
## The four-bucket model
For each item the agent encounters, exactly one of these:
| Bucket | When | What the user sees |
|---|---|---|
| **1. Auto-archive** | Obvious noise (newsletters, mass mailers, status alerts), items already handled by someone else, items needing no action | One-line FYI in the batched summary, always with a reason |
| **2. Auto-handle** | The agent can fully complete the work itself — mark a CRM task done, schedule a follow-up reminder, archive after the other side already replied | One-line FYI in the batched summary |
| **3. Draft → approve** | A reply is needed | Reviewed one by one in the batched output |
| **4. Park** | Ambiguous, or the user's judgment is required | Left in inbox with a one-line reason |
## Steps
1. **Sweep all connected surfaces.** Pull unread / unactioned items from email, Slack DMs, LinkedIn DMs, the Swan inbox, and the CRM task queue. Count them. If above ~30, switch to `swan-execute-code` — load the inbox snapshot into a frame and process in passes.