CtrlK
BlogDocsLog inGet started
Tessl Logo

code-review

Use this skill when the user wants to review code, audit a pull request, check code quality, find bugs, or get feedback on implementation.

65

Quality

78%

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

Quality

Content

76%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.

A highly actionable, token-efficient skill body built from executable code and a useful tool/command reference, with a clear review structure and report template. Its main gap is the absence of verification checkpoints to confirm findings against the actual code before a review is submitted.

Suggestions

Add an explicit verification step to the review workflow, e.g. 'Before reporting, confirm each issue references real code at {file}:{line} and is reproducible.'

Consider moving the longer inline snippets (AST complexity check, PyGithub PR submission) into a references/ file, keeping SKILL.md as a tighter overview.

Clarify the gate before calling pr.create_review — e.g. require a draft report to be reviewed/approved before submitting an outward-facing PR review event.

DimensionReasoningScore

Conciseness

The body is lean — mostly executable code, a compact checklist, and a reference table — with almost no explanation of concepts Claude already knows; minor bulk in the inline AST-complexity and static-analysis code could be trimmed or moved to references.

4 / 5

Actionability

Provides copy-paste-ready, executable code (get_staged_diff, run_pylint, check_complexity, review_pr) plus concrete tool commands in the Quick Reference table, covering the common review cases.

5 / 5

Workflow Clarity

A clear sequenced structure exists (the 5-part Review Structure and report template), but there are no validation checkpoints verifying that each reported issue maps to real code at the cited line before submitting a review.

3 / 5

Progressive Disclosure

Content is well-organized into clearly labeled sections with no nested references; at ~100 lines with all material inline it is slightly above the under-50-line simple-skill threshold, so a small amount of the static-analysis code could be split into reference files.

4 / 5

Total

16

/

20

Passed

Description

80%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.

A strong, trigger-rich description that names several concrete actions and an explicit 'Use when' clause, distinguishing it clearly as a code-review skill. It could be sharpened by separating the capability statement from the trigger clause and adding a few more natural synonyms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'review code, audit a pull request, check code quality, find bugs, or get feedback on implementation' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Both 'what' (the review/audit/check actions) and 'when' ('Use this skill when the user wants to...') are present and explicit, though the what and when are fused into a single clause rather than stated separately.

4 / 5

Trigger Term Quality

Natural phrases users would say ('review code', 'audit a pull request', 'find bugs', 'get feedback') are present, but a few common synonyms like 'code review', 'lint', or 'refactor' are missing.

4 / 5

Distinctiveness Conflict Risk

Code review is a clear, well-defined niche with distinct triggers and low conflict risk, though 'get feedback on implementation' is broad enough to slightly overlap with general development skills.

4 / 5

Total

17

/

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
ProwlrBot/prowlr-marketplace
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.