CtrlK
BlogDocsLog inGet started
Tessl Logo

code-simplifier

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

76

1.00x
Quality

63%

Does it follow best practices?

Impact

100%

1.00x

Average score across 3 eval scenarios

SecuritybySnyk

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
SKILL.md
Quality
Evals
Security

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 content is efficient, concrete, and well-structured, with executable refactoring examples and explicit verification steps in the workflow. It falls just short of top marks because of a missing failure-handling feedback loop, minor example redundancy, and a heavy inline Examples section.

DimensionReasoningScore

Conciseness

The body is mostly lean and action-oriented with no over-explanation of concepts Claude already knows, though the nested-ternary guidance is stated twice and the three before/after examples somewhat overlap, offering minor trim opportunities.

4 / 5

Actionability

Three fully worked, copy-paste-ready code refactors (Go nesting, TypeScript switch, Go field validation) plus a concrete lint command give strong executable guidance, with only minor gaps from project-specific assumptions like 'make check-style-fix' and illustrative method names.

4 / 5

Workflow Clarity

Both the Refinement Process and Workflow present clearly sequenced steps with explicit verification checkpoints (run linter, run tests, confirm functionality), but no explicit failure/retry feedback loop is documented.

4 / 5

Progressive Disclosure

The single file is well-organized under clear headers (Core Principles, Refinement Process, Scope, Workflow, Examples) with no nested or buried references; the only gap is a somewhat bulky inline Examples section for a skill exceeding 50 lines.

4 / 5

Total

16

/

20

Passed

Description

51%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 states a clear 'what' with several concrete facets but lacks an explicit 'Use when...' trigger clause and natural user-facing trigger phrases, capping completeness and trigger quality. It is reasonably distinct thanks to its recently-modified-code scope.

Suggestions

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

Surface natural user phrases such as 'refactor', 'clean up', and 'simplify' as trigger keywords.

Replace the generic verbs 'Simplifies and refines' with more concrete operations (e.g., 'reduces nesting, eliminates redundant code, and aligns with project style').

DimensionReasoningScore

Specificity

Names the domain (code) plus several concrete facets — 'clarity, consistency, and maintainability' and 'preserving all functionality' — though the verbs 'Simplifies and refines' are fairly general, leaving minor coverage gaps versus the comprehensive anchor.

4 / 5

Completeness

The 'what' is clear, but 'when' is only weakly implied via the scope statement 'Focuses on recently modified code unless instructed otherwise'; with no explicit 'Use when...' clause, completeness is capped at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Only generic keywords ('code', 'recently modified code') appear; the natural phrases a user would say ('refactor', 'clean up', 'simplify this code') and any explicit 'Use when...' trigger clause are missing.

2 / 5

Distinctiveness Conflict Risk

The refactoring-for-clarity niche plus the 'recently modified code' scope cue make it mostly distinct from sibling skills, with only minor overlap risk against general code-editing skills.

4 / 5

Total

13

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
mattermost/mattermost-ai-marketplace
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.