CtrlK
BlogDocsLog inGet started
Tessl Logo

node-check

Verify one CCB worker node and reject hidden fallback, degradation, scope shrinkage, or missing evidence.

55

Quality

61%

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_checker/skills/node-check/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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 exceptionally concise and well-structured for a simple decision skill, but its actionability and workflow clarity are held back by missing verification methodology and explicit feedback/rework checkpoints.

Suggestions

Add concrete checks for each rejection criterion (e.g., what specifically signals 'hidden fallback' or 'scope shrinkage') so the guidance is executable rather than enumerated.

Add an explicit rework feedback loop: when returning 'rework_required', specify how findings/required rework flow back to the worker and whether to re-verify.

Optionally include a brief output template or schema for the check plan, evidence reviewed, and findings to make the output more concrete.

DimensionReasoningScore

Conciseness

The body is lean and efficient — short input and output sections with no over-explanation of concepts Claude already knows; every token earns its place.

5 / 5

Actionability

It gives concrete enumeration (exact result classes and a listed input set) but omits key details on HOW to detect hidden fallback, degradation, or scope shrinkage, leaving the verification methodology incomplete.

3 / 5

Workflow Clarity

A rough sequence is present (use after a worker returns → review inputs → return one result class → include findings), but there are no explicit validation checkpoints or a rework feedback loop, so it sits at the validation-gap anchor.

3 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references and is organized into well-signaled ## Inputs and ## Output sections, satisfying the simple-skill exception for a 5.

5 / 5

Total

16

/

20

Passed

Description

51%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 specific and identifies a clear niche with concrete rejection criteria, but it lacks an explicit 'when to use' trigger clause and relies on domain jargon rather than natural user language.

Suggestions

Add an explicit 'Use when…' clause stating when this skill applies (e.g., after a CCB worker returns a node result) to raise completeness and trigger quality.

Include more natural trigger terms and synonyms a user might say alongside the jargon (e.g., 'check', 'review', 'accept/reject a worker node') to improve trigger_term_quality.

Specify how the rejection criteria are detected (e.g., what evidence to look for) to push specificity toward 5.

DimensionReasoningScore

Specificity

The description names the domain ('Verify one CCB worker node') and lists several concrete rejection criteria ('hidden fallback, degradation, scope shrinkage, or missing evidence'), though the criteria are abstract failure-mode categories rather than fully concrete operations, keeping it just below a 5.

4 / 5

Completeness

The 'what' is clear (verify a worker node and reject specific failure modes), but there is no 'Use when…' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

It leans on niche jargon ('CCB worker node', 'scope shrinkage', 'hidden fallback') rather than natural phrases a user would say, missing common variations and synonyms; noticeably below the midpoint.

2 / 5

Distinctiveness Conflict Risk

The CCB worker-node verification framing is a fairly distinct niche with specific triggers, but the general 'verify and reject' framing could overlap with related review/QA skills, so it is not a clear 5.

4 / 5

Total

13

/

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.