clean-code

This skill embodies the principles of "Clean Code" by Robert C. Martin (Uncle Bob). Use it to transform "code that works" into "code that is clean."

Quality

19%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

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

Quality

Discovery

17%

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 overly abstract and relies on a book reference rather than specifying concrete actions or trigger conditions. It lacks natural user keywords, specific capabilities, and clear guidance on when Claude should select this skill over others. It would be easily confused with any general code quality or refactoring skill.

Suggestions

List specific concrete actions the skill performs, e.g., 'Refactors functions for single responsibility, improves variable and method naming, reduces code duplication, simplifies complex conditionals.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to refactor code, improve readability, apply clean code principles, reduce complexity, or review code quality.'

Include distinguishing details that separate this from generic code review skills, such as mentioning specific Clean Code principles applied (SRP, DRY, meaningful names, small functions).

Dimension	Reasoning	Score
Specificity	The description mentions no concrete actions—'transform code that works into code that is clean' is abstract and metaphorical. It does not list specific capabilities like refactoring functions, renaming variables, reducing complexity, etc.	1 / 3
Completeness	There is a weak 'what' (transform code to be clean) and a partial 'when' ('Use it to transform code that works into code that is clean'), but neither is explicit or detailed. The 'Use it to...' clause is more of a vague purpose statement than a concrete trigger condition.	2 / 3
Trigger Term Quality	The only potentially useful trigger terms are 'Clean Code' and 'Robert C. Martin,' which are references rather than natural user keywords. Users are more likely to say 'refactor,' 'readability,' 'naming conventions,' or 'code quality,' none of which appear.	1 / 3
Distinctiveness Conflict Risk	The description is extremely generic—any code review, linting, refactoring, or style-related skill could overlap. There are no distinct triggers or a clear niche that would differentiate it from other code quality skills.	1 / 3
	Total	5 / 12 Passed

Implementation

22%

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

This skill reads as a condensed summary of Robert C. Martin's 'Clean Code' book rather than an actionable skill for Claude. It explains principles Claude already knows from training data without providing concrete workflows, executable refactoring steps, or specific transformation patterns. The content would be far more valuable if it provided a clear refactoring workflow with before/after code examples and validation checkpoints.

Suggestions

Replace the principle summaries with a concrete refactoring workflow: e.g., 1. Identify code smells → 2. Apply specific transformation → 3. Validate with tests → 4. Review naming → 5. Verify single responsibility

Add concrete before/after code transformation examples showing exactly how to apply each principle, rather than just describing the principle

Remove content Claude already knows (basic Clean Code principles, TDD laws, FIRST principles) and focus on project-specific conventions or non-obvious application patterns

Add validation checkpoints to the implementation checklist, such as 'Run tests after each refactoring step' and 'Verify no behavior changes before proceeding'

Dimension	Reasoning	Score
Conciseness	The skill summarizes Clean Code principles that Claude already knows well. While it's organized as bullet points (not overly verbose prose), the entire content is essentially a book summary of concepts Claude has deeply internalized from training data. The 'When to Use' section and philosophical quote add little value.	2 / 3
Actionability	The content is almost entirely descriptive principles and guidelines rather than concrete, executable instructions. There's one small Python example in the Comments section, but it's illustrative rather than actionable. There are no specific commands, refactoring recipes, or step-by-step procedures Claude can execute.	1 / 3
Workflow Clarity	There is no clear workflow or sequenced process for how to actually apply clean code principles to a piece of code. The checklist at the end is a static list of yes/no questions but lacks any sequence, validation steps, or feedback loops for the refactoring process.	1 / 3
Progressive Disclosure	The content is organized into numbered sections with clear headers, which aids scanning. However, it's a monolithic document with no references to external files for deeper content, and all 9 sections are presented at the same level of detail inline, making it a wall of bullet points.	2 / 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: 93c57b2

Reviewed: 6 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.