What problem does it solve?
When a CCB agent becomes stuck, disconnected, stops replying, or shows provider errors, this Skill provides a single structured workflow to diagnose the root cause, apply bounded recovery, verify the fix, and optionally file a redacted GitHub issue.
Core Features & Use Cases
- Authority-Based Diagnosis: Combines
ccb ping, ccb ps, ccb queue, ccb pend, and ccb trace output to establish the true runtime and job lineage state before acting.
- Deep Pane Inspection: Classifies the agent's tmux pane state (working, waiting_input, stale_prompt, provider_error, dead_or_blank, and more) using read-only capture, never mutating panes.
- Bounded Recovery: Applies the least disruptive supported repair such as
ccb repair ack, ccb repair retry, ccb repair resubmit, or a guarded ccb restart, then verifies the result.
- Use Case: A user reports that agent 'gemini' stopped replying mid-task. The Skill checks the daemon graph, inspects the pane, finds a provider rate-limit error, restarts the agent after cancelling stale work, verifies recovery, and prepares a redacted incident bundle.
Quick Start
Ask the assistant to run ccb-diagnose on the agent named gemini because it appears stuck and is not replying.