CtrlK
BlogDocsLog inGet started
Tessl Logo

requesting-code-review

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

62

Quality

72%

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 ./skills/requesting-code-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 concise, actionable, well-sequenced instruction for dispatching a code-reviewer subagent, with clean sectioning and a single clearly signaled reference. The only notable gaps are minor redundancy between sections and no explicit validation checkpoint in the workflow.

DimensionReasoningScore

Conciseness

The body is lean and sectioned with no padding of concepts Claude already knows, though the Example re-derives git SHAs and the Integration section partially restates When to Request, leaving minor instances that could be trimmed.

4 / 5

Actionability

It gives executable bash commands, a named subagent type, an explicit placeholder list, and a template pointer, with only a minor gap that the template content itself is not inline.

4 / 5

Workflow Clarity

The numbered 1-2-3 sequence (get SHAs, dispatch, act on feedback) is clear with prioritized feedback handling as an implicit recovery path; it lacks an explicit validate-then-proceed checkpoint, but the operation is neither destructive nor batch so no cap applies.

4 / 5

Progressive Disclosure

At well under 50 lines with no external material needed, the content is cleanly sectioned and the single one-level-deep reference to code-reviewer.md is signaled twice, meeting the simple-skill exception for a top score.

5 / 5

Total

17

/

20

Passed

Description

63%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 has strong, natural trigger phrasing and explicit 'when' guidance, but lacks concrete 'what' capabilities and is broad enough to risk overlap with other review/QA skills. Tightening it to name the actual action (dispatching a code-reviewer subagent) would raise specificity and distinctiveness.

Suggestions

Add the concrete action the skill performs, e.g. 'Dispatches a code-reviewer subagent to review your work' before the trigger clause.

Make the 'what' explicit so it is not just an implied purpose ('verify work meets requirements').

Narrow the trigger so it is less likely to collide with general QA or merge-checklist skills.

DimensionReasoningScore

Specificity

The description names a clear domain (verifying work meets requirements before merge) but lists no concrete actions — the actual capability (dispatching a code-reviewer subagent) is absent, leaving it at 'names domain and 1-2 concrete actions' level without fully meeting it.

3 / 5

Completeness

It explicitly answers 'when' ('Use when completing tasks, implementing major features, or before merging') and offers a weak-but-present 'what' ('verify work meets requirements'), but the concrete capability is not explicit, so 'when' could be more specific.

4 / 5

Trigger Term Quality

'completing tasks, implementing major features, or before merging' are natural phrases a developer would actually say, giving good keyword coverage, though synonyms are limited.

4 / 5

Distinctiveness Conflict Risk

Triggers like 'completing tasks' are broad and overlap with general QA/review skills, so it is somewhat specific but could still trigger for the wrong skill.

3 / 5

Total

14

/

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
lucianghinda/superpowers-ruby
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.