code-review-checklist

Comprehensive checklist for conducting thorough code reviews covering functionality, security, performance, and maintainability

Quality

30%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Risky

Do not use without reviewing

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/code-review-checklist/SKILL.md

Quality

Discovery

32%

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 identifies its domain (code reviews) and lists high-level coverage areas, but reads more like a document title than a skill description. It lacks concrete actions, explicit trigger guidance ('Use when...'), and natural keyword variations that would help Claude reliably select it from a large skill set.

Suggestions

Add an explicit 'Use when...' clause with trigger scenarios, e.g., 'Use when the user asks to review code, check a pull request, or wants feedback on code quality.'

Replace the high-level category list with specific concrete actions, e.g., 'Checks for security vulnerabilities, identifies performance bottlenecks, flags error handling gaps, and verifies test coverage.'

Include natural keyword variations users might say: 'PR review', 'pull request', 'code feedback', 'review my code', 'code quality check'.

Dimension	Reasoning	Score
Specificity	Names the domain (code reviews) and lists categories (functionality, security, performance, maintainability), but doesn't describe concrete actions like 'check for SQL injection', 'verify error handling', or 'flag N+1 queries'. The categories are high-level rather than specific actions.	2 / 3
Completeness	Describes what it is (a checklist for code reviews) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' portion is also weak (it's a noun phrase describing a checklist rather than actions), so this scores a 1.	1 / 3
Trigger Term Quality	Includes 'code review' which is a strong natural trigger term, and related terms like 'security', 'performance', 'maintainability'. However, it misses common variations users might say like 'review my PR', 'pull request', 'code quality', 'review checklist', or 'code feedback'.	2 / 3
Distinctiveness Conflict Risk	The 'code review checklist' framing is somewhat distinctive, but the broad categories (security, performance, maintainability) could overlap with dedicated security audit skills, performance optimization skills, or general code quality skills. It's not generic enough to be a 1, but lacks the sharp niche definition of a 3.	2 / 3
	Total	7 / 12 Passed

Implementation

27%

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

This skill is excessively verbose and repetitive, presenting the same checklist items multiple times across different sections (steps, examples, and complete checklist). While the concrete good/bad code examples add value, the overall content explains many concepts Claude already knows and could be condensed to roughly 25% of its current length. The lack of any bundle structure means everything is crammed into one monolithic file with no progressive disclosure.

Suggestions

Eliminate redundancy by consolidating the step-by-step walkthrough, example checklists, and 'Complete Review Checklist' into a single concise checklist — currently the same items appear 2-3 times.

Remove explanations of basic concepts (what SQL injection is, what DRY means, what edge cases are) and keep only the checklist items and code examples.

Split detailed category-specific checklists (security, performance, code quality) into separate bundle files and reference them from a lean SKILL.md overview.

Add a concrete workflow with validation steps — e.g., specify what tool commands to run (linters, security scanners), how to prioritize findings, and when to approve vs request changes.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~350+ lines. Explains basic concepts Claude already knows (what edge cases are, what SQL injection is, what DRY means). Massive redundancy: the same checklist items appear in the step-by-step walkthrough, the examples, AND the 'Complete Review Checklist' section. The 'When to Use This Skill' section is unnecessary padding. Review comment templates and best practices sections explain things any competent reviewer already knows.	1 / 3
Actionability	The code examples showing good vs bad patterns are concrete and executable, which is valuable. However, the skill is fundamentally a checklist/reference document rather than executable guidance — it tells Claude what to check but doesn't provide specific commands or tools to run. The checklists themselves are generic and not tied to any specific tooling or workflow.	2 / 3
Workflow Clarity	Steps are listed (Steps 1-6) but they are essentially just categories of things to check, not a true workflow with validation checkpoints or feedback loops. There's no guidance on what to do when issues are found (beyond 'fix it'), no prioritization of findings, and no explicit verification that the review is complete before approval.	2 / 3
Progressive Disclosure	Monolithic wall of text with no bundle files to reference. All content is inline in a single massive file. The 'Related Skills' and 'Additional Resources' sections reference external links and other skills but the core content that could be split (security checklist, performance checklist, code quality checklist) is all dumped into one file with heavy repetition.	1 / 3
	Total	6 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: sickn33/antigravity-awesome-skills
Commit: d89c349

Reviewed: about 13 hours ago

Table of Contents

Discovery Implementation Validation

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.