Agent skill
loom-team-manager-pane-dead-on-spawn
Diagnose and fix Loom team manager pane dying immediately (tmux pane status 1).
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/loom-team-manager-pane-dead-on-spawn
Metadata
Additional technical details for this skill
- version
- 1
- created at
- 2026-01-29T09:27:53.279Z
- updated at
- 2026-01-29T09:27:53.279Z
SKILL.md
When To Use
loom team start <TEAM>succeeds, but manager pane shows dead (status 1) and capture output is empty.
Diagnose
- Confirm run exists:
loom team status <TEAM> --show-dead
- Capture manager:
loom team capture <TEAM> manager --lines 200 --header
- Open the capture metadata file under
.team/runs/<TEAM>/captures/*.jsonand check:pane.start_commandpane.current_commandpane.dead
Common Root Cause: Missing team Binary
- If
pane.start_commandbegins withteam tui ...:- Verify:
command -v team(likely missing) - Verify Loom exists:
command -v loom - This means the pane died because tmux tried to run
teamdirectly.
- Verify:
Fix Options
- Option A (fast local): add a
teamshim on PATH that forwards to Loom.teamshould behave like:loom team "$@"
- Option B (proper): adjust Loom/runner config so tmux spawns
loom team tui ...(notteam tui ...). - Option C: pass an explicit harness
--binthat points to the correct executable if supported.
Validate
- Restart run (or use
--force):loom team start <TEAM> --force ...
- Confirm manager pane is alive:
loom team status <TEAM>loom team capture <TEAM> manager --lines 40
Manual notes
This section is preserved when the skill is updated. Put human notes, caveats, and exceptions here.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?