CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

simplify-code

Parallel 4-agent cleanup of recent code changes.

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/software-development/simplify-code/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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 an unusually well-engineered process document: exact commands, copy-paste reviewer prompts, risk-tiered application rules with explicit test-verification loops, and honest treatment of failure modes (no delegation, empty diffs, conflicting reviewers). Its weaknesses are redundancy (risk tiers, large-diff warnings, and the bug-hunt boundary are each stated 2-3 times) and its monolithic structure, which inlines reference-grade material instead of splitting it into bundle files.

Suggestions

Deduplicate the SAFE/CAREFUL/RISKY definitions — define the tiers once (Phase 2) and reference them by name in Phase 3 instead of re-listing the examples, and merge the Phase 1 large-diff warning with the 'Large diffs blow context' pitfall.

Move the four reviewer prompt blocks into references/ files (e.g. references/reviewer-reuse.md, reviewer-quality.md, reviewer-efficiency.md, reviewer-altitude.md) and keep one-line summaries plus the shared instructions in SKILL.md, making the main file a true overview.

State the 'this is a cleanup pass, not a bug hunt' boundary once (the intro already does it well) and drop the re-statements in Pitfalls and Related, or fold them into a single one-line cross-reference.

DimensionReasoningScore

Conciseness

The body contains no filler or explanations of concepts Claude already knows, but it repeats itself materially: the SAFE/CAREFUL/RISKY tiers are defined in Phase 2 and re-listed in Phase 3, the large-diff warning appears in both Phase 1 and Pitfalls, and the 'cleanup not bug hunt' distinction is made three times (intro, Pitfalls, Related). This matches 'mostly efficient but includes some unnecessary explanation or could be tightened'; it exceeds 'minor instances of over-explanation', so not a 4.

3 / 5

Actionability

Everything is executable: exact git commands for every scope variant (`git diff HEAD~1`, `git diff main...HEAD`, `git diff -- src/foo.py`), four fully written copy-paste reviewer prompts, a structured finding format (file:line → problem → cost → fix | confidence | risk), a concrete fallback for when delegation is unavailable, and explicit per-tier apply rules. 'Every token earns its place' applies to the guidance itself; the deductions are for redundancy, not vagueness.

5 / 5

Workflow Clarity

The three phases are clearly sequenced with explicit validation checkpoints and feedback loops: 'Run tests after each file. Revert any that break', 'If a fix breaks a test, revert that one fix and report it', and re-running linter/type checks, plus a stop condition when no changes exist. This matches 'clear sequence with explicit validation steps; feedback loops for error recovery'.

5 / 5

Progressive Disclosure

Section headers are clear and well-ordered, but the entire skill is one ~270-line inline file with no bundle files: the four substantial reviewer prompt blocks and the 11-item Pitfalls catalog are prime candidates for references/ files that would keep SKILL.md a lean overview. This matches 'some structure but could be better organized; content that should be separate is inline'; it is not a 4 because there are no reference files at all, and not a 2 because the inline content is well-sectioned, not a headerless wall of API reference.

3 / 5

Total

16

/

20

Passed

Description

50%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 terse and honest but under-sells the skill: it states the mechanism (4 parallel agents) and domain (cleanup of recent changes) without a single concrete cleanup action, any trigger guidance, or the synonyms a user would naturally say. It functions as a label rather than a routing description.

Suggestions

Add a 'Use when...' clause with concrete trigger phrases, e.g. 'Use when the user says simplify, clean up my changes, or /simplify'.

List 2-3 concrete actions the cleanup performs — e.g. 'removes duplicated logic, dead code, needless complexity, and band-aid fixes' — instead of the generic word 'cleanup'.

Include natural synonyms (simplify, refactor, clean up, review my recent changes) so the skill triggers on the phrasing users actually use; 'simplify' is notably absent even though the skill name is simplify-code.

DimensionReasoningScore

Specificity

The description names the domain ("cleanup of recent code changes") and one concrete framing ("Parallel 4-agent") but lists no specific cleanup actions such as removing duplication, dead code, or flattening complexity, so it matches 'names domain and 1-2 concrete actions, but not comprehensive'. It is not a 4 because it does not list several specific actions, and not a 2 because the domain plus the concrete 4-agent mechanism is more substantive than bare 'Processes code'.

3 / 5

Completeness

The 'what' is clear (parallel 4-agent cleanup of recent changes) but there is no 'Use when...' clause or equivalent explicit trigger guidance, which the judging guidelines explicitly cap at 3 ('has a clear what but when is missing or only weakly implied'). It cannot be a 4 because 4 requires both what and when to be present.

3 / 5

Trigger Term Quality

Terms like "cleanup" and "code changes" are phrases a user might say, but the most natural trigger words for this skill — "simplify", "refactor", "clean up my code" — are absent, matching 'some relevant keywords but missing common variations or synonyms'. It is not a 4 because there is effectively no synonym coverage at all.

3 / 5

Distinctiveness Conflict Risk

"Code cleanup" overlaps broadly with generic refactoring and code-review skills, and the description alone does nothing to carve out this skill's niche (the body's bug-hunt-vs-cleanup distinction is not surfaced here), matching 'somewhat specific but could still overlap with similar skills'. Not a 4 because the description text itself does not establish distinct triggers.

3 / 5

Total

12

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

NousResearch/hermes-agent

Path

skills/software-development/simplify-code/SKILL.md

Reviewed

Table of Contents

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.