CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ce-simplify-code

Simplify code for clarity, reuse, quality, and efficiency while preserving behavior, and prune tests and comments that carry no value. Use after implementation and before review, or to audit tests or comments in any part of a repo; use ce-debug for bugs.

Quality

92%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exceptionally tight, highly actionable orchestration skill: every step is concrete, validation and error-recovery loops are explicit, and reviewer detail is properly pushed into bundle files rather than inlined. The single weakness is that the structural review pass is buried two reference levels deep and disconnected from the Step 2 dispatch list that Step 5's summary depends on.

DimensionReasoningScore

Conciseness

The ~70-line body is dense with instruction and free of padding: no concept explanations Claude already knows, no filler — every rule earns its place (e.g., "Prioritize readable, explicit code over compact code — fewer lines is not the goal" is a real guardrail, not explanation). The long Preflight paragraph defines the skill's own scoping rule for "code" rather than teaching a known concept. This matches the score-5 anchor (lean and efficient, assumes Claude's competence).

5 / 5

Actionability

Guidance is fully concrete and executable for an orchestration skill: an ordered scope-resolution procedure (user-named → branch diff → `git diff HEAD` → conversation-edited files), an exact list of persona files to "pass the full file content" as subagent prompts with per-file applicability conditions, explicit edit-boundary rules, and a defined fallback when no subagent primitive exists. As an instruction-only skill whose guidance is this specific, it meets the score-5 anchor.

5 / 5

Workflow Clarity

Steps 1–5 (scope → parallel review → fix → verify → summarize) are clearly sequenced with explicit validation and feedback loops: a preflight stop when the scope holds no code, Step 4's typecheck/lint/test verification with "Fix simplification-caused failures or revert the responsible change", and hard guardrails for risky edits ("Never weaken or remove a test to make a check pass", proof-test protection). This matches the score-5 anchor including error-recovery loops.

5 / 5

Progressive Disclosure

The body is a lean overview with clearly signaled, verifiable references (all listed persona and reference files exist on disk, each with an explicit "read before X" trigger), which is well above score 3. It falls short of score 5's "well-signaled one-level-deep references" because the structure-review workflow is only reachable through a two-hop chain (SKILL.md → standalone-report.md → structural-pass.md → structure-evidence.py/structure-reviewer.md), and Step 5 requires reporting "structure" counts for a reviewer never named in Step 2's dispatch list — a minor organization gap.

4 / 5

Total

19

/

20

Passed

Description

88%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 description that explicitly covers what the skill does, when to use it, and how it routes against a sibling debugging skill, in third person with no padding. The only gaps are a few missing natural synonyms (e.g., "refactor", "clean up") and residual overlap risk with adjacent review/refactor skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with comprehensive coverage of the skill's domain: "Simplify code for clarity, reuse, quality, and efficiency while preserving behavior, and prune tests and comments that carry no value" — simplification is broken into four named dimensions plus test/comment pruning and a behavior-preservation constraint. This matches the score-5 anchor (multiple specific concrete actions, comprehensive coverage), not score 4, because no capability of the skill is left unenumerated.

5 / 5

Completeness

Both questions are explicitly answered: the "what" is concrete ("Simplify code for clarity, reuse, quality, and efficiency... prune tests and comments that carry no value") and the "when" is an explicit use clause with concrete triggers ("Use after implementation and before review, or to audit tests or comments in any part of a repo"). This matches the score-5 anchor exactly; the score-4 anchor's caveat ("'when' could be more explicit") does not apply.

5 / 5

Trigger Term Quality

Natural terms users would say are present — "Simplify code", "audit tests or comments", "prune" — giving good keyword coverage. It falls short of the score-5 anchor (comprehensive coverage including synonyms) because common natural variations like "refactor", "clean up", or "tidy" are absent, while clearly exceeding score 3 ("some relevant keywords but missing common variations").

4 / 5

Distinctiveness Conflict Risk

The skill has a clear niche (behavior-preserving simplification and test/comment pruning) and even includes routing guidance ("use ce-debug for bugs"), which pushes above score 3. However, broad terms like "quality" and "efficiency" and the positioning "before review" leave minor overlap risk with closely related code-review and refactoring skills in the same family, so the score-5 anchor's "minimal conflict risk" is not fully met.

4 / 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.

Validation — 14 / 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: 5 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

EveryInc/compound-engineering-plugin

Path

skills/ce-simplify-code/SKILL.md

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.