svelte-expert

Expert Svelte/SvelteKit development assistant for building components, utilities, and applications. Use when creating Svelte components, SvelteKit applications, implementing reactive patterns, handling state management, working with stores, transitions, animations, or any Svelte/SvelteKit development task. Includes comprehensive documentation access, code validation with svelte-autofixer, and playground link generation.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

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

The body has a strong, well-gated validation workflow and good progressive disclosure via real reference files, but it loses conciseness to generic best-practice filler and a documentation-category catalog that restates reference content. Tightening those sections would materially raise the score.

Suggestions

Remove the generic 'Best Practices' items Claude already knows (e.g. 'Follow accessibility guidelines (a11y)', 'Use semantic HTML and ARIA attributes', 'Implement proper error handling') and keep only Svelte-specific guidance.

Trim or drop the 'Documentation Categories' section — it duplicates the structure already in references/documentation-paths.md; a single pointer to that file is enough.

Cut the redundant opening line 'Expert assistant for building production-ready Svelte components and SvelteKit applications.', which restates the frontmatter description without adding new information.

Dimension	Reasoning	Score
Conciseness	Mostly efficient, but the generic 'Best Practices' list ('Follow accessibility guidelines', 'Use semantic HTML and ARIA attributes', 'Implement proper error handling') tells Claude what it already knows, and the 'Documentation Categories' section duplicates structure already in references/documentation-paths.md.	3 / 5
Actionability	Provides named tools (get_documentation, svelte-autofixer, playground-link), a copy-paste Svelte 5 runes component example, and concrete validation/playground steps, with only minor gaps (tool call signatures and broader examples not shown).	4 / 5
Workflow Clarity	The Core Workflow is a clear three-phase sequence, and phase 2 has an explicit feedback loop — 'Call svelte-autofixer ... Fix all issues ... Repeat until no issues remain ... Only return validated code' — with a hard validation gate before output.	5 / 5
Progressive Disclosure	SKILL.md is a lean overview with well-signaled one-level-deep references (documentation-paths.md, component-patterns.md, migration-guide.md — all verified present), and detailed material is appropriately split into those files.	5 / 5
	Total	17 / 20 Passed

Description

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

The description is strong: it clearly states what the skill does and when to use it, with concrete Svelte/SvelteKit-specific trigger phrases and a well-defined niche. The only gap is trigger-term breadth — adding synonyms and the '.svelte' extension would push it to the top anchor.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'building components, utilities, and applications', 'implementing reactive patterns', 'handling state management', 'working with stores', 'code validation with svelte-autofixer', 'playground link generation' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both 'what' (an assistant for building components/utilities/applications with validation and playground generation) and 'when' via a concrete 'Use when creating Svelte components, SvelteKit applications, ...' clause.	5 / 5
Trigger Term Quality	Good natural keyword coverage ('Svelte components', 'SvelteKit applications', 'reactive patterns', 'state management', 'stores', 'transitions', 'animations'), but missing common synonyms and a '.svelte' file-extension trigger that the top anchor expects.	4 / 5
Distinctiveness Conflict Risk	The 'Svelte/SvelteKit' niche and framework-specific triggers (runes, stores, SvelteKit routing) make it clearly distinct from general web-dev skills with minimal conflict risk.	5 / 5
	Total	19 / 20 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: Raudbjorn/claude
Path: svelte-expert/SKILL.md
Commit: bd02b72

Reviewed: 10 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.