agentleFS
sschemelsschemel/second-brain-starter/.agents/skills/tab-color/SKILL.md

tab-color

Skill0 starsChanged 16 days agoMITView on GitHub

Changes the background color of the iTerm2 session this agent is running in (not whichever tab has focus) as a visual cue for which project or context that session is working on (e.g. /tab-color cloudflare orange, /tab-color reset). Use when the user asks to change the tab, session, background, or terminal color, or names a brand or theme color for their terminal. Not for editor or syntax themes.

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
  1. Very specific:

    Run set-color.sh, which sits next to this SKILL.md.

    line 17
  2. Very specific:

    If the skill is linked globally (for example ~/.claude/skills/tab-color), use that folder's copy of the script instead.

    line 21

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Tab Color

Requested: $ARGUMENTS

Color this agent's own session, never "the current session": that's whichever tab has focus, which may be a different project. Agent shells aren't attached to the visible pty, so ANSI/OSC escape sequences never reach the window. The bundled script finds this session's tty and sets that iTerm2 session's color through AppleScript.

  1. Resolve the color: a brand ("Cloudflare orange", "AWS blue"), a theme, a project name (pick a stable, distinct hue for it), or reset/default (use 0 0 0). Nothing records past colors, so if asked for "the one we had before", say there's no record and offer a fresh pick rather than guessing silently.
  2. Convert it to a dark, readable 16-bit RGB (0–65535 per channel). Keep every channel under about 15000 so light text stays legible. Examples: dark orange 15000 5000 0, dark red 14000 1500 1500, dark blue 0 4000 10000.
  3. Run set-color.sh, which sits next to this SKILL.md. From the vault root:
    bash ".agents/skills/tab-color/set-color.sh" R G B
    If the skill is linked globally (for example ~/.claude/skills/tab-color), use that folder's copy of the script instead.
  4. Relay the script's one-line output. If it exits non-zero (no terminal, iTerm2 not running, or the session lives in another terminal such as Cursor's), say so plainly and don't claim success.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.