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.

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

Low

Low-risk findings worth noting

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.

A well-crafted instruction-only skill: lean, concrete commands, a clearly sequenced workflow with validation checkpoints and feedback loops, and clean section organization. It assumes Claude's competence and provides actionable, copy-paste-ready guidance throughout.

DimensionReasoningScore

Conciseness

Lean and operational throughout with no concept explanations (no 'what is a callback') and no padding; every section earns its place, matching the score-3 anchor rather than the score-2 'mostly efficient but could be tightened'.

3 / 3

Actionability

Provides concrete, copy-paste-ready commands with argument placeholders (e.g. "ccb repair retry <job_id|attempt_id>", "ccb cancel <job_id>"), fully executable rather than the score-2 pseudocode level.

3 / 3

Workflow Clarity

An 8-step sequence with explicit validation (step 8 re-runs trace and states success criteria) and a feedback loop (step 6: cancel, re-trace, stop-and-report on blocker), so the destructive-operation validation cap at 2 does not apply.

3 / 3

Progressive Disclosure

Organized into four clear headed sections (Core Workflow, Decision Rules, Artifact Rules, Red Lines) with no monolithic wall and no nested references; no bundle files are present or needed, so well-organized sections suffice.

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.

A strong description: third person, specific actions, an explicit "Use for" trigger clause covering natural problem terms, and a distinct niche. It cleanly answers both what the skill does and when to invoke it.

DimensionReasoningScore

Specificity

Lists concrete actions ("Diagnose and repair") and enumerates the specific lineage components (ask/job/message/reply/artifact/callback), matching the 'multiple specific concrete actions' anchor rather than the score-2 'names domain and some actions'.

3 / 3

Completeness

Clearly answers both what ("Diagnose and repair CCB ... lineage") and when via an explicit "Use for ..." trigger clause, satisfying the score-3 anchor instead of the score-2 'what present but when implied'.

3 / 3

Trigger Term Quality

The "Use for" clause covers natural problem phrasings a user would say ("missing replies", "incomplete artifacts", "pending callbacks", "reply delivery problems", "work-chain resume advice"), giving good coverage rather than the score-2 partial coverage.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (CCB lineage repair) with triggers specific to reply/callback/lineage issues, unlikely to conflict with unrelated skills; written in third person with no first/second person voice.

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.