Organize Tabs
Skill35 starsChanged 4 days agoMITView on GitHub
Clean up tab chaos: dedupe, group by site, and report. 1. Review OPEN TABS from the page context. Build an inventory: host → list of tabs (title + duplicate count). 2. Choose the mode from the user's intent: - "close duplicates" → organize_tabs with mode: "dedupe" - "group/organize" → organize_tabs with mode: "group" - "clean up" → dedupe first, then group, then report leftovers. 3. After the executor confirms, summarize what changed. - NEVER close a tab whose content is…
In this repository11 other files it gives its agents.
- Compare PricesSkill
- Deep ResearchSkill
- Extract DataSkill
- Fill FormSkill
- Find AlternativesSkill
- Manage BookmarksSkill
- Monitor PageSkill
- Read LaterSkill
- Save PageSkill
- Screenshot WalkthroughSkill
- Summarize PageSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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 29
After the executor confirms, summarize what changed.
- Distinctive: line 33
NEVER close a tab whose content is unique (documents, forms, carts).
- Distinctive: line 34
When unsure, group instead of close.
- Very specific: line 35
Prefer one organize_tabs call over many close_tab calls.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Organize Tabs
Clean up tab chaos: dedupe, group by site, and report.
Procedure
- Review OPEN TABS from the page context. Build an inventory: host → list of tabs (title + duplicate count).
- Choose the mode from the user's intent:
- "close duplicates" →
organize_tabswithmode: "dedupe" - "group/organize" →
organize_tabswithmode: "group" - "clean up" → dedupe first, then group, then report leftovers.
- "close duplicates" →
- After the executor confirms, summarize what changed.
Tool discipline
- NEVER close a tab whose content is unique (documents, forms, carts). When unsure, group instead of close.
- Prefer one
organize_tabscall over manyclose_tabcalls.
Answer format
Closed N duplicate tabs · Grouped M tabs into K groups
Remaining: <host> (×n), <host> (×n)…Mirror in data: { "closed": N, "groups": [...] }.
Verify before done
- Executor result confirms the reorganization.
- The summary matches the actual action count.
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.

