CtrlK
BlogDocsLog inGet started
Tessl Logo

ccb-comm-reply-recover

Diagnose and recover CCB communication and reply delivery stalls. Use when a user reports a missing CCB_REPLY, stuck ask, agent stuck busy/delivering, queued work behind an active job, cancelled/incomplete reply, empty artifact, callback not continuing, duplicate retry after success, or a CCB mailbox/communication backend that appears stuck.

69

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, command-driven runbook with explicit verification and a worked example that scores high on actionability and workflow. Minor conciseness redundancy and terse error-recovery are the only weak points.

Suggestions

Consolidate the duplicated safety rules between Overview and Red Lines (e.g., the do-not-edit authority-files rule) into one place to remove the conciseness trim opportunity.

Expand the cancel-failure branch from a bare "stop" into an explicit fix-and-revalidate loop to lift workflow clarity toward the validation-checkpoint anchor.

Consider splitting the Incident Classes taxonomy into a short reference file if the list grows, to keep SKILL.md a lean overview with one-level-deep navigation.

DimensionReasoningScore

Conciseness

The body is instruction-dense with no concept tutoring and commands given directly, but safety rules repeat across Overview and Red Lines (e.g., do-not-edit authority files vs. do-not-mutate-tmux), a minor trim opportunity that keeps it just below the lean-every-token-earns anchor.

4 / 5

Actionability

Concrete executable commands appear throughout — `ccb trace <id>`, `ccb queue --detail <agent>`, `ccb cancel <job_id>`, `ccb repair retry|resubmit|ack`, `ccb ps`, `ccb ping` — plus a fully worked example pattern covering common cases, matching the copy-paste-ready anchor.

5 / 5

Workflow Clarity

A clear 5-step Core Workflow with a dedicated Verification checklist and a re-run-trace feedback loop, but error recovery is terse ("If cancel fails or reports a blocker, stop") rather than a fix-and-revalidate loop, leaving a minor validation gap.

4 / 5

Progressive Disclosure

A single well-organized file with clear section headers and no nested references, all content appropriately inline; it sits above the 50-line simple-skill threshold so the structure is good but not the maximal clear-overview-with-one-level-references anchor.

4 / 5

Total

17

/

20

Passed

Description

86%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, trigger-rich description that clearly answers both what and when with concrete, natural incident phrasing. It is slightly limited on action specificity and has minor overlap with a sibling recovery skill.

DimensionReasoningScore

Specificity

"Diagnose and recover CCB communication and reply delivery stalls" names a specific domain with two concrete actions (diagnose, recover), but offers no broader action coverage beyond those two verbs, matching the 1-2-actions anchor rather than the several-actions anchors above.

3 / 5

Completeness

It explicitly states what ("Diagnose and recover CCB communication and reply delivery stalls") and when (an explicit "Use when a user reports..." clause listing concrete triggers), matching the anchor that requires both with concrete trigger phrases.

5 / 5

Trigger Term Quality

The "Use when" clause packs natural operator phrasing — "missing CCB_REPLY", "stuck ask", "agent stuck busy/delivering", "cancelled/incomplete reply", "empty artifact", "callback not continuing", "duplicate retry after success" — with synonyms covering the same failure from multiple angles.

5 / 5

Distinctiveness Conflict Risk

The reply-delivery-stall niche is distinct with specific triggers, but the body hands off to a sibling `ccb-self-recover` skill, indicating a closely related skill and minor overlap risk rather than minimal conflict.

4 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
SeemSeam/claude_codex_bridge
Reviewed

Table of Contents

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.