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

93%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.

An exceptionally tight, instruction-only skill: a complete executable submission template, an unambiguous status-to-terminal mapping, an explicit rework feedback loop, and firm boundaries — every token is load-bearing. The only meaningful gap is that the promised 'bounded' chain is never quantified, which leaves the workflow one notch below fully airtight.

DimensionReasoningScore

Conciseness

The body is lean and imperative throughout — no concept explanations, no padding, every line instructs. Even the guardrail sentences ("It is not an environment variable and must not be inferred"; "do not rely on the Reviewer's remembered role instructions alone") earn their tokens by preventing concrete failure modes. This matches the anchor 'lean and efficient; every token earns its place'.

5 / 5

Actionability

A fully executable `command ask --chain --artifact-reply` heredoc template with every payload field itemized, the exact four-value machine-line status enum, explicit placeholder-substitution rules, and a copy-paste-ready continuation branch per status. The only unfilled parts are inherent placeholders (`<ref>`, `<node id>`, `<assigned-reviewer>`), which the skill explicitly tells the reader to fill. Matches the 'copy-paste ready' anchor.

5 / 5

Workflow Clarity

The sequence is clear (implement and verify → submit exactly once → stop → branch on status) with an explicit feedback loop (rework: apply only the requested repair, rerun verification, re-ask the same Reviewer) and terminal-status mapping. Falls short of 5 because 'bounded' is never quantified — no hop limit or convergence rule beyond the non_converged escape hatch — leaving 'exactly once per bounded review hop' with an implicit bound.

4 / 5

Progressive Disclosure

A ~60-line single-topic skill with no external reference needs and no bundle files; the Submit / Continuation / Boundaries sections are well-organized and the command block is appropriately inline as core content. Per the simple-skill guideline, well-organized sections with no need for external references score 5.

5 / 5

Total

19

/

20

Passed

Description

53%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.

A concise, third-person description with a clear 'what' and a genuinely distinctive niche, but no 'when' — the trigger condition lives only in the body, and the keyword set is jargon-heavy with no natural user phrasing or synonyms. Adding an explicit 'Use when the node task names one assigned Reviewer' clause would fix both the completeness cap and the trigger-term weakness.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the node task names one assigned Reviewer and requires a bounded pass/rework review chain before Coder can finish.'

Include natural keyword variations users would actually say ('assigned reviewer', 'review chain', 'submit for review', 'pass/rework') so the description surfaces on natural phrasing, not just internal jargon.

Mention the outcome the skill guarantees — e.g. 'return Coder terminal done only after Reviewer pass' — to sharpen the 'what' and further distinguish it from generic review-submission skills.

DimensionReasoningScore

Specificity

The description names its domain and two concrete actions ("Submit one node result to the assigned Reviewer", "finish only after a bounded pass/rework chain"), but stops there — it omits the rework loop handling, terminal statuses, and stopping rules that make up the skill. This matches the anchor for 1-2 concrete actions without comprehensive coverage, and falls short of anchor 4's 'several specific actions'.

3 / 5

Completeness

The 'what' is clear (submit a node result; finish only after a bounded pass/rework chain), but the description contains no 'Use when...' clause or equivalent trigger guidance — the trigger condition exists only in the body ("Use this skill only when the node task names one assigned Reviewer"). Per the judging guideline, a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

"assigned Reviewer", "node result", and "pass/rework chain" are relevant keywords for this niche, but they are system jargon with no natural user phrasing, synonyms, or variations. Anchor 3 ('some relevant keywords but missing common variations') fits better than 2 (the terms are domain-relevant, not generic) and well below 4 (no natural trigger phrasing a user would echo).

3 / 5

Distinctiveness Conflict Risk

"assigned Reviewer", "node result", and "bounded pass/rework chain" carve a narrow, distinctive niche unlikely to fire for generic review or submission skills. Not 5: without any trigger clause in the description itself, it retains minor overlap risk with sibling review/submission skills in the same environment.

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.

Validation — 16 / 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.