菜单
Set iTerm2 tab title and color to reflect the current work context. Only use this skill when the user explicitly asks: "set tab", "color tab", "label tab", "iterm", or "tag this". Never trigger proactively.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | iterm |
| description | Set iTerm2 tab title and color to reflect the current work context. Only use this skill when the user explicitly asks: "set tab", "color tab", "label tab", "iterm", or "tag this". Never trigger proactively. |
Set the iTerm2 tab title and color so the user can visually distinguish work contexts across tabs at a glance.
Run the setup script — it handles everything it can programmatically:
~/.claude/scripts/iterm-setup.sh
This is also triggered automatically by /update-wfk pull when iTerm2 is detected.
The script will report which manual steps remain (typically: restart iTerm2, confirm the Python API consent dialog, and verify the Title dropdown is set to "Session Name").
If you need to set things up by hand, here are the individual steps:
defaults write com.googlecode.iterm2 EnableAPIServer -bool true
Then restart iTerm2 and confirm the consent dialog.
mkdir -p ~/.claude/venvs
python3 -m venv ~/.claude/venvs/iterm2
~/.claude/venvs/iterm2/bin/pip install iterm2
Copy these files from WFK or another machine:
~/.claude/scripts/iterm-tab.sh # Tab color + title by work type
~/.claude/scripts/iterm-notify.sh # Flash tab when Claude is waiting
Make them executable:
chmod +x ~/.claude/scripts/iterm-tab.sh ~/.claude/scripts/iterm-notify.sh
Add to ~/.zshrc:
alias cld='claude --dangerously-skip-permissions --teammate-mode tmux'
Add to ~/.claude/settings.json:
{
"hooks": {
"Stop": [
{
"matcher": "",
"hooks": [
{
"type": "command",
"command": "~/.claude/scripts/iterm-notify.sh flash"
}
]
}
],
"UserPromptSubmit": [
{
"matcher": "",
"hooks": [
{
"type": "command",
"command": "~/.claude/scripts/iterm-notify.sh clear"
}
]
}
]
}
}
curl -sL -o /tmp/Spacedust.itermcolors \
"https://raw.githubusercontent.com/mbadolato/iTerm2-Color-Schemes/master/schemes/Spacedust.itermcolors"
open /tmp/Spacedust.itermcolors
# Then select it in Settings → Profiles → Colors → Color Presets
tab.async_set_title()) — the only method that persists while Claude Code is running, because Claude Code continuously resets the session name via OSC escape sequencesiterm-notify.sh flash → tab pulses gold 3x then stays gold. UserPromptSubmit hook fires iterm-notify.sh clear → resets to default color.| Script | Purpose |
|---|---|
~/.claude/scripts/iterm-tab.sh | Set tab color + title by work type |
~/.claude/scripts/iterm-notify.sh | Flash/clear tab for input notifications |
| Type | Color | RGB | When to use |
|---|---|---|---|
pickup | Steel blue | 78, 154, 190 | Loading or working on a PIC |
infra | Warm amber | 190, 120, 50 | Infrastructure, Docker, CI/CD, deployment |
feature | Forest green | 80, 160, 90 | New feature development |
bug | Muted red | 190, 60, 60 | Bug fixes, issue triage |
reset | Default | — | Clear color, return to neutral |
# Set color + title by work type
~/.claude/scripts/iterm-tab.sh <type> [title]
# Set title only (no color change)
~/.claude/scripts/iterm-tab.sh title "My Title"
# Set custom RGB color (no title change)
~/.claude/scripts/iterm-tab.sh color <r> <g> <b>
# Flash tab (waiting notification)
~/.claude/scripts/iterm-notify.sh flash
# Clear flash (return to default)
~/.claude/scripts/iterm-notify.sh clear
Examples:
~/.claude/scripts/iterm-tab.sh pickup "PIC - KB Migration"
~/.claude/scripts/iterm-tab.sh feature "Feature - Meeting Notes Pipeline"
~/.claude/scripts/iterm-tab.sh infra "Infra - SSL Renewal"
~/.claude/scripts/iterm-tab.sh bug "Bug - Auth Loop"
~/.claude/scripts/iterm-tab.sh reset "Vaults - Claude"
~/.claude/scripts/iterm-tab.sh title "Planning Session"
~/.claude/scripts/iterm-tab.sh color 150 80 200
pickup type, title = PIC nameType - Brief Description (e.g., Feature - Email Templates)The front door to the Pipeline Coordination system. One guided skill that doubles as installer + onboarder + meta-plan builder + first-handoff drafter + launcher. It scans a project's recent work for a goal and a candidate work-pile, sorts that pile WITH the operator, writes a coordination meta-plan PL and a first delegation handoff (HAN), installs the handoff-handling overlays into the create-note and pickup skills, teaches the three roles (orchestrator / coordinator / worker) in plain words, and prints exact launch instructions. Trigger on "meta-plan-init", "/meta-plan-init", "set up coordination", "set up the meta-plan", "bootstrap the pipeline coordination", "onboard me to the coordination system", "adopt my existing work into a meta-plan", or any request to stand up the coordinated-pipeline-execution layer for a project. Messy-work-adopt is the primary path; clean-start is the degenerate case.
Coordinator playbook for executing a delegation handoff issued by a meta-plan orchestrator. Auto-invoked by /pickup when it detects a delegation HAN (a `HAN - *.md` with `category: Handoff`, an `orchestrator_contact`, a `related_pl` pointing at a meta-plan, and `## Checkpoint log` + `## Clarification requests` sections) and this session is executing it. Also trigger when the operator says "coordinate this handoff", "I'm the coordinator", "run this HAN", "work the delegation". The coordinator is the top-level interactive instance the operator chats with: it stands up a workgroup of meta-plan-worker subagents, validates their deliverables, and posts LEAN progress to the HAN for the orchestrator. It does not own or edit the meta-plan.
Get oriented in the current project or Obsidian vault — read agent configs, guardrails, vault structure, and lessons learned. Use this skill at the start of any new session, after context compaction, when entering an unfamiliar project directory, or when the user says "orient", "get oriented", "what's the context here", "read the agents file", or "start up". Also trigger on /orient with no arguments. Even continued sessions count as new starts after compaction — always re-read the config chain.
Run a structured open-source landscape survey before designing or rebuilding a complex system. Six phases: bracket, discover (video + oracle + grounding doc), workspace (scratch clone), anchor read (manual, 1-2 closest peers), parallel deep-reads (team-dispatched), synthesis (single-worker comparative RE). Produces per-repo AREs + one comparative-analysis RE + grounding-doc cross-ref appendix; hands off to SD update and SPC drafting. Use whenever the user says "landscape survey", "deep-read these repos", "what should we borrow from X", "research before we spec", "evaluate candidates before the rebuild", "comparative source analysis", "what's the state of the art for [domain]", or invokes /landscape-survey. Also fires when the user points the assistant at a candidate set (a list of repos / libraries / approaches) and asks for a build plan before the SPC. The skill is the structural answer to "we built the system on marketing-page understanding and only discovered the failure mode after shipping."
Log work to the daily note AND project log. Use this skill when the user wants to record what they've been working on, says "log this", "log work", "add to worked on", "update the daily note", or wants to capture implementation progress. Always writes to both layers: daily note (human-readable) and PJL (agent-readable). Also trigger on "what did I work on" if the user wants to retroactively log work.
Load pickup documents (PICs) and resume work. Handles both single-PIC loading and full backlog triage. Use this skill when the user says "pickup", "pick up", "start of day", "what's on my plate", "what do I need to do", "get started", "load the pickup", "continue where I left off", "resume work", "triage pickups", "which pickups are easiest", "work through my pickups", "clear out pickups", "pickup backlog", "how many open pickups", "rank my pickups", "what's the quickest pickup to close", "batch my pickups", "group pickups by project", or points at a specific PIC document. Also trigger when the user opens a new session and says something like "ok what am I doing today" or "what was I working on".