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.

80

Quality

100%

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

100%

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

The content is lean, highly actionable, and well-sequenced with explicit verification loops and red-line guardrails. It is appropriately self-contained with strong section organization.

DimensionReasoningScore

Conciseness

The body is dense and purposeful—command sequences, incident classes, and repair rules—without explaining concepts Claude already knows; nearly every token earns its place.

3 / 3

Actionability

Concrete, executable commands with specific argument forms (ccb trace <id>, ccb cancel <job_id>, ccb repair retry <job_id|attempt_id>) plus explicit decision rules make the guidance copy-paste ready for a ccb operator.

3 / 3

Workflow Clarity

A numbered Core Workflow with explicit sequencing, a dedicated Verification section with feedback checkpoints (re-run trace and queue checks), and incident-class-driven classification provide clear validation loops for this risky recovery operation.

3 / 3

Progressive Disclosure

No bundle files exist; the skill is a single self-contained ~120-line file organized into clear sections (Overview, Core Workflow, Incident Classes, Repair Rules, Verification, Example Pattern, Red Lines), which satisfies the simple-skill allowance for a top score.

3 / 3

Total

12

/

12

Passed

Description

100%

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

The description is specific, trigger-rich, complete, and distinctively scoped to CCB communication/reply recovery. It cleanly hits the top anchor on every dimension.

DimensionReasoningScore

Specificity

"Diagnose and recover CCB communication and reply delivery stalls" names concrete actions and enumerates multiple specific failure modes, matching the 'lists multiple specific concrete actions' anchor; it is not a level-2 domain-plus-some-actions description.

3 / 3

Completeness

It states what ("Diagnose and recover CCB communication and reply delivery stalls") and gives an explicit "Use when..." trigger clause, clearly answering both what and when.

3 / 3

Trigger Term Quality

Phrases like "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" are natural incident-reporting terms a user would actually say, giving good coverage.

3 / 3

Distinctiveness Conflict Risk

The CCB_REPLY / mailbox / communication-backend niche with its specific incident triggers is a clear niche unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.