inbox-cleanup
Skill2 starsChanged 31 days agoLicence not identifiedView on GitHub
Reviews the last two months of a Gmail inbox read-only, through a Gmail connector or MCP server, browser automation (Claude in Chrome, Codex's browser), or both, and builds a private dashboard page that explains the mailbox. It charts mail per day by kind (people, newsletters, promotions, notifications), when mail arrives, what gets opened, the biggest senders, newsletters, the unread backlog, big attachments and likely phishing, adds the agent's own insights, then gives a declutter plan with Gmail searches and filter suggestions that the user ticks to approve. Use when the user asks to clean up, declutter, audit or review their Gmail or inbox, find what to unsubscribe from, see which emails they never open, cut email noise or free Gmail storage. Never sends, deletes, archives, unsubscribes or creates filters without the user's approval of that specific action. Not for writing or answering email, and not for mailboxes other than Gmail.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- HybridAIOne/hybridclawtheir own version, first seen Oct 13, 2026
- sarthakguptadev/feedsheriff-mcptheir own version, first seen Oct 2, 2026
- vellum-ai/vellum-assistanttheir own version, first seen Jul 8, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- vellum-ai/vellum-assistant★ 1.5ksame name
- HybridAIOne/hybridclaw★ 159same name
- sarthakguptadev/feedsheriff-mcp★ 1same name
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.
In this repository12 other files it gives its agents.
- site/llms-full.txtllms.txt
- site/llms.txtllms.txt
- backup-checkupSkill
- bookmark-cleanupSkill
- calendar-fixerSkill
- desktop-iconsSkill
- disk-space-reportSkill
- drive-auditSkill
- momSkill
- rename-documentsSkill
- subscription-auditSkill
- tidy-foldersSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 3 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.
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.