CtrlK
BlogDocsLog inGet started
Tessl Logo

refactoring

Per-change refactoring mechanics: count callers exactly, decide inline vs keep, collapse duplicate switch branches, route raw access through a single typed boundary, surgical one-change-per-commit, post-refactor straggler sweep for stale JSDoc and dead exports. Use when actually editing code to clean it up, when deciding whether a 1-caller helper earns its keep, or when planning a sequence of small refactor commits. For the smell catalog use code-audit; for session-long simplification use collapse-pass.

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.

A thorough, actionable refactoring methodology with executable examples, sequenced workflows, validation checkpoints, and a well-organized single-file structure. It respects Claude's competence and avoids concept re-teaching.

DimensionReasoningScore

Conciseness

Lean and code-dense — it assumes Claude's competence, never explaining what refactoring or types are, with tight prose and per-section code. Every section earns its place; not score 2, which would require unnecessary explanation it largely avoids.

3 / 3

Actionability

Concrete executable TypeScript/Svelte snippets, a caller-count decision table, a grep-based straggler sweep checklist with specific search targets, and real commit-message examples. Patterns are copy-paste-ready; not score 2, which would be pseudocode or incomplete.

3 / 3

Workflow Clarity

Clear sequences with checkpoints: 'edit → diagnostics → test → commit → next edit', a numbered post-refactor straggler sweep, and a Go-to-Definition verification step. Commits are test-validated between each, and the sweep is a separate labeled commit, satisfying the destructive/batch feedback-loop requirement.

3 / 3

Progressive Disclosure

Single-file skill with no bundle, but well-organized into clearly headed sections; per the simple-skills scoring note this can score 3 without external references. Sibling-skill links are one-level navigation aids, not nested references.

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.

A high-quality description: specific enumerated mechanics, explicit third-person trigger guidance, and active de-confliction against sibling skills. Voice is third person throughout, so no voice penalty applies.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — 'count callers exactly', 'decide inline vs keep', 'collapse duplicate switch branches', 'route raw access through a single typed boundary', 'surgical one-change-per-commit', 'post-refactor straggler sweep for stale JSDoc and dead exports'. Matches the score-3 anchor listing several concrete actions; not score 2 which only names a domain and some actions.

3 / 3

Completeness

Explicitly answers both what (the enumerated refactoring mechanics) and when ('Use when actually editing code to clean it up, when deciding whether a 1-caller helper earns its keep, or when planning a sequence of small refactor commits'). Has an explicit 'Use when' clause as the score-3 anchor requires.

3 / 3

Trigger Term Quality

Covers natural terms a user would say — 'editing code to clean it up', '1-caller helper earns its keep', 'sequence of small refactor commits', 'refactor'. Good coverage of common variations rather than jargon-only; not score 2 which misses common variations.

3 / 3

Distinctiveness Conflict Risk

Clear niche (per-change refactoring mechanics) with explicit de-conflict routing — 'For the smell catalog use code-audit; for session-long simplification use collapse-pass'. Distinct triggers and low conflict risk match the score-3 anchor.

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

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository
EpicenterHQ/epicenter
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.