CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-reviewer

Identify improvement opportunities in Claude Code skills through targeted review operations. Complements review-multi by focusing on actionable improvements rather than scoring. Use when seeking specific improvements, conducting improvement-focused reviews, or identifying enhancement opportunities for existing skills.

54

Quality

61%

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

The canonical home for this skill is skill-reviewer in fernandezbaptiste/Skrillz

SKILL.md
Quality
Evals
Security

Quality

Content

61%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 content is well-structured and token-efficient for an instruction-only skill, but its operations read as high-level prompting questions rather than concrete, executable review procedures with validation checkpoints.

Suggestions

Convert each operation's Process from prompting questions into concrete, executable steps (e.g., specific checks to run, criteria for flagging an issue).

Specify a concrete output format for each operation's 'Output' (e.g., a structured findings list with severity and suggested fix) instead of 'List of content improvements with priorities'.

Add a validation/verification step to each operation so Claude confirms its findings are actionable before reporting (a lightweight feedback loop).

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence without explaining concepts Claude already knows; only minor padding remains (the closing tagline and the Quick Reference table that repeats the four operations).

4 / 5

Actionability

Each operation gives a structured Process with specific focus areas, but the steps are framed as prompting questions ('could any be more concrete?') rather than executable methods, and output formats are underspecified.

3 / 5

Workflow Clarity

Each operation has a clearly numbered 4-step sequence, but there are no validation checkpoints or feedback loops; the steps read as a checklist rather than a guarded workflow.

3 / 5

Progressive Disclosure

Content is well-organized into Overview, When to Use, Operations, and Quick Reference sections in a single self-contained file with no nested references, though the Operations section could offload detail to references if the skill grew.

4 / 5

Total

14

/

20

Passed

Description

62%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 answers both what and when and distinguishes the skill from review-multi, but its trigger terms and named actions are more abstract than concrete, leaving it solid but not exemplary.

Suggestions

Add concrete trigger phrases users would naturally say (e.g., 'Use when the user asks to improve, refine, or enhance an existing skill').

Name the specific review operations (content, usability, integration, efficiency) in the description so capabilities are concrete rather than implied.

Replace abstract phrasing like 'enhancement opportunities' with more natural synonyms a user would actually utter.

DimensionReasoningScore

Specificity

Names the domain ('improvement opportunities in Claude Code skills') and a concrete action ('targeted review operations'), but does not enumerate the specific review operations the way a score-4/5 description would; it relies on the body to list them.

3 / 5

Completeness

Explicitly states both what ('Identify improvement opportunities... through targeted review operations') and when ('Use when seeking specific improvements, conducting improvement-focused reviews...'), but the 'when' triggers are somewhat generic rather than concrete user phrases.

4 / 5

Trigger Term Quality

Includes relevant terms ('improvements', 'review', 'enhancement opportunities'), but these are fairly abstract phrasings a user might not naturally say, and common variations/synonyms are limited.

3 / 5

Distinctiveness Conflict Risk

Explicitly differentiates from review-multi ('focusing on actionable improvements rather than scoring'), carving a clear niche with only minor overlap risk against related review/updater skills.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository
fernandezbaptiste/Skrillz
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.