CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

migration-migrate-module

Use when a complete module needs migration to the target architecture - runs 6 phases with approval gates.

Quality

75%

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 ./packs/react/skills/migration-migrate-module/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 an exemplary lean orchestration skill: a crisp goal, well-sequenced phases with per-phase validation and approval gates, and appropriate external references. Its main weakness is actionability — validation and the `@migrator` invocation are named but not executable, and failure handling is unspecified.

Suggestions

Add the concrete validation commands (e.g., `npx tsc --noEmit`, `npm test`) so "Validate build/tsc/tests" is executable rather than named.

Show how `@migrator` is invoked or what it returns, so the delegation step is actionable rather than assumed.

Add a brief error-recovery loop (e.g., "If validation fails, fix and re-validate before requesting approval for the next phase").

DimensionReasoningScore

Conciseness

The ~25-line body is lean with zero padding: a one-line goal statement, terse phase bullets, and a two-line close ("Validate build/tsc/tests after each phase. Ask for approval before each phase."). It assumes Claude's competence and explains nothing it already knows.

5 / 5

Actionability

Gives concrete artifacts ("`.types.ts` + `.contracts.ts`", "`src/modules/[name]/`") and specific tech targets (React Query, Zustand, useCallback/useMemo), but no executable commands: "Validate build/tsc/tests" names no commands (e.g., `npx tsc --noEmit`) and how to invoke `@migrator` is unstated. Not 4 because concrete code or commands are absent.

3 / 5

Workflow Clarity

Clear 7-phase sequence with validation checkpoints after each phase and approval gates before each phase; validation steps are stated, so the destructive/batch cap at 3 does not apply. Not 5 because there is no error-recovery feedback loop (what to do when build/tsc/tests fail) for a workflow that moves files and removes Redux.

4 / 5

Progressive Disclosure

Under 50 lines, no bundle files, well-organized sections, and a single one-level external reference (`docs/ARCHITECTURE.md`) plus delegation to `@migrator`. Per the rubric's short-skill guidance, this merits a 5 with just well-organized sections.

5 / 5

Total

17

/

20

Passed

Description

62%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 has an explicit, well-formed "Use when..." trigger and covers both what and when, but the "what" is underspecified and the phase count conflicts with the body (6 vs. 7 phases). Trigger vocabulary lacks common synonyms like "refactor" or "port" that users would naturally say.

Suggestions

List 2-3 concrete migration capabilities in the description (e.g., "migrates services, types, state (Redux to Zustand/React Query), and class components") instead of the abstract "runs 6 phases".

Add natural trigger synonyms such as "migrate", "refactor", or "port" a module to broaden keyword coverage.

Fix the phase-count inconsistency: the body defines Phases 0-6 (seven phases), while the description says "6 phases".

DimensionReasoningScore

Specificity

Names the domain ("module needs migration to the target architecture") and 1-2 actions ("runs 6 phases with approval gates") but lists no concrete migration capabilities, and "6 phases" contradicts the 7 phases (0-6) in the body. Not 4 because it does not enumerate several specific actions.

3 / 5

Completeness

Explicitly answers both: what ("runs 6 phases with approval gates") and when ("Use when a complete module needs migration to the target architecture"). Not 5 because the "what" is thin and lacks concrete capability phrases; not 3 because the "when" is explicit, not merely implied.

4 / 5

Trigger Term Quality

Includes relevant keywords ("module", "migration", "target architecture") but misses natural variations users would say such as "migrate", "refactor", "port", or "rewrite". Not 4 because the gap is more than "a few" missing terms.

3 / 5

Distinctiveness Conflict Risk

"Complete module needs migration to the target architecture" carves a distinct whole-module-migration niche with "approval gates" as a distinguishing detail. Not 5 due to residual overlap with general refactoring or migration skills; not 3 since the scope is clearly narrower than generic refactoring.

4 / 5

Total

14

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

fernandezbaptiste/specialist-agent

Path

packs/react/skills/migration-migrate-module/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.