CLI tools for Svelte 5 documentation lookup and code analysis. MUST be used whenever creating, editing or analyzing any Svelte component (.svelte) or Svelte module (.svelte.ts/.svelte.js). If possible, this skill should be executed within the svelte-file-editor agent for optimal results.
76
95%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
You have access to @sveltejs/mcp CLI for Svelte-specific assistance. Use these commands via npx:
npx @sveltejs/mcp list-sectionsLists all available Svelte 5 and SvelteKit documentation sections with titles and paths.
npx @sveltejs/mcp get-documentation "<section1>,<section2>,..."Retrieves full documentation for specified sections. Use after list-sections to fetch relevant docs.
Example:
npx @sveltejs/mcp get-documentation "$state,$derived,$effect"npx @sveltejs/mcp svelte-autofixer "<code_or_path>" [options]Analyzes Svelte code and suggests fixes for common issues.
Options:
--async - Enable async Svelte mode (default: false)--svelte-version - Target version: 4 or 5 (default: 5)Examples:
# Analyze inline code (escape $ as \$)
npx @sveltejs/mcp svelte-autofixer '<script>let count = \$state(0);</script>'
# Analyze a file
npx @sveltejs/mcp svelte-autofixer ./src/lib/Component.svelte
# Target Svelte 4
npx @sveltejs/mcp svelte-autofixer ./Component.svelte --svelte-version 4Important: When passing code with runes ($state, $derived, etc.) via the terminal, escape the $ character as \$ to prevent shell variable substitution.
list-sections then get-documentation for relevant topicssvelte-autofixer on the code to detect issuessvelte-autofixer before finalizing any Svelte component65f65c3
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.