simplify-code

Reduce complexity of over-engineered code. Identify unnecessary abstractions, remove dead code, flatten deep nesting, and simplify logic while preserving behavior.

Quality

73%

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 ./.agents/skills/simplify-code/SKILL.md

Quality

Content

75%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 body is lean, actionable, and well-structured with a clear simplification protocol and verification step. The main gap is the lack of an explicit feedback loop for test failures after destructive edits.

Suggestions

Add an explicit failure-recovery loop in Step 4 (e.g., "If tests fail, revert the change or fix and re-run until green") to push workflow_clarity to 5.

Trim the opening epigraph and "Complexity is a cost" block to tighten conciseness.

Optionally extract the smell reference tables into a bundled reference file to improve progressive-disclosure navigation.

Dimension	Reasoning	Score
Conciseness	Dense smell-to-action tables and before/after code keep the body efficient, with only minor motivational padding (the opening epigraph and "Complexity is a cost" block) that could be trimmed.	4 / 5
Actionability	Concrete tables mapping smells to specific actions plus executable before/after JavaScript/TypeScript examples and `npm run test`/`npm run build` commands give mostly copy-paste-ready guidance, with minor gaps in the table-only entries.	4 / 5
Workflow Clarity	The four-step Simplification Protocol is clearly sequenced and includes a verification step (Step 4: run tests/build), so the destructive-cap at 3 does not apply; however an explicit failure-recovery loop ("if tests fail, revert/fix and re-verify") is absent.	4 / 5
Progressive Disclosure	Content is well-organized into clear sections (Core Principle, Checklist, Protocol, When NOT to Simplify) with no external references needed for this self-contained skill; minor organization gaps keep it just below a 5.	4 / 5
	Total	16 / 20 Passed

Description

71%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 is specific and action-rich with good trigger terms, but it lacks an explicit "when to use" clause, which limits its completeness. Adding a Use-when trigger phrase would raise the score.

Suggestions

Append a "Use when..." clause naming user phrases like "simplify", "clean up", "reduce complexity", or "this is over-engineered" to satisfy the completeness dimension.

Add synonyms such as "clean up" and "refactor" to broaden natural trigger-term coverage.

Clarify the boundary from a general refactoring skill (e.g., behavior-preserving focus) to reduce conflict risk.

Dimension	Reasoning	Score
Specificity	"Identify unnecessary abstractions, remove dead code, flatten deep nesting, and simplify logic while preserving behavior" lists multiple specific concrete actions with comprehensive coverage, matching the score-5 anchor.	5 / 5
Completeness	The description gives a clear "what" but contains no "Use when..." clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Natural terms like "reduce complexity", "over-engineered", "dead code", and "simplify" are present, but common variations such as "clean up" and "refactor" are missing, so it sits just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	"Reduce complexity of over-engineered code" carves a clear niche with distinct triggers, though "simplify logic" leaves minor overlap risk with a general refactoring skill.	4 / 5
	Total	16 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: vudovn/ag-kit
Path: .agents/skills/simplify-code/SKILL.md
Commit: 211561c

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