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.

67

Quality

80%

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

85%

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

The body is lean, well-structured, and has a clear validated workflow, but its actionability is held back by the absence of concrete before/after examples illustrating the simplifications.

Suggestions

Add one or two short before/after code snippets (e.g. a nested ternary replaced with control flow) to make the guidance concrete and copy-paste ready.

Consolidate the repeated behavior-preservation guidance so the principle is stated once and referenced, trimming redundancy across Principles, Process, and Verification.

DimensionReasoningScore

Conciseness

The body is bullet-driven and assumes Claude's competence, with no padding explaining what refactoring or code is; behavior-preservation recurs but as brief reinforcement rather than verbose restatement.

3 / 3

Actionability

Concrete signals (deep nesting, nested ternaries, boolean flag arguments) and do/don't lists are actionable, but there are no worked before/after examples, leaving the transformation guidance more directive than copy-paste ready.

2 / 3

Workflow Clarity

A clear four-step process is sequenced with explicit validation checkpoints ("Run relevant tests", "Keep it only if behavior is preserved") and a closing Verification Checklist for error recovery.

3 / 3

Progressive Disclosure

The skill is a single self-contained file with no bundle references and well-organized sections (Overview, Principles, Process, Checklist) giving easy navigation; no splitting is needed at this length.

3 / 3

Total

11

/

12

Passed

Description

75%

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 well-formed with third-person voice, an explicit "Use for" trigger, and a clear niche, but it under-specifies concrete actions and misses common trigger phrasings.

Suggestions

Add concrete actions to raise specificity, e.g. "Simplifies code for clarity without changing behavior — flattens nesting, extracts helpers, removes dead code. Use when ..."

Broaden trigger terms with phrasings users actually say, such as "refactor", "clean up", "make this more readable", alongside readability/maintainability/complexity.

DimensionReasoningScore

Specificity

"Simplifies code for clarity without changing behavior" names the domain and one core action, but it does not enumerate multiple specific concrete actions (e.g. flattening nesting, extracting helpers) the way the anchor-3 example does.

2 / 3

Completeness

It states what the skill does ("Simplifies code for clarity without changing behavior") and gives an explicit "Use for ... after behavior is understood" trigger clause, answering both what and when.

3 / 3

Trigger Term Quality

"readability, maintainability, and complexity reduction" are reasonably natural terms, but common variations users would actually say ("refactor", "clean up", "simplify this") are absent, leaving coverage incomplete.

2 / 3

Distinctiveness Conflict Risk

The behavior-preserving simplification framing carves a clear niche distinct from a general refactor or feature skill, with triggers unlikely to fire for unrelated skills.

3 / 3

Total

10

/

12

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.