CtrlK
BlogDocsLog inGet started
Tessl Logo

refactor

Restructure existing code without changing behaviour

61

Quality

72%

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 ./app/src/main/assets/skills/refactor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

87%

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

A well-structured, lean instruction skill with concrete tool guidance and clean sections; the only real gap is an explicit verify-fix-reverify loop for the post-edit validation step.

Suggestions

Make the post-edit feedback loop explicit: "If Grep finds stale references, fix them and re-verify before moving on" to lift workflow_clarity to 3.

Add a one-line pre-flight check that the prior-read requirement is satisfied before the first edit, so the sequence's first checkpoint is explicit rather than buried in the Discipline section.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: short discipline rules and named tools with no explanation of concepts Claude already knows, so every token earns its place.

3 / 3

Actionability

Guidance is concrete and executable — named tools (ListFiles, Grep, EnterPlanMode) with specific checks ("Verify with Grep that no stale references remain") and decision rules; per the instruction-only scoring note, absence of code is not penalized when guidance is this actionable.

3 / 3

Workflow Clarity

Clear Before/After sequencing with an explicit verification step exists, but the error-recovery feedback loop (what to do when verification finds stale references) is only implicit rather than spelled out, which the top anchor requires.

2 / 3

Progressive Disclosure

The skill is under 50 lines, single-purpose, needs no external references, and is organized into clear sections (Discipline, Before any edit, After every edit, Don't), meeting the simple-skill allowance for a top score.

3 / 3

Total

11

/

12

Passed

Description

57%

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 distinctive but thin: it states one action and lacks in-field trigger guidance, so most dimensions land at the middle anchor rather than the top.

Suggestions

Add concrete actions to the description (e.g. "rename symbols, extract components, split modules") to lift specificity from one action to several.

Fold in natural trigger terms users actually say ("refactor", "clean up", "rename") and an explicit "Use when..." clause to reach completeness 3.

Consider merging the separate when_to_use guidance into the description so both what and when appear in the evaluated field.

DimensionReasoningScore

Specificity

"Restructure existing code" names the domain and a concrete action, but lists only a single action rather than multiple specific operations, matching the "names domain and some actions, not comprehensive" anchor.

2 / 3

Completeness

It clearly states what the skill does ("Restructure existing code without changing behaviour") but the description field itself contains no "Use when..." trigger clause, so per the rubric guideline completeness is capped at 2.

2 / 3

Trigger Term Quality

"restructure" is a natural term a user might say, but the description omits common variations like "refactor" or "clean up", fitting "some relevant keywords but missing common variations"; it is not a 1 because it avoids jargon.

2 / 3

Distinctiveness Conflict Risk

The qualifier "without changing behaviour" carves a clear behavior-preserving niche that is unlikely to trigger for feature-work or bug-fixing skills, matching the "clear niche with distinct triggers" anchor.

3 / 3

Total

9

/

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
shiaho777/web-to-app
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.