code-simplifier

Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.

1.00x

Quality

63%

Does it follow best practices?

Impact

100%

1.00x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/code-simplifier/skills/code-simplifier/SKILL.md

Quality

Content

77%Weight 40%Scale 1-3

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

The body is highly actionable with concrete examples and a validated workflow, but it is somewhat verbose with overlapping process sections and makes no use of progressive disclosure despite its length.

Suggestions

Merge the Refinement Process and Workflow sections to remove redundancy and trim obvious principles Claude already knows.

Move the three before/after examples into a referenced EXAMPLES.md (or a single references file) and keep only a compact quick-start example inline, enabling one-level-deep progressive disclosure.

Add an explicit 'if tests or linter fail, fix and re-run' feedback loop to make the workflow's recovery path unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and leads with concrete examples, but the Refinement Process and Workflow sections overlap, and several principles ('Reduce unnecessary complexity and nesting', 'Eliminate redundant code') restate what Claude already knows, fitting 'mostly efficient but could be tightened' rather than the lean level-3 anchor.	2 / 3
Actionability	It provides three complete, executable before/after code examples (Go and TypeScript) plus concrete commands ('make check-style-fix', 'git status/diff') and a specific step sequence, matching the 'fully executable code/commands; copy-paste ready' anchor.	3 / 3
Workflow Clarity	The 7-step Workflow includes explicit validation checkpoints ('Run the project's linter', 'Run relevant tests to confirm functionality is preserved'), satisfying the 'clear sequence with explicit validation steps' anchor; the test-failure recovery loop is only implicit, which keeps it from being unambiguous but the checkpoints are clearly present.	3 / 3
Progressive Disclosure	Sections are well organized, but there are no bundle files and all content — including three lengthy before/after example blocks — lives inline in a single ~170-line file with no one-level-deep references or signaling, matching the level-2 'content that should be separate is inline' anchor rather than the split-and-linked level-3 example.	2 / 3
	Total	10 / 12 Passed

Description

50%Weight 40%Scale 1-3

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 clearly conveys what the skill does and its scoping behavior, but lacks an explicit 'Use when...' trigger and uses fairly general action language, leaving it at the midpoint across all dimensions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to simplify, clean up, or refactor recently changed code.'

Include natural user variations such as 'refactor' and 'clean up code' alongside 'simplify' and 'refine'.

Sharpen the action list toward concrete outcomes (e.g. 'reduces nesting, consolidates repeated logic, applies project style rules') to lift specificity.

Dimension	Reasoning	Score
Specificity	It names the domain (code) and several actions ('Simplifies and refines', 'preserving all functionality'), but the actions are general rather than a comprehensive list of concrete operations, matching the level-2 anchor rather than the multi-action level-3 example.	2 / 3
Completeness	The 'what' is clearly stated, but the only temporal guidance is the scope phrase 'Focuses on recently modified code unless instructed otherwise', which is not an explicit 'Use when...' trigger; per the guidelines a missing explicit trigger caps completeness at 2.	2 / 3
Trigger Term Quality	Terms like 'Simplifies', 'refines', 'clarity', 'consistency', and 'maintainability' are plausible user language, but common variations such as 'refactor' or 'clean up' are absent and there is no explicit trigger clause, fitting the level-2 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	The 'recently modified code' focus and 'preserving all functionality' framing carve out a niche, yet 'Simplifies and refines code' broadly overlaps with general refactoring or cleanup skills, matching the level-2 'somewhat specific but could still overlap' anchor.	2 / 3
	Total	8 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: mattermost/mattermost-ai-marketplace
Path: plugins/code-simplifier/skills/code-simplifier/SKILL.md
Commit: 90ab32d

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