clean-code

tessl i github:sickn33/antigravity-awesome-skills --skill clean-code

Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments

43%

Overall

Validation — 69%

Implementation — 55%

Activation — 0%

SKILL.md

Review

Evals

Activation

This description fails on all dimensions by stating abstract coding philosophy rather than concrete capabilities. It lacks specific actions, natural trigger terms, explicit usage guidance, and any distinguishing characteristics that would help Claude select it appropriately from a skill library.

Suggestions

Add specific concrete actions the skill performs (e.g., 'Writes minimal, readable code without boilerplate. Refactors verbose code to be concise.')

Include a 'Use when...' clause with natural trigger terms (e.g., 'Use when writing new code, refactoring existing code, or when user asks for clean/simple/minimal implementations')

Specify the scope or domain to reduce conflict risk (e.g., is this for all languages? Specific frameworks? Code reviews vs. new code generation?)

Dimension	Reasoning	Score
Specificity	The description uses vague, abstract language like 'pragmatic coding standards' and 'no over-engineering' without listing any concrete actions Claude would perform. It describes qualities/principles rather than specific capabilities.	1 / 3
Completeness	Missing both clear 'what' (specific actions) and 'when' (no 'Use when...' clause or equivalent). The description only states philosophical principles without explaining what the skill does or when to invoke it.	1 / 3
Trigger Term Quality	Contains no natural keywords users would say when needing this skill. Terms like 'pragmatic' and 'over-engineering' are abstract concepts, not trigger phrases like 'write code', 'refactor', or 'code review'.	1 / 3
Distinctiveness Conflict Risk	Extremely generic - 'coding standards' could conflict with any code-related skill. No specific domain, language, or task type is identified to distinguish it from other coding skills.	1 / 3
	Total	4 / 12 Passed

Implementation

55%

The skill provides clear coding standards with good workflow checkpoints and validation steps, but suffers from poor content organization. The verification scripts and agent mapping sections significantly bloat what should be a concise coding standards document. The content would benefit from splitting into multiple files and adding more executable code examples.

Suggestions

Extract the 'Verification Scripts' and 'Agent → Script Mapping' sections into a separate VERIFICATION.md file and reference it with a single line

Add 2-3 concrete before/after code examples showing the anti-patterns and their fixes in actual code

Consolidate the multiple 'CRITICAL' and 'MANDATORY' sections - the repetition dilutes their impact

Create a CHECKLIST.md for the self-check and pre-edit questions, keeping only a brief summary in the main skill

Dimension	Reasoning	Score
Conciseness	The skill uses efficient table formats and avoids explaining basic concepts, but includes significant bloat: the verification scripts section with agent mappings is extensive and likely belongs in a separate file, and some sections repeat similar points (multiple 'CRITICAL' and 'MANDATORY' markers).	2 / 3
Actionability	Provides concrete rules and patterns in table format, but lacks executable code examples. The 'Quick Check' pseudo-example and script commands are helpful, but most guidance is descriptive rules rather than copy-paste ready implementations.	2 / 3
Workflow Clarity	Clear workflows with explicit validation checkpoints: 'Before Editing ANY File' section has a structured checklist, 'Self-Check Before Completing' provides verification steps, and 'Script Output Handling' defines a clear READ → SUMMARIZE → ASK → fix sequence with feedback loops.	3 / 3
Progressive Disclosure	Monolithic wall of content with no references to external files. The verification scripts section alone is ~40 lines that should be in a separate SCRIPTS.md or AGENTS.md file. All content is inline with no navigation structure.	1 / 3
	Total	8 / 12 Passed

Validation

69%

Warnings & errors only

Criteria	Description	Result
description_trigger_hint	Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...')	Warning
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
metadata_version	'metadata' field is not a dictionary	Warning
license_field	'license' field is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	11 / 16 Passed

Reviewed

19 days ago

Table of Contents

Activation 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.