CtrlK
BlogDocsLog inGet started
Tessl Logo

review-checklist

Pre-merge review checklist based on recurring AI reviewer feedback patterns

56

Quality

65%

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

Quality

Content

92%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 tight, well-structured, actionable checklist that assumes Claude's competence and embeds the validation steps the workflow-clarity rubric rewards, with no padding and appropriate sectioning.

DimensionReasoningScore

Conciseness

The body is a lean checklist with no padding and no explanation of concepts Claude already knows; every line earns its place, matching the 'lean and efficient; assumes Claude's competence' anchor.

5 / 5

Actionability

Checks are concrete and specific, citing real APIs and commands (redact_params(), requires_approval(), tempfile, is_char_boundary(), 'grep impl LlmProvider for'), giving mostly executable guidance; held at 4 rather than 5 because it is guidance rather than copy-paste-ready code, which suits a checklist skill but leaves minor gaps versus the fully-executable anchor.

4 / 5

Workflow Clarity

As a single-purpose validation checklist it is unambiguous and well-sectioned, and its items themselves supply the validation/transaction/secret checks that feedback-loop caps require, so the simple-skill exception yields a 5 rather than a validation-capped 3.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references, and content is organized into clearly headed sections with no bundle files, matching the 'simple skill, progressive disclosure can score 5 with just well-organized sections' guideline.

5 / 5

Total

19

/

20

Passed

Description

37%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 states a clear purpose and niche but omits concrete actions and any explicit 'when to use' trigger guidance, with natural keywords relegated to the activation block rather than the description itself.

Suggestions

Add 2-3 concrete actions the checklist performs, e.g. 'Verifies transaction wrapping, SSRF/secret safety, and trait-wrapper coverage before merging'.

Append an explicit trigger clause such as 'Use when a PR is ready to merge or the user asks for a pre-merge check'.

Fold natural user phrases ('ready to merge', 'pre-merge check', 'review checklist') into the description so trigger-term quality is visible without relying on the activation block.

DimensionReasoningScore

Specificity

The description names the domain ('Pre-merge review checklist') and its provenance ('recurring AI reviewer feedback patterns') but lists no concrete actions, matching the 'names the domain but actions are minimal or generic' anchor rather than level 3 which requires 1-2 concrete actions.

2 / 5

Completeness

There is a clear 'what' ('Pre-merge review checklist based on recurring AI reviewer feedback patterns') but no 'Use when...' or equivalent 'when' guidance in the description, matching the 'clear what but when is missing' anchor; the missing-use-when cap of 3 also applies.

3 / 5

Trigger Term Quality

The description text itself contains no natural user phrases (e.g. 'ready to merge', 'check before merge'); those live in the separate activation block, so natural keyword coverage in the description is minimal, fitting the 'one or two generic keywords; missing natural phrases' anchor.

2 / 5

Distinctiveness Conflict Risk

'Pre-merge review checklist' is somewhat specific to a pre-merge niche but is generic enough to overlap with general code-review skills, matching the 'somewhat specific but could still overlap' anchor rather than the more-distinct level 4.

3 / 5

Total

10

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
nearai/ironclaw
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.