CtrlK
BlogDocsLog inGet started
Tessl Logo

ccb-self-diagnose

Diagnose CCB runtime, mounted daemon graph, tmux namespace and panes, provider context, queue/inbox/trace, replies/artifacts, config drift, and storage boundaries. Use when the user asks what is broken, which agent is stuck, whether CCB is mounted, why a reply did not arrive, or what to check first.

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.

A tight, well-structured triage skill: concrete commands, an explicitly validated workflow, clear failure-domain routing, and firm red-line guardrails, all without verbosity. It exemplifies an instruction-only skill that is fully actionable without code.

DimensionReasoningScore

Conciseness

The body is lean and well-sectioned, assuming Claude's competence — it never explains what a daemon or tmux is, and every line earns its place.

3 / 3

Actionability

It gives concrete, copy-paste diagnostic commands with real flags ('ccb queue --detail all', 'ccb pend --inbox --detail <agent>', 'ccb trace <job_id|message_id|attempt_id|reply_id>') rather than abstract direction.

3 / 3

Workflow Clarity

The Core Workflow is a numbered 6-step sequence with explicit validation checkpoints (validate then dry-run, recheck the daemon graph, report a blocker if the artifact is absent) and a clear failure-domain handoff step.

3 / 3

Progressive Disclosure

Content is self-contained and organized into clear single-level sections (Evidence Model, Core Workflow, Failure Domains, Reporting, Red Lines) with no nested references; no bundle files are needed for this scope.

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, third-person description that pairs concrete capabilities with an explicit, naturally-worded 'Use when' clause and a distinct triage niche. It is concise yet comprehensive without fluff or over-claims.

DimensionReasoningScore

Specificity

The description lists multiple concrete diagnostic targets ('mounted daemon graph', 'tmux namespace and panes', 'queue/inbox/trace', 'replies/artifacts', 'config drift', 'storage boundaries') rather than vague language.

3 / 3

Completeness

It explicitly answers both what ('Diagnose CCB runtime...') and when ('Use when the user asks...'), with an explicit trigger clause.

3 / 3

Trigger Term Quality

The 'Use when' clause surfaces natural user phrasings — 'what is broken', 'which agent is stuck', 'why a reply did not arrive', 'what to check first' — that a user would actually say.

3 / 3

Distinctiveness Conflict Risk

It carves a clear CCB read-only triage niche with distinct triggers, unlikely to fire for the sibling recover/chain/config 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.