Use the Svelte CLI to check any Svelte component or module that you create, edit, or analyze.
70
86%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Follow svelte-core-bestpractices for Svelte patterns. Use svelte-docs for documentation.
Run the autofixer when reviewing or debugging Svelte code, and before returning
changes to a .svelte, .svelte.ts, or .svelte.js file:
mise x -- npx @sveltejs/mcp svelte-autofixer ./path/to/Component.svelteUse --svelte-version 4 only for Svelte 4 code. Use --async when checking
async Svelte mode. Fix the cause of reported warnings.
Prefer a file path to inline source. If inline source contains $ runes, use
shell single quotes. Do not add backslashes to runes inside single quotes.
5cbd584
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.