CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

refactor

Guides a refactor, cleanup, or restructure with the right decomposition. Use when the user asks to refactor, simplify, extract, or modernize code.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./packages/shared-skills/skills/refactor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

62%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 well-sequenced, highly actionable refactoring workflow with strong validation and recovery loops, undermined by significant verbosity and a monolithic single-file structure that inlines 600+ lines where a lean overview plus separate references would serve better.

Suggestions

Cut the 'What This Command Does' and 'Tool Usage Philosophy' sections — they restate what the phase instructions already specify and pad the token budget without adding guidance Claude doesn't already have.

Move the entire Team Mode Protocol addendum (~140 lines) into a separate reference file (e.g., references/team-mode.md) loaded only when team_* tools are present, keeping SKILL.md as a lean overview.

Trim the per-phase todo-reminder boilerplate (repeated 'Mark phase-N as in_progress/completed' callouts) into a single upfront convention statement, saving dozens of lines without losing sequencing clarity.

DimensionReasoningScore

Conciseness

The ~610-line body includes several padded sections: the marketing-style "What This Command Does" list ("Understands your intent", "Maps the codebase"), a "Tool Usage Philosophy" section restating tool basics Claude already knows, and a 140-line team-mode addendum of dense protocol. This matches anchor 2 (noticeably verbose, several unnecessary or padded sections) rather than anchor 3, where padding would be incidental.

2 / 5

Actionability

Guidance is mostly executable: exact tool calls (lsp_goto_definition, lsp_find_references, lsp_rename, sg --pattern ... --rewrite ...), a complete JSON team spec, and concrete prompt templates. Minor gaps keep it below anchor 5: pervasive [TARGET]/[agent_1_id] placeholders and the pseudocode `for (file of changedFiles)` loop in Phase 6.5.

4 / 5

Workflow Clarity

Phases 0-6 are explicitly sequenced with per-phase todo tracking, mandatory post-step verification (diagnostics, tests, type check), a failure-recovery protocol (STOP/REVERT/DIAGNOSE/OPTIONS), abort conditions, and an intent-gate checklist. This matches the top anchor: clear sequence, explicit validation, feedback loops, and checklists.

5 / 5

Progressive Disclosure

The body is well-sectioned with clear phase headers, but it is a single 610-line monolith with no bundle files: the team-mode protocol and detailed phase templates clearly belong in separate reference files. This fits anchor 3 (good internal structure but content that should be separate is inline) rather than anchor 2, since structure is thorough, not minimal.

3 / 5

Total

14

/

20

Passed

Description

70%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 well-formed description with an explicit 'Use when...' clause and natural trigger verbs covering the refactoring domain. The main weakness is a thin, near-synonymous action list on the what-side plus mild fluff in "with the right decomposition".

DimensionReasoningScore

Specificity

"Guides a refactor, cleanup, or restructure with the right decomposition" lists near-synonymous verbs rather than several distinct concrete actions, and "with the right decomposition" is vague filler. It names the domain plus 1-2 actions, matching anchor 3; it does not reach anchor 4 because the verbs are not separate capabilities (no mention of codebase analysis, dependency mapping, or test verification).

3 / 5

Completeness

Both parts are present: a what ("Guides a refactor, cleanup, or restructure...") and an explicit "Use when..." trigger clause with multiple concrete verbs. Not anchor 5 because the what-side is thin — it does not state what the guidance actually involves (planning, verification, safety).

4 / 5

Trigger Term Quality

"Use when the user asks to refactor, simplify, extract, or modernize code" contains natural phrases users would actually say, and "cleanup" appears in the what-clause. It falls short of anchor 5 because synonyms like "restructure", "tidy up", or "clean up code" are absent from the trigger list.

4 / 5

Distinctiveness Conflict Risk

Refactoring is a clear niche with mostly distinct triggers, but "simplify" and "extract" are broad verbs that could plausibly fire for non-refactoring requests (e.g., data extraction), creating minor overlap risk with closely related skills.

4 / 5

Total

15

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (756 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

13

/

16

Passed

Repository

code-yeongyu/oh-my-openagent

Path

packages/shared-skills/skills/refactor/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.