CtrlK
BlogDocsLog inGet started
Tessl Logo

code-reviewer

Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.

86

1.54x
Quality

78%

Does it follow best practices?

Impact

99%

1.54x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/code-reviewer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The content is well-crafted: concise, concrete with real executable commands, a clearly sequenced workflow with a preflight checkpoint, and cleanly organized into navigable sections. No bundle files are needed or referenced.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: it provides direct commands and short checklist framing without explaining concepts Claude already knows (e.g., it never explains what git or a PR is). Every section earns its place.

3 / 3

Actionability

It gives concrete, copy-paste-ready commands ('gh pr checkout <PR_NUMBER>', 'git diff --staged', 'npm run preflight') plus a structured output format (Summary / Critical / Improvements / Nitpicks / Conclusion), fully actionable guidance.

3 / 3

Workflow Clarity

A clear five-step sequence (Determine Target → Preparation → Analysis → Feedback → Cleanup) with an explicit preflight validation checkpoint; this is a read-only review task so the missing error-recovery loop does not cap the score.

3 / 3

Progressive Disclosure

A single self-contained ~57-line SKILL.md with no bundle files, organized into well-signaled sections; per the rubric's simple-skill note, well-organized sections with no need for external references score 3.

3 / 3

Total

12

/

12

Passed

Description

57%

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 clear and specific in scope but lacks an explicit 'Use when...' trigger clause and the breadth of natural trigger terms needed for a top score. Its distinctiveness is strong thanks to the local+PR dual targeting.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when the user asks to review code, a Pull Request, or staged/local changes.'

Broaden trigger terms to common phrasings users actually say, such as 'code review', 'review my changes', and 'review PR #123'.

List concrete review actions (e.g. 'analyzes diffs, runs preflight checks, and reports structured findings') instead of the single verb 'review'.

DimensionReasoningScore

Specificity

It names the domain ('review code') and concrete scopes ('local changes (staged or working tree) and remote Pull Requests (by ID or URL)'), but offers a single review action across two targets rather than a list of multiple distinct concrete actions like the score-3 anchor.

2 / 3

Completeness

It answers 'what' (reviews local changes and remote PRs, focusing on correctness/maintainability/standards) but the 'when' is only implied by 'Use this skill to review code' — there is no explicit 'Use when...' trigger clause, which caps completeness at 2 per the rubric guidelines.

2 / 3

Trigger Term Quality

It includes relevant keywords ('review code', 'Pull Requests', 'PR') a user might say, but misses common natural variations such as 'code review', 'review my changes', or 'review PR #123'.

2 / 3

Distinctiveness Conflict Risk

The combination of local working-tree/staged review plus remote PR-by-ID/URL review carves a clear, distinct niche that is unlikely to trigger for the wrong skill.

3 / 3

Total

9

/

12

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
google-gemini/gemini-cli
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.