CtrlK
BlogDocsLog inGet started
Tessl Logo

od-code-migration

Default reference pipeline for the code-migration taskKind — code-import → design-extract → token-map → rewrite-plan → patch-edit ↔ build-test devloop → diff-review → handoff.

58

Quality

68%

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 ./plugins/_official/scenarios/od-code-migration/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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, well-structured declarative pipeline definition with a clear stage sequence and an explicit build/test convergence feedback loop. It is actionable and appropriately scoped for a sub-50-line single-purpose scenario skill.

DimensionReasoningScore

Conciseness

Lean and assumes framework competence without re-explaining basics; only minor flourishes ('convergence engine', the spec section citations) could be trimmed, keeping it just shy of fully lean.

4 / 5

Actionability

Provides a concrete JSONC pipeline definition and typed user inputs (repoPath, targetStack, testCommand) that are directly usable, with only minor gaps since no shell commands are shown.

4 / 5

Workflow Clarity

The pipeline is a clearly sequenced multi-step flow with an explicit verify feedback loop and convergence condition 'until: (build.passing && tests.passing) || iterations>=8', supplying the validation checkpoint and error-recovery loop the top anchor requires.

5 / 5

Progressive Disclosure

Under 50 lines with no need for external references and well-organized sections (Default pipeline, Required user inputs), meeting the simple-skill exception for a top score on progressive disclosure.

5 / 5

Total

18

/

20

Passed

Description

51%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 clearly conveys a specific code-migration pipeline with concrete named stages, but it relies heavily on framework jargon and omits any explicit 'when to use' trigger guidance. It is distinct within its niche but weak on natural user-facing keywords.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers (e.g., migrating a repo to a new stack or framework).

Introduce common user-facing terms or synonyms alongside the jargon atom names so the description matches how users actually ask.

Briefly gloss the opaque atom identifiers (e.g., 'token-map (map source design tokens)') to lift specificity toward 5.

DimensionReasoningScore

Specificity

Lists eight named concrete pipeline stages (code-import, design-extract, token-map, rewrite-plan, patch-edit, build-test, diff-review, handoff), giving several specific actions, though the terse atom names leave minor clarity gaps.

4 / 5

Completeness

Provides a clear 'what' (the default pipeline and its stages) but no 'Use when...' clause or equivalent trigger guidance, so completeness is capped at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Dominated by framework jargon ('taskKind', 'devloop', atom identifiers); only 'code-migration' is a term a user would naturally say, missing the common natural phrases.

2 / 5

Distinctiveness Conflict Risk

'code-migration taskKind' with its named atoms carves a clear niche with distinct triggers, carrying only minor overlap risk with generic migration skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
nexu-io/open-design
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.