CtrlK
BlogDocsLog inGet started
Tessl Logo

gitnexus-refactoring

Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file"

76

Quality

95%

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

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

Excellent, highly actionable content: concrete tool invocations, validation checkpoints with a dry-run feedback loop, and recovery guidance, all delivered with minimal token overhead. The only notable weakness is redundancy between the Example section and the Rename checklist/Tools sections, which could be consolidated to shorten the file.

DimensionReasoningScore

Conciseness

Lean throughout: no concept explanations, no filler — every section is parameterized tool calls, checklists, or a risk table. Every token earns its place.

5 / 5

Actionability

Copy-paste-ready tool calls with concrete arguments (rename with dry_run, impact with direction, detect_changes, a cypher query, and the stale-index recovery command), plus a fully worked end-to-end rename example covering the common case.

5 / 5

Workflow Clarity

Clear sequence with an explicit update ordering rule, a dry-run preview → review → apply → detect_changes → run-tests feedback loop for this batch operation, per-operation checklists, and error recovery for the stale-index case.

5 / 5

Progressive Disclosure

Well-organized single-file skill with no nested references, but the worked Example section substantially duplicates the Rename checklist and Tools section content, and at ~117 lines it exceeds the simple-skill inline comfort zone — minor organization gaps rather than an ideal split.

4 / 5

Total

19

/

20

Passed

Description

91%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 strong description with an explicit 'Use when' clause, natural verbatim trigger phrases, and good synonym coverage. Its main weakness is that it describes the user's tasks rather than the skill's concrete capabilities, and it omits the feature (GitNexus graph analysis) that would most distinguish it from sibling skills.

DimensionReasoningScore

Specificity

Lists five concrete action verbs ("rename, extract, split, move, or restructure") but never states the skill's own capabilities (graph-based impact analysis, automated multi-file edits, verification), a minor coverage gap matching anchor 4 rather than 5.

4 / 5

Completeness

Explicitly answers both: what (rename/extract/split/move/restructure code) and when ("Use when the user wants to..." plus concrete example trigger phrases), matching the anchor 5 example pattern.

5 / 5

Trigger Term Quality

Includes verbatim natural user phrases ("Rename this function", "Refactor this class") with synonym coverage across rename/refactor/restructure/extract/split/move — comprehensive for the domain; nothing common is missing.

5 / 5

Distinctiveness Conflict Risk

The refactoring niche is fairly distinct, but generic triggers like "refactor" and "move" risk minor overlap with general code-editing skills, and the differentiator (GitNexus graph tooling) is absent from the description.

4 / 5

Total

18

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
mindfold-ai/Trellis
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.