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

57%

Does it follow best practices?

Impact

100%

1.00x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/code-simplifier/skills/code-simplifier/SKILL.md

Quality

Content

64%

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

This is a solid, well-structured skill with excellent concrete examples demonstrating real refactoring patterns. Its main weaknesses are moderate verbosity (some principles are obvious to Claude) and a workflow that lacks explicit error recovery loops when linting or tests fail. The before/after code examples are a strong point that makes the skill highly actionable.

Suggestions

Add explicit feedback loops to the workflow: 'If linter fails, fix issues and re-run. If tests fail, revert changes and re-analyze the simplification approach.'

Trim obvious guidance that Claude already knows (e.g., 'Use clear, descriptive variable and function names', 'Never change what the code does') to reduce token usage.

Dimension	Reasoning	Score
Conciseness	The skill is reasonably well-structured but includes some unnecessary verbosity. Principles like 'Never change what the code does — only how it does it' and lists of things to avoid are somewhat obvious for Claude. The examples section, while useful, is lengthy and could be more compact. Some bullet points restate common sense (e.g., 'Use clear, descriptive variable and function names').	2 / 3
Actionability	The skill provides concrete, executable code examples in multiple languages (Go, TypeScript) showing clear before/after transformations. The workflow section gives specific steps including running linters and tests. The examples are copy-paste ready and demonstrate real refactoring patterns.	3 / 3
Workflow Clarity	The workflow has a clear sequence (read standards → identify changes → analyze → apply → lint → test → summarize) and includes validation via linting and testing. However, there's no explicit feedback loop for when linting or tests fail — no 'if tests fail, revert and re-analyze' checkpoint, which is important for a skill that modifies code.	2 / 3
Progressive Disclosure	The content is well-organized with clear sections and headers, but it's somewhat monolithic — the three detailed examples could be in a separate EXAMPLES.md file. For a standalone skill with no bundle files, the inline examples are acceptable but the overall length pushes it toward needing better separation.	2 / 3
	Total	9 / 12 Passed

Description

50%

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 communicates the general purpose of the skill—simplifying and refining code—but lacks the concrete action specificity and explicit trigger guidance needed for reliable skill selection. It would benefit from listing specific refactoring actions and adding a 'Use when...' clause with natural user trigger terms like 'clean up', 'refactor', or 'simplify my code'.

Suggestions

Add an explicit 'Use when...' clause with natural trigger terms such as 'clean up code', 'refactor', 'simplify', 'reduce complexity', 'improve readability'.

List more concrete actions like 'removes dead code, renames variables for clarity, extracts helper functions, reduces nesting' to improve specificity.

Include common user phrasings and synonyms (e.g., 'tidy up', 'make code cleaner', 'code cleanup') to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (code) and some actions ('simplifies', 'refines'), and mentions goals ('clarity, consistency, maintainability'), but doesn't list multiple concrete specific actions like 'remove dead code, rename variables, extract functions'.	2 / 3
Completeness	The 'what' is reasonably covered (simplifies and refines code), and there's a partial 'when' hint ('focuses on recently modified code'), but there is no explicit 'Use when...' clause with trigger guidance, which caps this at 2 per the rubric.	2 / 3
Trigger Term Quality	Includes some relevant terms like 'simplifies', 'refines', 'clarity', 'maintainability', but misses common natural user terms like 'clean up code', 'refactor', 'code review', 'tidy up', 'reduce complexity'.	2 / 3
Distinctiveness Conflict Risk	Somewhat specific to code simplification/refinement, but could easily overlap with general code review, refactoring, or linting skills. The mention of 'recently modified code' adds some distinctiveness but not enough to clearly carve out a unique niche.	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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: mattermost/mattermost-ai-marketplace
Commit: 83f690a

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