Diagnose a named CCB managed agent using runtime, job-lineage, and provider evidence.
Scanned 9/2/2026
Install to Claude Code
npx -y skills add SeemSeam/claude_codex_bridge --skill ccb-diagnose --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Ccb Diagnose?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/seemseam-ccb-diagnose-d3f2e35f)More formats (shields.io, HTML) on the badges page.
---
name: ccb-diagnose
description: Diagnose a named CCB managed agent using runtime, job-lineage, and provider evidence.
metadata:
short-description: Diagnose CCB agent
---
# CCB Diagnose
Diagnose exactly one current mounted agent. Start with CCB authority:
```bash
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.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...