node-check

Verify one coder node against the assigned execution contract and return pass, rework, blocked, or non-converged evidence.

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./docs/plantree/plans/agentic-loop-workflow/drafts/agentroles.code_reviewer/skills/node-check/SKILL.md

Quality

Content

78%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 lean, well-structured instruction-only workflow with concrete verdict output and clear checkpoints; it appropriately avoids destructive actions by design. The main improvement is adding an explicit error-recovery feedback loop and trimming a few explanatory sentences.

Dimension	Reasoning	Score
Conciseness	The ~40-line body is efficient and avoids explaining concepts Claude already knows, with only minor over-explanation such as 'Reviewer model text can never satisfy that check' that could be trimmed.	4 / 5
Actionability	As an instruction-only review skill it gives concrete actions and an exact machine-verdict format ('status: pass', 'status: rework_required', etc.), with only minor abstraction in steps like 'Audit hidden fallback'.	4 / 5
Workflow Clarity	A clear 7-step numbered sequence with explicit decision checkpoints (e.g., 'Missing or mismatched visible identity is blocked'), missing only a fully spelled-out validate-fix-retry feedback loop.	4 / 5
Progressive Disclosure	Under 50 lines with no external references needed, the content is well-organized into Workflow and Boundaries sections, satisfying the simple-skill exception for progressive disclosure.	5 / 5
	Total	17 / 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 clearly states what the skill does, including its four return verdicts, but lacks any 'Use when...' trigger guidance and leans heavily on internal jargon. Adding explicit trigger phrasing and more natural synonyms would raise completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause stating when this skill should be invoked (e.g., 'Use when reviewing a coder node's execution contract compliance').

Replace or supplement internal jargon ('execution contract', 'non-converged') with more natural trigger terms a user might actually say.

Briefly mention the scope of nodes/contracts covered to sharpen distinctiveness from adjacent review skills.

Dimension	Reasoning	Score
Specificity	Names the domain (coder node verification) and several concrete actions including four explicit return verdicts ('pass, rework, blocked, or non-converged'), with only minor abstraction around 'execution contract'.	4 / 5
Completeness	It gives a clear 'what' (verify a node and return one of four verdicts) but no 'when'/trigger clause is present, so per the rubric guideline completeness is capped at 3.	3 / 5
Trigger Term Quality	The terms ('coder node', 'execution contract', 'non-converged') are domain-specific technical jargon rather than natural phrases a user would say, missing common synonyms or variations.	2 / 5
Distinctiveness Conflict Risk	The narrow node-review niche and explicit four-verdict output make it mostly distinct with only minor overlap risk against closely related review skills.	4 / 5
	Total	13 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: SeemSeam/claude_codex_bridge
Path: docs/plantree/plans/agentic-loop-workflow/drafts/agentroles.code_reviewer/skills/node-check/SKILL.md
Commit: 01d5b1c

Reviewed: about 20 hours ago

Table of Contents

Discovery Implementation Validation

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.