CtrlK
BlogDocsLog inGet started
Tessl Logo

tdd-workflows-tdd-refactor

Use when working with tdd workflows tdd refactor

40

Quality

38%

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

Quality

Content

48%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 content provides a well-sequenced refactoring workflow with validation and recovery, plus a concrete code example, but is padded with reference catalogs of concepts Claude already knows and uses no progressive disclosure to external files. Tightening and offloading catalogs would materially improve it.

Suggestions

Move the code-smell, design-pattern, SOLID, and refactoring-technique catalogs into a separate REFERENCE.md and link to it, leaving only the workflow and quick-start inline.

Trim one-line explanations of well-known concepts (e.g. 'Single Responsibility: One reason to change') since Claude already knows SOLID.

Replace abstract heuristic bullets with concrete, executable steps or commands where possible to lift actionability.

DimensionReasoningScore

Conciseness

The body extensively catalogs concepts Claude already knows (every SOLID principle with definitions, all GoF pattern categories, a full code-smell list, every refactoring technique), which is noticeable padding; not a 3 because multiple sections are unnecessary explanations rather than a few trimmable lines.

2 / 5

Actionability

There is a concrete, complete TypeScript before/after example and a specific Task-tool invocation with subagent_type, but the bulk of guidance is abstract heuristic bullet lists ('Duplicated code → Extract methods/classes'); not a 4 because key steps rely on vague directives rather than executable commands.

3 / 5

Workflow Clarity

A clear 10-phase Core Process is sequenced with explicit validation checkpoints ('Run tests after each modification', 'Run full test suite after each change') and a Recovery Protocol feedback loop; not a 5 because some checkpoints are implicit and ordering between phases could be tighter.

4 / 5

Progressive Disclosure

The file has section structure but inlines large reference-style catalogs (code smells, design patterns, SOLID, refactoring techniques) that belong in separate files, and no bundle/reference files exist; not a 4 because nothing is split out and navigation is purely one long document.

3 / 5

Total

12

/

20

Passed

Description

28%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 essentially a bare 'when' clause with no statement of capabilities, leaving both what and how underspecified. Its trigger phrasing is repetitive and jargon-laden rather than natural.

Suggestions

Add a concrete 'what' clause listing specific actions, e.g. 'Refactor code under a green-test baseline using the tdd-orchestrator agent.'

Rewrite the trigger with natural user phrasing and synonyms, e.g. 'Use when refactoring code safely with tests, doing TDD refactors, or improving code quality without breaking tests.'

Avoid the repetitive 'tdd workflows tdd refactor' construction; state the niche once and concretely.

DimensionReasoningScore

Specificity

The description names the domain ('tdd workflows tdd refactor') but states no concrete actions or verbs, matching 'Names the domain but actions are minimal or generic'; it is not a 1 because the domain itself is named clearly.

2 / 5

Completeness

Only a 'when' clause is present ('Use when working with tdd workflows tdd refactor') with no 'what' describing what the skill does, matching the anchor 'only when is present without what'.

2 / 5

Trigger Term Quality

'tdd workflows tdd refactor' offers only a couple of generic/jargon keywords and is awkwardly repetitive, missing natural phrases a user would say; not a 3 because synonyms and natural variations are absent.

2 / 5

Distinctiveness Conflict Risk

'tdd refactor' is a somewhat specific niche but the generic, broken phrasing risks overlap with general refactoring or TDD skills; not a 4 because the trigger is not sharply distinguished.

3 / 5

Total

9

/

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
rmyndharis/antigravity-skills
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.