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

51%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/clean-code/SKILL.md

Quality

Content

53%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 a well-structured, readable digest of Clean Code principles with concrete micro-examples and a checklist, but it restates knowledge Claude already has and lacks a sequenced, validated workflow for actually performing a refactor. It is self-contained and well-organized as a single file.

Suggestions

Trim or condense widely-known explanations (e.g. the newspaper metaphor, Law of Demeter definition) to keep only operational guidance Claude would not already infer.

Add a short ordered refactor workflow with an explicit validation checkpoint (e.g. run focused tests before/after, confirm behavior preserved) to lift workflow clarity.

Provide at least one complete before/after code example showing the full transformation rather than only one-line illustrations.

Dimension	Reasoning	Score
Conciseness	The body is organized as terse bullet points rather than verbose prose, but it largely restates well-known Clean Code principles (Law of Demeter, F.I.R.S.T., the newspaper metaphor) that Claude already knows, fitting 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	Each principle pairs a rule with a concrete micro-example (e.g. 'elapsedTimeInDays instead of d', 'isPasswordValid is better than check') and a checklist, but there is no executable refactor procedure or complete code workflow, matching 'some concrete guidance but incomplete'.	3 / 5
Workflow Clarity	The Implementation Checklist lists criteria and the Example mentions 'verify it with focused tests', but there is no ordered multi-step sequence with validation checkpoints, so it sits at 'steps listed but validation gaps; checkpoints missing or implicit'.	3 / 5
Progressive Disclosure	The body is a single self-contained file with well-organized numbered sections (1-9) plus checklist, example, and limitations; no bundle files exist and none are needed, giving 'good structure; most content appropriately placed' with only minor organization gaps.	4 / 5
	Total	13 / 20 Passed

Description

48%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 identifies a clear, named niche (Clean Code by Uncle Bob) but relies on a vague transformative phrasing instead of concrete actions and lacks an explicit 'Use when...' trigger clause. It is reasonably distinct from other skills but would benefit from naming specific capabilities and trigger scenarios.

Suggestions

Add concrete actions, e.g. 'Refactors code for meaningful names, small functions, and clear error handling; reviews pull requests against Clean Code principles.'

Add an explicit trigger clause such as 'Use when refactoring legacy code, reviewing pull requests, or improving code quality and team standards.'

Include natural user synonyms like 'refactor', 'code review', 'code quality', or 'code smell' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ("principles of Clean Code by Robert C. Martin") but the only action is the generic "transform code that works into code that is clean" — no concrete actions like renaming, extracting functions, or removing smells, matching the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	It states a clear 'what' (embodying Clean Code principles to transform code) but lacks an explicit 'Use when...' trigger clause — "Use it to transform..." states purpose, not when to invoke it, so per the rubric cap completeness at 3.	3 / 5
Trigger Term Quality	"Clean Code", "Robert C. Martin", and "Uncle Bob" are recognizable terms a user might say, but common natural variations like "refactor", "code review", "code quality", or "code smell" are missing, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Anchoring to a named book/author ("Clean Code by Robert C. Martin (Uncle Bob)") gives a clear niche with minimal conflict risk, though it could still overlap with general code-review or refactoring skills.	4 / 5
	Total	12 / 20 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/agentic-awesome-skills
Path: skills/clean-code/SKILL.md
Commit: b1aebac

Reviewed: ~17 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.