CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

svelte-migrate

Migrate a Svelte 4 component to Svelte 5 runes syntax. Use when asked to migrate, convert, or upgrade a .svelte file to Svelte 5.

89

1.06x
Quality

89%

Does it follow best practices?

Impact

92%

1.06x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

A strong, highly actionable reference made almost entirely of concrete before/after code pairs with a clear workflow ending in a validation step. Minor improvements are possible: consolidate the duplicated onMount guidance, add an error-recovery loop after pnpm check, and consider splitting rarely needed patterns into a reference file.

DimensionReasoningScore

Conciseness

Nearly all content is non-obvious before/after mapping code rather than explanations of concepts Claude already knows, but minor trimming is possible: pattern 12 re-presents unchanged code as the "After" state, and the onMount/onDestroy guidance is duplicated between section 10 and the Important Notes section.

4 / 5

Actionability

Every one of the 13 migration patterns is given as a complete, executable before/after code pair covering the common Svelte 4 to 5 cases, plus a concrete verification command (pnpm check), matching the fully-executable copy-paste-ready anchor.

5 / 5

Workflow Clarity

The 6-step workflow is clearly sequenced and ends with an explicit validation checkpoint ("Run pnpm check to verify no type errors"), but there is no fix-and-revalidate feedback loop, so it falls one step short of the explicit-feedback-loops anchor.

4 / 5

Progressive Disclosure

The body is well organized into 13 clearly headed pattern sections plus workflow and notes, making it easy to navigate, but roughly 490 lines are kept entirely inline with no split-out reference files, so it sits at the good-structure-with-minor-gaps anchor rather than a clear overview with one-level-deep references.

4 / 5

Total

17

/

20

Passed

Description

90%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 well-crafted description with explicit what and when clauses, strong natural trigger synonyms plus the .svelte extension, and a clearly distinct niche. Its only limitation is that the capability statement names a single action rather than enumerating the specific transformations the skill performs.

DimensionReasoningScore

Specificity

"Migrate a Svelte 4 component to Svelte 5 runes syntax" names the domain and one concrete action, but does not enumerate several specific transformations (props, state, events, slots), matching the 1-2-concrete-actions anchor rather than the several-actions anchor.

3 / 5

Completeness

It explicitly answers both what ("Migrate a Svelte 4 component to Svelte 5 runes syntax") and when ("Use when asked to migrate, convert, or upgrade a .svelte file to Svelte 5") with concrete trigger phrases, exactly matching the top anchor.

5 / 5

Trigger Term Quality

"Use when asked to migrate, convert, or upgrade a .svelte file to Svelte 5" provides comprehensive synonym coverage (migrate/convert/upgrade) plus the .svelte file extension, matching the comprehensive-synonyms-and-extensions anchor; only niche variants like "port" or "modernize" are absent.

5 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (Svelte version migration) with distinct triggers (Svelte 5, runes, .svelte) and minimal overlap with other skills, matching the clear-niche anchor.

5 / 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

temporalio/ui

Path

.claude/skills/svelte-migrate/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.