CtrlK
BlogDocsLog inGet started
Tessl Logo

review

Read-only correctness review with actionable findings first, tight file/line evidence, severity, and a concise residual-risk summary.

64

Quality

76%

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 ./crates/tui/assets/skills/review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A concise, well-organized, read-only review skill with a clear sequenced workflow and appropriate section structure; its main weakness is actionability, where steps are somewhat high-level and lack concrete examples of severity levels or finding format.

Suggestions

Define a concrete severity scale (e.g., critical / high / medium / low) and show an example finding format with file/line evidence to make the guidance copy-paste ready.

Tighten the vague first step "Establish the change scope" into a specific action, such as enumerating changed files from the diff before reviewing.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — "Use for correctness review of a diff, PR, or named change set" and a four-step workflow with no padding or elementary explanation, so every token earns its place.

3 / 3

Actionability

Steps like "List findings by severity with file/line evidence" and "Call out residual risk and missing tests" give concrete direction, but "Establish the change scope" is abstract and no example severity scale or finding format is provided, leaving guidance incomplete.

2 / 3

Workflow Clarity

A clear numbered four-step sequence is present; since the skill is read-only and non-destructive, the missing-validation cap does not apply and the simple, well-sequenced workflow meets the clarity bar.

3 / 3

Progressive Disclosure

The skill is under 50 lines, needs no external references, and is organized into clear sections (When to use, Non-goals, Workflow), satisfying the simple-skill exception for progressive disclosure.

3 / 3

Total

11

/

12

Passed

Description

67%

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 specific, distinct, third-person description that names concrete review actions, but it omits an explicit "Use when..." trigger clause, leaving the when-to-use guidance only implied and capping completeness.

Suggestions

Add an explicit trigger clause such as "Use when reviewing a diff, PR, or named change set for correctness" to lift completeness to 3.

Surface natural user phrasing ("diff", "PR", "review my code") in the description itself rather than only in the body, improving trigger term coverage.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "correctness review", "actionable findings first", "tight file/line evidence", "severity", and "concise residual-risk summary" — matching the multi-action anchor rather than the single-domain anchor at 2.

3 / 3

Completeness

It clearly answers what the skill does, but there is no explicit "Use when..." trigger clause in the description; per the guideline a missing explicit trigger caps completeness at 2.

2 / 3

Trigger Term Quality

Relevant keywords like "correctness review", "findings", and "severity" appear, but natural user phrasing such as "diff", "PR", or "review my code" lives in the body rather than the description, so common variations are missing.

2 / 3

Distinctiveness Conflict Risk

The read-only, findings-first, severity-and-residual-risk framing carves a clear niche distinct from general code skills, so it is unlikely to trigger for the wrong skill.

3 / 3

Total

10

/

12

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
Hmbown/CodeWhale
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.