CtrlK
BlogDocsLog inGet started
Tessl Logo

simplify

Simplifies code for clarity without changing behavior. Use for readability, maintainability, and complexity reduction after behavior is understood.

64

Quality

75%

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 ./src/skills/simplify/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 a well-structured, lean methodology with concrete signals, an explicitly sequenced process, and emphasized validation throughout. It lands at 4 across dimensions due to minor redundancy between sections and an implicit rather than fully structured error-recovery loop.

DimensionReasoningScore

Conciseness

The body is lean with no padding about concepts Claude already knows, though the Five Principles and Step 2 signals overlap somewhat and could be tightened.

4 / 5

Actionability

As an instruction-only skill it provides concrete, recognizable signal lists (deep nesting, nested ternaries, boolean flag arguments, dead code) and per-change checklists, with only minor principle-level gaps and no code examples (appropriate here).

4 / 5

Workflow Clarity

The four-step process is clearly sequenced with per-change validation ('Keep it only when the evidence supports preservation') and a dedicated final-state verification section, falling just short of a structured validate→fix→retry recovery loop.

4 / 5

Progressive Disclosure

Self-contained skill with no bundle files, organized under clear headers and logical sections; the Five Principles section is somewhat long and slightly overlaps the Process, keeping it just below the top anchor.

4 / 5

Total

16

/

20

Passed

Description

75%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 concise and answers both what and when with concrete, behavior-preserving framing and natural trigger terms. It sits just below the top anchor because its 'when' clause names dimensions rather than concrete triggering situations and omits common synonyms like 'refactor'.

DimensionReasoningScore

Specificity

Lists several concrete facets ('Simplifies code for clarity', 'readability, maintainability, and complexity reduction') naming the domain and multiple specific actions, with only minor coverage gaps versus a fully comprehensive list.

4 / 5

Completeness

Explicitly states both what ('Simplifies code for clarity without changing behavior') and when ('Use for readability, maintainability, and complexity reduction after behavior is understood'), though the 'when' lists abstract qualities rather than concrete triggering scenarios.

4 / 5

Trigger Term Quality

Natural terms like 'clarity', 'readability', 'maintainability', and 'complexity' are phrases users would say, but common synonyms like 'refactor' or 'clean up' are missing, keeping it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

The 'without changing behavior' constraint carves a clear niche distinct from general refactoring, with only minor overlap risk against generic code-review skills.

4 / 5

Total

16

/

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
alvinunreal/oh-my-opencode-slim
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.