CtrlK
BlogDocsLog inGet started
Tessl Logo

assigned-review-chain

Submit one node result to the assigned Reviewer and finish only after a bounded pass/rework chain.

62

Quality

73%

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.coder/skills/assigned-review-chain/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%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 tightly written, single-purpose instruction skill with concrete executable guidance, an explicit submit/continuation workflow, and validation feedback loops. Structure is clean with no bundle files required.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence with no padding or restatement of known concepts, matching the score-5 anchor where every token earns its place.

5 / 5

Actionability

It provides a copy-paste-ready command with an exact machine-line contract and concrete placeholders, fully executable for the common cases per the score-5 anchor.

5 / 5

Workflow Clarity

A clear sequence with explicit validation (rerun verification) and a feedback loop (rework -> rerun verification -> re-ask the same Reviewer), satisfying the score-5 anchor including the destructive/batch validation requirement.

5 / 5

Progressive Disclosure

The skill is compact and single-purpose with well-organized sections and no need for external bundle files, qualifying for the score-5 simple-skill exception.

5 / 5

Total

20

/

20

Passed

Description

46%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 concise and distinctive but leans on internal jargon rather than natural user trigger terms and omits any explicit "when to use" guidance. Its completeness is capped by the missing trigger clause.

Suggestions

Add an explicit trigger clause, e.g. "Use when the node task names one assigned Reviewer to review the node result."

Soften jargon with at least one natural keyword phrase so users would say it when they need the skill.

Consider listing the bounded pass/rework outcomes in the description to broaden the concrete action coverage.

DimensionReasoningScore

Specificity

Names the review-chain domain and a couple concrete actions ("Submit one node result", "bounded pass/rework chain") but the action set is not comprehensive, matching the score-3 anchor.

3 / 5

Completeness

There is a clear "what" but no explicit "when"/Use-when clause, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

The phrasing is internal jargon ("node result", "bounded pass/rework chain", "assigned Reviewer") rather than natural keywords a user would say; it sits noticeably below the midpoint anchor.

2 / 5

Distinctiveness Conflict Risk

The niche is specific (an assigned single-Reviewer review chain) with distinct triggers and only minor overlap risk with adjacent review skills, fitting just above the score-3 anchor.

4 / 5

Total

12

/

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.