CtrlK
BlogDocsLog inGet started
Tessl Logo

round-verification

Verify a CCB execution round and produce a machine-readable round result artifact.

59

Quality

67%

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

Fix and improve this skill with Tessl

tessl review fix ./docs/plantree/plans/agentic-loop-workflow/drafts/agentroles.ccb_round_checker/skills/round-verification/SKILL.md
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 body is a tight, highly actionable instruction-only skill with an exact output format, a clear sequenced workflow, an explicit validation gate, and well-organized sections needing no external references. It earns top marks across all content dimensions.

DimensionReasoningScore

Conciseness

The body is lean for a strict output-gate protocol ("Do not write any preamble, heading, Markdown fence..."), assumes Claude's competence, and avoids explaining concepts Claude already knows; the repeated prohibitions are deliberate reinforcement rather than padding.

3 / 3

Actionability

It gives the exact first-line format `round result: pass|partial|replan_required|blocked`, explicit rejection conditions, and precise placement rules (first non-empty line, no preceding tools/tests), which is copy-paste-ready actionable guidance for an instruction-only skill.

3 / 3

Workflow Clarity

The three-step sequence (read evidence, reject listed failure modes, emit one result line) is clearly ordered with a validation checkpoint ("If the evidence is insufficient, start with `round result: blocked`") and a rejection checklist in step 2.

3 / 3

Progressive Disclosure

At under 50 lines with no external references needed and well-organized sections (Workflow, Boundaries), this single-purpose skill meets the rubric's simple-skill allowance for a top progressive-disclosure score; the body references no bundle files and none exist.

3 / 3

Total

12

/

12

Passed

Description

35%

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 states a concrete purpose but relies entirely on internal jargon and omits any explicit "Use when..." trigger, capping completeness at 2 and leaving trigger-term quality at 1. It is recognizable within its niche but not discoverable via natural user language.

Suggestions

Add an explicit "Use when..." clause naming natural triggers (e.g. after a controller-owned node review/integration round completes) to raise completeness and trigger-term quality.

Replace or supplement jargon ("integrated round evidence", "script import") with terms a user would naturally say when they need round verification.

List one or two more concrete actions to move specificity toward the anchor-3 multiple-actions bar.

DimensionReasoningScore

Specificity

Quotes "Verify integrated round evidence and return a machine-readable round result" name the domain and two concrete actions, but fall short of the anchor-3 bar of listing multiple comprehensive concrete actions (only two, and "integrated round evidence" is abstract).

2 / 3

Completeness

It states what the skill does (verify and return a result) but provides no "Use when..." trigger, so per the judging guideline completeness is capped at 2 (has what, when missing/only implied).

2 / 3

Trigger Term Quality

Phrases like "integrated round evidence", "machine-readable round result", and "script import" are internal-pipeline jargon a user would not naturally say, matching the no-natural-keywords anchor rather than the partial-coverage anchor 2.

1 / 3

Distinctiveness Conflict Risk

The round-verification niche is specific, but with only jargon triggers and no natural language distinguishing it from related review/round skills it remains overlap-prone rather than a clear-anchor-3 distinct niche.

2 / 3

Total

7

/

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.