CtrlK
BlogDocsLog inGet started
Tessl Logo

refactor-safely

Plan and execute safe refactoring using dependency analysis

60

Quality

70%

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 ./skills/refactor-safely/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a tight, highly actionable workflow that names exact tools and arguments while respecting token budget. Workflow clarity is strong with safety checks, though the apply/verify loop could be made more explicit as a hard validation checkpoint.

DimensionReasoningScore

Conciseness

Lean and efficient throughout; it never explains concepts Claude already knows and every line gives concrete tool invocations or a tight directive, with each token earning its place.

5 / 5

Actionability

Fully executable guidance: each step names the exact tool and mode/argument (e.g., `refactor_tool` with mode="rename", `get_minimal_context_tool(task=...)`), making the instructions copy-paste ready for the common cases.

5 / 5

Workflow Clarity

Steps are clearly numbered and sequenced with safety checks, but validation is preview-oriented rather than a hard validate-then-apply feedback loop; minor checkpoints (e.g., 'verify the refactoring impact') are present but somewhat implicit.

4 / 5

Progressive Disclosure

A short, single-purpose skill under 50 lines with no external references needed; content is organized into clear sections (Steps, Safety Checks, Token Efficiency Rules), which satisfies the simple-skill exception for a top score.

5 / 5

Total

19

/

20

Passed

Description

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

The description is concise and third-person with a clear domain, but it lacks explicit "when to use" trigger guidance and offers limited trigger-term coverage, capping its score. It is reasonably distinct from sibling skills.

Suggestions

Add an explicit 'Use when...' clause naming trigger situations (e.g., 'Use when planning refactors, renaming symbols, or removing dead code').

Broaden trigger terms with natural synonyms users say, such as 'rename', 'restructure', 'dead code', 'refactor safely'.

List 2-3 concrete actions (suggest, detect dead code, preview renames) to lift specificity from one technique to comprehensive coverage.

DimensionReasoningScore

Specificity

Names the domain ("safe refactoring") and one concrete action ("dependency analysis"), but lists only one technique rather than comprehensive coverage of concrete actions.

3 / 5

Completeness

States clearly what the skill does ("Plan and execute safe refactoring using dependency analysis") but omits any explicit "Use when..." trigger guidance, capping completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Contains "refactoring" as a natural term but lacks common variations users would say (e.g., "rename", "restructure", "dead code") and synonyms, leaving mostly one generic keyword.

2 / 5

Distinctiveness Conflict Risk

The pairing of "safe refactoring" with "dependency analysis" carves a clear niche distinct from general coding skills, with only minor overlap risk against related refactor/code-analysis skills.

4 / 5

Total

12

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
tirth8205/code-review-graph
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.