CtrlK
BlogDocsLog inGet started
Tessl Logo

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

86%

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 highly actionable migration reference built from complete before/after code examples with a clear ordered workflow and validation step. The main gaps are a missing explicit error-recovery loop in the workflow and minor prose redundancy around onMount handling.

Suggestions

Add an explicit feedback loop to the Workflow section (e.g., 'If pnpm check reports errors, fix them and re-run until clean') to reach the top workflow_clarity anchor.

Consolidate the onMount/onDestroy guidance so it appears once — either in section 10 or in Important Notes — to remove the duplicated explanation and tighten conciseness.

Consider extracting the 13 pattern reference into a separate references file (e.g., PATTERNS.md) and keeping SKILL.md as a quick-start overview with one-level-deep links to improve progressive disclosure for a ~490-line skill.

DimensionReasoningScore

Conciseness

The body is dominated by before/after code with minimal prose and assumes Svelte competence, but the onMount guidance is repeated across section 10 and Important Notes, leaving minor trimmable redundancy.

4 / 5

Actionability

Thirteen before/after patterns provide fully executable, copy-paste-ready code covering the common migration cases, with concrete handler rewrites and import updates.

5 / 5

Workflow Clarity

The Workflow section gives a clear ordered sequence with a validation checkpoint ("Run pnpm check to verify no type errors"), but it lacks an explicit fix-and-re-validate feedback loop, which keeps it just below the top anchor.

4 / 5

Progressive Disclosure

Content is well-organized under numbered pattern headers and a self-contained cheat-sheet structure with easy navigation; no external references are used, but the cohesive single-file form does not clearly require them, so it sits above the mid anchor.

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 tight, third-person description that clearly answers both what and when with strong trigger-term coverage and a distinct niche. Its only limitation is listing a single action rather than multiple concrete capabilities.

DimensionReasoningScore

Specificity

Names the domain and one concrete action ("Migrate a Svelte 4 component to Svelte 5 runes syntax") but does not enumerate multiple distinct actions, matching the anchor for 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

Explicitly states what it does (migrate Svelte 4 component to runes syntax) and when to use it (asked to migrate/convert/upgrade a .svelte file to Svelte 5) with concrete trigger phrases.

5 / 5

Trigger Term Quality

"migrate, convert, or upgrade a .svelte file to Svelte 5" provides synonyms plus the file extension and target version, giving comprehensive natural-term coverage users would actually say.

5 / 5

Distinctiveness Conflict Risk

The Svelte 4→5 runes niche with .svelte/Svelte 5 triggers is highly specific and unlikely to fire for unrelated skills, indicating minimal conflict risk.

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