Install any skill in seconds. Free to start, no credit card required.
Get Started Free →inbox-cleanup
Run a high-recall, multi-pass email inbox cleanup. Pattern-based subject queries catch 25x more archivable email than sender scans alone. Includes urgency triage, classification signals, and post-cleanup filter setup.
Passed 9 of 22 test cases with the skill, and 1 of 22 without it.
8 fixed1 passed either way14 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
The instructions your model reads when the skill loads.
A playbook for large-scale email inbox cleanup. The core insight: sender-based scans are low-recall. Subject/body pattern queries catch 25x more archivable email. This skill is a multi-pass pipeline built around that insight.
Works with any connected email provider. Adapt query syntax to whatever the provider supports — the strategy (what to search for, how to decide what to archive) is universal.
Gmail is a required integration. It's declared via
includes: ["gmail"]in the frontmatter so it loads synchronously on activation, not lazily after the preferences form. Load/confirm the Gmail integration the moment this skill activates — before Phase 1 — so a missing or unauthorized connection surfaces up front rather than mid-cleanup.
Do this before touching anything. Ask the user:
1. Aggressiveness level
2. Age threshold Archive everything older than X days? Common choices: 30 / 60 / 90 days. Or no age filter.
First-run scope: On first invocation, scope to last 30 days or top 3 noise patterns, whichever surfaces faster. Show result, offer to expand. Prove the approach on a fast, visible slice before draining the whole backlog.
3. VIP senders to protect Ask: "Are there any senders that might look like cold outreach but you actually care about? Think: specific individuals at investors, advisors, your lawyer, accountant, recruiters you're actively working with."
Build an explicit keep list. Do not archive anything matching it, ever, regardless of aggressiveness.
4. Categories to confirm before archiving These need a sample + explicit approval before bulk action:
test cases passed, vs 1 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.