max

Cleans up and improves existing code without changing behavior.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

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 a well-structured, lean role definition with concrete actionable guidance, explicit test-validation feedback loops, and clean section organization, all of which fit the rubric's top anchors.

Dimension	Reasoning	Score
Conciseness	The body is lean and disciplined — tight bullet points with no padding and no explanation of concepts Claude already knows (e.g., what refactoring is), assuming Claude's competence throughout.	3 / 3
Actionability	Concrete, specific guidance throughout ('eliminate N+1 queries, add missing indexes', 'Rule of Three... 3 real instances', 'functions longer than ~40 lines', '5+ params') plus a copy-paste-ready structured report template; the instruction-only format is fully actionable.	3 / 3
Workflow Clarity	Clear sequencing with explicit validation checkpoints ('Run Quinn's full test suite before and after. If any test fails, revert') and a feedback loop for refactor/batch operations, plus a sequenced handoff protocol.	3 / 3
Progressive Disclosure	Self-contained single file with no bundle files present and no nested references; content is organized into clear, well-signaled sections (Responsibilities, Output Format, Handoff Protocol, Interaction Style).	3 / 3
	Total	12 / 12 Passed

Description

50%

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 concise and states the core constraint (no behavior change), but it omits explicit trigger guidance and natural keywords, capping both completeness and trigger quality at the mid level.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g. 'Use when the user asks to refactor, optimize, or clean up already-tested code without changing behavior.'

Expand specificity by naming the concrete actions Max performs (algorithmic optimization, abstraction, dead-code removal, readability).

Include natural trigger terms users would say — 'refactor', 'optimize', 'clean up code', 'remove dead code'.

Dimension	Reasoning	Score
Specificity	Names the domain ('existing code') and two actions ('cleans up', 'improves') plus the constraint ('without changing behavior'), but does not enumerate the multiple concrete actions (refactoring, optimization, dead-code removal) the body covers, so it is not comprehensive.	2 / 3
Completeness	It answers 'what' but lacks any 'Use when...' clause, so 'when' is only implied; per guidelines a missing explicit trigger caps completeness at 2.	2 / 3
Trigger Term Quality	It implies the domain but includes no natural trigger keywords a user would say ('refactor', 'optimize', 'clean up code'); relevant but missing common variations.	2 / 3
Distinctiveness Conflict Risk	'Cleans up and improves existing code' is a recognizable niche but is generic enough to overlap with general coding skills and lacks distinct triggers.	2 / 3
	Total	8 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

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

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Commit: 6e69f00

Reviewed: 5 days 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.