CtrlK
BlogDocsLog inGet started
Tessl Logo

code-review

Perform thorough code reviews focusing on correctness, readability, security, and maintainability.

58

Quality

66%

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 ./SKILL.md

The canonical home for this skill is code-review in neil-tessl/skill-index-evals-dev

SKILL.md
Quality
Evals
Security

Quality

Content

80%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 skill body is exceptionally lean and well-organized for a simple review skill, with concrete examples that distinguish blocking issues from nits. Its main gap is the absence of an explicit review workflow sequence with validation checkpoints, leaving workflow clarity only implicit.

Suggestions

Add a short ordered review workflow (e.g. read the diff -> check the checklist -> categorize findings -> post feedback) to make the process sequence explicit.

Include a concrete validation checkpoint such as 're-read the suggested fix against the surrounding code before posting a blocking comment'.

Optionally show one small executable code snippet or command (e.g. how to view a diff) to raise actionability from 4 to 5.

DimensionReasoningScore

Conciseness

The body is lean with no padding or explanation of concepts Claude already knows; every line is a concrete checklist item, guidance rule, or example, so every token earns its place.

5 / 5

Actionability

It gives concrete, executable guidance (line-number references, a blocking example with a concrete fix, a nit example) but contains no actual code or commands, leaving minor gaps for an instructional review skill.

4 / 5

Workflow Clarity

A review is not a destructive/batch operation, so the destructive cap does not apply, but the body presents a checklist and feedback style rather than a clearly sequenced review workflow with checkpoints, so sequence and validation are only implicit.

3 / 5

Progressive Disclosure

For a simple, single-purpose skill under 50 lines with no bundle files, the content is well organized into clear sections (Checklist, Feedback Style, Examples) with no nested references, which earns a 5 under the simple-skill exception.

5 / 5

Total

17

/

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.

The description clearly states the skill's purpose and focus areas using third person, but it omits any explicit 'Use when' trigger guidance, which limits its completeness and trigger discoverability. Specificity is decent but stays at the level of named review dimensions rather than enumerated concrete actions.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases, e.g. 'Use when the user asks to review code, a pull request, or a diff.'

Strengthen specificity by listing concrete actions performed during a review (e.g. 'identifies bugs, flags security issues, suggests refactors') rather than only naming review categories.

Include natural synonyms users say, such as 'review my code', 'check this PR', or 'look at this diff', to improve trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain ('code reviews') and lists four concrete focus areas (correctness, readability, security, maintainability), but the actions are generic review categories rather than multiple distinct concrete operations.

3 / 5

Completeness

It states clearly what the skill does, but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

'code reviews' and 'code review' are natural terms, but it lacks common synonyms users say such as 'review my code', 'look at this diff', or 'PR review', so coverage is only partial.

3 / 5

Distinctiveness Conflict Risk

'code reviews' is a fairly distinct niche with its own triggers and low overlap risk with unrelated skills, though it could still overlap with a general 'review' or debugging skill.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
neil-tessl/nh-code-review-skills
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.