CtrlK
BlogDocsLog inGet started
Tessl Logo

code-review

Toolkit for performing structured code reviews. Covers identifying bugs, security issues, performance problems, and style violations. Use when asked to review code changes, pull requests, or individual files.

67

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 compact, well-organized instruction skill that gives concrete review guidance via a decision tree and checklist. It would benefit from a final verification step and slightly more worked examples.

Suggestions

Add an explicit final 'verify findings' checkpoint to the decision tree (e.g. re-confirm severity and reproducibility before reporting) to lift workflow clarity.

Expand the Examples section into one or two fully worked review cases instead of single-line prompts to strengthen actionability.

Trim the opening paragraph that restates the frontmatter description to improve conciseness.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, with only minor padding — the opening line restates the frontmatter description.

4 / 5

Actionability

Concrete, specific guidance throughout (e.g. 'Are there unnecessary allocations, N+1 queries, or unbounded loops?', 'Group findings by severity: critical, high, medium, suggestion'), with minor gaps since examples are illustrative quotes rather than fully worked cases.

4 / 5

Workflow Clarity

The decision tree gives a clear, sequenced branching workflow backed by a checklist, but lacks an explicit verification checkpoint confirming findings before reporting.

4 / 5

Progressive Disclosure

Under 50 lines with no need for external references, yet well-organized into clearly labeled sections (Decision Tree, Review Checklist, Examples, Guidelines) — meeting the simple-skill exception for a top score.

5 / 5

Total

17

/

20

Passed

Description

83%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, well-structured description that clearly states both capabilities and usage triggers in third person. It is specific and actionable, with only minor room to broaden trigger-term synonyms.

DimensionReasoningScore

Specificity

Names the domain and lists several concrete actions ('identifying bugs, security issues, performance problems, and style violations'), with only minor gaps in coverage rather than fully comprehensive granularity.

4 / 5

Completeness

Explicitly answers both what ('Toolkit for performing structured code reviews...') and when ('Use when asked to review code changes, pull requests, or individual files') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural trigger phrases 'review code changes, pull requests, or individual files' map well to what users say, though common synonyms like 'diff' or 'merge request' are missing.

4 / 5

Distinctiveness Conflict Risk

'Structured code reviews' is a clear niche with distinct triggers, with only minor overlap risk against dedicated security-audit or linting 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
agntcy/dir
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.