CtrlK
BlogDocsLog inGet started
Tessl Logo

ccb-self-chain

Diagnose and repair CCB ask/job/message/reply/artifact/callback lineage. Use for missing replies, incomplete artifacts, pending callbacks, retry/resubmit/ack decisions, reply delivery problems, or work-chain resume advice.

70

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

88%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.

The body is a tight, highly actionable runbook with concrete ccb commands, a well-sequenced workflow, explicit validation/feedback loops, and clear red lines. The only friction is minor repetition of the repair taxonomy across two sections and a single-file structure that could optionally split reference material.

Suggestions

Collapse the retry/resubmit/ack definitions so they appear once (e.g., define them in Decision Rules and reference them from Core Workflow step 5) to remove the minor duplication.

If the artifact-checksum and project_shutdown edge cases grow, consider moving them into a one-level-deep reference file to push progressive disclosure toward 5.

DimensionReasoningScore

Conciseness

The body is lean operational guidance with no padding about concepts Claude already knows, but the retry/resubmit/ack taxonomy recurs in both Core Workflow step 5 and the Decision Rules section, a minor duplication that could be tightened.

4 / 5

Actionability

Fully executable commands with explicit argument placeholders (ccb trace <id>, ccb cancel <job_id>, ccb repair retry <job_id|attempt_id>) cover the common cases and match the 'copy-paste ready, specific examples cover common cases' anchor.

5 / 5

Workflow Clarity

An 8-step sequenced workflow with explicit validation checkpoints ('re-run trace before choosing retry or resubmit', 'After repair, re-run trace and queue/inbox checks'), error-recovery feedback loops (cancel fails -> stop), and a defined success criteria checklist, matching the top anchor.

5 / 5

Progressive Disclosure

Content is well-organized into clear sections (Core Workflow, Decision Rules, Artifact Rules, Red Lines) with no nested references and all guidance self-contained, but the skill exceeds 50 lines with no external file split, so it sits at 'good structure, minor organization gaps' rather than the well-signaled one-level-deep reference pattern of the top anchor.

4 / 5

Total

18

/

20

Passed

Description

82%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.

The description is a strong, third-person statement that clearly defines a niche domain and supplies explicit 'Use for...' trigger guidance covering multiple concrete problem scenarios. Its only weak spot is specificity, where two verbs undersell the range of concrete actions the skill performs.

Suggestions

Expand the action list beyond 'Diagnose and repair' to name the concrete operations the skill performs (e.g., trace lineage, cancel in-flight jobs, repair retry/resubmit/ack) to lift specificity toward 5.

Add a couple of natural synonyms or user phrasings (e.g., 'stuck job', 'lost reply', 'duplicate work') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names a rich domain (CCB ask/job/message/reply/artifact/callback lineage) with two concrete verbs ('Diagnose and repair'), but lists only 1-2 actions rather than several, matching the 'names domain and 1-2 concrete actions' anchor and falling short of the 'several specific actions' anchor above.

3 / 5

Completeness

Explicitly answers both what ('Diagnose and repair CCB ... lineage') and when ('Use for missing replies, incomplete artifacts, pending callbacks...') with concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

The 'Use for missing replies, incomplete artifacts, pending callbacks, retry/resubmit/ack decisions, reply delivery problems, or work-chain resume advice' clause gives good natural problem-scenario coverage a user would voice, missing only a few synonyms to reach the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

The CCB lineage-repair niche with specific triggers (missing replies, pending callbacks, reply delivery problems) is clearly distinct from other skills with minimal conflict risk, matching the 'clear niche with distinct triggers' anchor.

5 / 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.