CtrlK
BlogDocsLog inGet started
Tessl Logo

reviewing-code

Review code for quality, maintainability, and correctness. Use when reviewing pull requests, evaluating code changes, or providing feedback on implementations. Focuses on API design, patterns, and actionable feedback.

64

Quality

75%

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

Quality

Content

75%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 a well-structured, actionable guide that assumes Claude's competence and supplies concrete rules, examples, and a verification checklist rather than abstract advice. Its main limitation is mild verbosity in the philosophy/tone prose and the absence of deeper reference material, neither of which materially weakens it.

DimensionReasoningScore

Conciseness

The body is mostly lean, using bullets, tables, and short sections and avoiding restating concepts Claude already knows, though the 'Philosophy' and 'Tone' prose sections contain general guidance that could be trimmed.

4 / 5

Actionability

Provides concrete, specific guidance — explicit dependency-pin rules ('The version pin in pyproject.toml must match'), named anti-patterns (mutable defaults, contradicting defaults), a before/after comment-example table, and a checklist with specific commands (uv sync, prek, pytest) — with only minor gaps.

4 / 5

Workflow Clarity

A clear review sequence ('For Agent Reviewers' steps) plus a decision-framework gating the approval and a verification checklist provide most checkpoints; because code review is a judgment rather than destructive/batch task, the missing-explicit-feedback-loop cap does not apply.

4 / 5

Progressive Disclosure

The content is well-organized into clearly headed sections with no nested or buried references and no bundle files present; it is slightly above the 50-line simple-skill threshold, so it does not reach the 5 available to compact single-purpose skills despite its clean structure.

4 / 5

Total

16

/

20

Passed

Description

75%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 is strong and well-formed: third person, explicit 'Use when...' triggers, and a clear statement of scope and focus. Both the 'what' and 'when' are present and concrete, with only minor gaps in synonym coverage and action comprehensiveness.

DimensionReasoningScore

Specificity

Names the code-review domain plus several concrete focus areas ('quality, maintainability, and correctness', 'API design, patterns, and actionable feedback'), but these are review dimensions rather than a comprehensive list of distinct executable actions, leaving minor gaps versus a 5.

4 / 5

Completeness

Explicitly answers both what ('Review code for quality, maintainability, and correctness... Focuses on API design, patterns...') and when ('Use when reviewing pull requests, evaluating code changes, or providing feedback on implementations'); the 'when' is clear and concrete but slightly formulaic rather than the idealized, exhaustive trigger list of a 5.

4 / 5

Trigger Term Quality

Includes natural phrases users would actually say ('reviewing pull requests', 'evaluating code changes', 'providing feedback on implementations'), though common synonyms like 'PR', 'diff', or 'code review' itself are absent.

4 / 5

Distinctiveness Conflict Risk

The pull-request / code-review framing carves a distinct niche with minimal conflict risk, though it could still mildly overlap with general-purpose coding or refactoring skills.

4 / 5

Total

16

/

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
PrefectHQ/fastmcp
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.