ccb-diagnose

Diagnose a named CCB managed agent using runtime, job-lineage, and provider evidence.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./inherit_skills/dsh_skills/ccb-diagnose/SKILL.md

CCB Diagnose

Diagnose exactly one current mounted agent. Start with CCB authority:

command ccb ping "$AGENT"
command ccb ps
command ccb queue --detail "$AGENT"
command ccb pend --inbox --detail "$AGENT"

Use ccb trace for a current lineage id and ccb doctor logs for provider/API evidence. For DSH, the pane is only the managed host process/log surface: pane text is not prompt, reply, or completion authority. Native authority is the exact DSH session/RPC event history and turn/end reason recorded by CCB.

Do not read credentials, mutate tmux directly, restart all agents, or submit a GitHub issue without showing a redacted proposal and receiving explicit authorization. Apply only a bounded supported repair, then re-check the same runtime and lineage evidence.

Repository: SeemSeam/claude_codex_bridge
Path: inherit_skills/dsh_skills/ccb-diagnose/SKILL.md
Commit: 18bf0af

Last updated: 7 days ago
First committed: 2 months ago

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.