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.

1.06x

Quality

77%

Does it follow best practices?

Impact

92%

1.06x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/svelte-migrate/SKILL.md

Quality

Content

65%Weight 40%Scale 1-3

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 with complete before/after examples and a concrete validation command. Its main weaknesses are length/redundancy, a missing error-recovery loop in the workflow, and a monolithic structure that could benefit from splitting rarer patterns into a separate file.

Suggestions

Add a feedback loop to the Workflow, e.g. after 'Run pnpm check': 'If it fails, review the errors, fix the affected pattern, and re-run until it passes.'

Tighten the lifecycle section (pattern 10) and pattern 12 to a single canonical form to reduce redundancy and overall length.

Move the less-common patterns (e.g. slots, bindable props, dynamic components) into a references/ file and link to it from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body avoids teaching known concepts and stays on-point with before/after patterns, but at ~490 lines it carries redundancy (the verbose onMount/$effect lifecycle section, pattern 12's two equivalent output forms) that could be tightened to earn a 3.	2 / 3
Actionability	Every migration pattern provides complete, executable Svelte before/after code blocks, and the workflow ends with a concrete 'Run pnpm check' command, making the guidance copy-paste ready.	3 / 3
Workflow Clarity	The Workflow lists a clear ordered sequence with an explicit validation step ('Run pnpm check'), but it lacks an error-recovery feedback loop (what to do when the check fails) for a code-rewriting operation, which the level-3 anchor requires.	2 / 3
Progressive Disclosure	The ~490-line body is organized into clearly headed sections, but it is a monolithic single file with no external references; rarer patterns (slots, bindable, dynamic components) are inline content that could be split into a one-level-deep reference file.	2 / 3
	Total	9 / 12 Passed

Description

90%Weight 40%Scale 1-3

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 concise, well-targeted description that explicitly covers both what the skill does and when to use it, using natural trigger terms. Its only weakness is listing one migration action rather than several concrete capabilities.

Dimension	Reasoning	Score
Specificity	It names the domain and a concrete action ('Migrate a Svelte 4 component to Svelte 5 runes syntax'), but lists a single migration action rather than multiple distinct concrete actions, so it sits below the 'multiple specific actions' anchor.	2 / 3
Completeness	It clearly states what the skill does ('Migrate a Svelte 4 component to Svelte 5 runes syntax') and gives an explicit 'Use when...' clause for when to invoke it, satisfying both halves of the completeness anchor.	3 / 3
Trigger Term Quality	'Use when asked to migrate, convert, or upgrade a .svelte file to Svelte 5' supplies several natural verbs a user would actually say, plus '.svelte file' and 'Svelte 5', giving good keyword coverage.	3 / 3
Distinctiveness Conflict Risk	The Svelte 4-to-5 runes niche with '.svelte file'/'Svelte 5' triggers is narrow and unlikely to collide with unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

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
Commit: 0c4b698

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

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.