This skill content is essentially a description of what code review is rather than actionable guidance for performing it. It lacks concrete review criteria, checklists, example outputs, or any executable guidance. The content explains concepts Claude already understands while failing to provide the specific, actionable instructions that would make this skill useful.

Suggestions

Add a concrete checklist of specific things to check during code review (e.g., error handling, input validation, naming conventions, security issues)

Include example review output format showing how to structure feedback with severity levels and specific line references

Provide language-specific review criteria or reference files for different programming languages

Remove the explanatory content about what code review is and replace with actionable review steps and criteria

Dimension	Reasoning	Score
Conciseness	The content explains what code review is and how it works, which Claude already knows. Phrases like 'This skill helps you review code' and 'it will look at the code and give you feedback' are unnecessary padding.	1 / 3
Actionability	No concrete guidance, code examples, commands, or specific review criteria are provided. The content describes rather than instructs, with vague phrases like 'things that could be improved.'	1 / 3
Workflow Clarity	No workflow or process is defined. There are no steps for how to conduct a review, what to check, or how to structure feedback. The bullet points are vague categories, not actionable steps.	1 / 3
Progressive Disclosure	The content is short and has some section structure (How it works, Tips), but there are no references to additional resources, examples, or detailed guides that would help with more complex review scenarios.	2 / 3
	Total	5 / 12 Passed

Description

14%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is too vague and generic to be useful for skill selection. It lacks specific actions, explicit trigger conditions, and distinctive language that would help Claude choose this skill over others in a large skill library.

Suggestions

Add specific concrete actions like 'Identifies bugs, suggests refactoring improvements, checks coding standards, reviews pull requests'

Add a 'Use when...' clause with trigger terms like 'review my code', 'code review', 'PR review', 'check code quality', 'improve this code'

Include distinctive scope markers to differentiate from related skills (e.g., specify languages supported, types of reviews performed, or whether it's for PRs vs general code)

Dimension	Reasoning	Score
Specificity	The description uses vague language ('reviews code', 'helps with code quality') without listing any concrete actions like 'identifies bugs', 'suggests refactoring', or 'checks style compliance'.	1 / 3
Completeness	The description weakly addresses 'what' with vague terms and completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Contains some relevant keywords ('code', 'code quality') that users might say, but misses common variations like 'review PR', 'code review', 'lint', 'refactor', or 'clean up code'.	2 / 3
Distinctiveness Conflict Risk	Extremely generic - 'code' and 'code quality' could overlap with debugging skills, linting skills, testing skills, refactoring skills, or any general coding assistance skill.	1 / 3
	Total	5 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Reviewed

4 months ago

Table of Contents

Discovery Implementation Validation