CtrlK
BlogDocsLog inGet started
Tessl Logo

simplify

Review recent code changes for reuse, code quality, and efficiency, then directly apply straightforward cleanup improvements. Use when the user wants a post-implementation cleanup pass, pre-PR polish, or asks to simplify/refine recent changes. Invoke with `/simplify` or `/simplify <focus>`.

79

Quality

100%

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

100%

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

The body is a lean, fully actionable cleanup workflow with concrete commands, parallel-pass configuration, and explicit verification checkpoints. It is well-organized as a single overview with no unnecessary concept padding.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains git or code-reuse concepts — and every section (scope detection, parallel passes, aggregation, apply, verify) earns its tokens; the bolded anti-fork warning is emphatic but prevents a real failure mode rather than padding concepts, so it clears the lean-and-efficient level 3 rather than the could-be-tightened level 2.

3 / 3

Actionability

Provides executable commands (`git diff HEAD --name-only`, `git ls-files --modified --others --exclude-standard`) and concrete tool configuration (`subagent_type: "general-purpose"`, `run_in_background: false`) plus copy-ready fix examples, matching the fully-executable level 3 rather than the pseudocode/incomplete level 2.

3 / 3

Workflow Clarity

Five clearly sequenced steps with explicit validation in Step 5 (focused tests, project quality checks, fallback to targeted build/typecheck/lint) and a stop condition in Step 1.6, matching the clear-sequence-with-validation level 3 rather than the checkpoint-missing level 2.

3 / 3

Progressive Disclosure

No bundle files exist and the 111-line body is a single well-organized overview with clearly labeled sections (Steps 1–5), which per the simple-skills scoring note qualifies for level 3 without external references rather than the poorly-organized or monolithic lower levels.

3 / 3

Total

12

/

12

Passed

Description

100%

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, specific, and provides explicit what-and-when triggers with natural user phrasing. It carves a distinct niche (post-implementation cleanup / pre-PR polish) with low conflict risk.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: reviews for 'reuse, code quality, and efficiency' and 'directly apply straightforward cleanup improvements', matching the anchor for three concrete actions rather than the partial domain-only level 2.

3 / 3

Completeness

Explicitly answers both what (review for reuse/quality/efficiency and apply improvements) and when ('Use when the user wants a post-implementation cleanup pass, pre-PR polish, or asks to simplify/refine recent changes'), matching the explicit-trigger level 3 rather than the implied-when level 2.

3 / 3

Trigger Term Quality

Covers natural user phrases a person would actually say — 'post-implementation cleanup pass', 'pre-PR polish', 'simplify/refine recent changes' — with good variation coverage rather than the missing-common-variations level 2.

3 / 3

Distinctiveness Conflict Risk

Carves a clear niche (cleanup of recent changes before a PR) with distinct triggers unlikely to collide with other skills, matching the clear-niche level 3 rather than the still-overlapping level 2.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
QwenLM/qwen-code
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.