CtrlK
BlogDocsLog inGet started
Tessl Logo

ce-simplify-code

Simplify settled, recently changed code for clarity, reuse, quality, and efficiency while preserving behavior. Use after implementation and before review; use ce-debug for bugs.

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

A tightly structured five-step workflow with concrete commands, explicit verification checkpoints, and well-signaled one-level-deep references to real bundle files. The only minor weakness is occasional over-explanation in the host-agnostic guardrail paragraphs.

DimensionReasoningScore

Conciseness

Lean and directive throughout with no basic-concept padding, though the tool-discovery and model-selection paragraphs carry some over-explanation that could be trimmed.

4 / 5

Actionability

Provides concrete executable guidance — 'git diff HEAD', named platform primitives ('Agent'/'Task', 'spawn_agent'), specific persona file paths, and 'Run project-wide typecheck and lint' — covering the common cases across platforms.

5 / 5

Workflow Clarity

Five clearly sequenced steps with explicit validation in Step 4 (typecheck, lint, scoped tests) and a feedback loop ('Fix simplification-caused failures or revert the responsible change'), plus preflight and bounded-dispatch gates.

5 / 5

Progressive Disclosure

The body is a well-organized overview pointing to three one-level-deep persona files under references/personas/, each clearly signaled by full path and verified to exist.

5 / 5

Total

19

/

20

Passed

Description

87%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.

A strong, specific description that clearly states both purpose and trigger timing while disambiguating from a sibling debug skill. Minor room to broaden trigger synonyms, but it answers what and when concretely.

DimensionReasoningScore

Specificity

Names the domain and multiple concrete facets of simplification — 'clarity, reuse, quality, and efficiency while preserving behavior' — but these are objectives of one action rather than several distinct actions.

4 / 5

Completeness

Explicitly answers both what ('Simplify...code for clarity, reuse, quality, and efficiency while preserving behavior') and when ('Use after implementation and before review') with concrete trigger guidance.

5 / 5

Trigger Term Quality

Includes natural phrases a user would say ('simplify settled, recently changed code', 'after implementation and before review', 'ce-debug for bugs') with good coverage, though synonyms like 'refactor' or 'clean up' are missing.

4 / 5

Distinctiveness Conflict Risk

The 'settled, recently changed code' scoping carves a clear niche and the 'use ce-debug for bugs' disambiguation minimizes conflict with adjacent skills.

5 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 3 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository
EveryInc/compound-engineering-plugin
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.