tab-setup
Skill82 starsChanged 42 days agoMITView on GitHub
Set a unique color and name for this Claude Code tab based on the current working directory. Use "all" to recolor and relabel every active session at once.
In this repository27 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ai-reviewSkill
- brieflySkill
- commit-batchingSkill
- commit-batchSkill
- create-alertSkill
- disclose-projectSkill
- discloseSkill
- evolve-claude-mdSkill
- figure-reviewSkill
- grillingSkill
- grill-meSkill
- handoffSkill
- lit-reviewSkill
- overbakedSkill
- pathfinderSkill
- pickupSkill
- recover-sessionsSkill
- repo-initSkill
- retroSkill
- reviewer-2Skill
- slack-messageSkill
- spot-aiSkill
- unstaleSkill
- worklogSkill
- write-new-skillSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
If $ARGUMENTS is update, pull the latest skill from its repo and re-install it:
- Very specific: line 27
If $ARGUMENTS is all, run the bulk sync:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
If $ARGUMENTS is update, pull the latest skill from its repo and re-install it:
bash ~/.claude/skills/tab-setup/scripts/update.shReport whether it updated (and from/to which commit) or was already current. Note that changes take effect on the next Claude session.
If $ARGUMENTS is all, run the bulk sync:
bash ~/.claude/skills/tab-setup/scripts/sync-all.shReport the output exactly as returned (list of sessions with their assigned colors and TTYs). Renames inject automatically with a short delay — no further action needed.
Otherwise, set up this session's tab:
bash ~/.claude/skills/tab-setup/scripts/setup.sh "${CLAUDE_SESSION_ID}" $ARGUMENTSThe script output is one line: color=<name> name=<tab-name>. Report to the user: "Tab set up: <color> / <name>". Color applies immediately; /color and /rename fire automatically in ~4 seconds.
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.

