svelte-code-writer

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.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

93%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 is a tight, fully executable reference with a clear workflow and an explicit validation step, well-organized for a simple single-purpose skill. The only gap is the absence of an explicit error-recovery loop after the validation step.

Suggestions

Add a short feedback loop after the 'Always validate' step, e.g., 'If svelte-autofixer reports issues, fix them and re-run before finalizing' to push workflow clarity to 5.

Consider listing a couple of common section names from list-sections (e.g., $state, $derived, $effect) inline so users know what documentation is retrievable without running list-sections first.

Dimension	Reasoning	Score
Conciseness	The body is lean: brief intros, exact command signatures, minimal examples, and one genuinely useful gotcha (escaping '$'). It assumes Claude's competence with no padded explanations of what Svelte is, matching anchor 5.	5 / 5
Actionability	Fully executable npx commands with concrete copy-paste-ready examples covering inline code, file paths, and version targeting, matching the anchor 5 example of fully executable guidance covering common cases.	5 / 5
Workflow Clarity	The 3-step workflow has an explicit validation checkpoint ('Always validate - Run svelte-autofixer before finalizing'), placing it above anchor 3. It falls short of 5 because no error-recovery loop specifies what to do when the autofixer flags issues.	4 / 5
Progressive Disclosure	Under 50 lines, single-purpose, and well-organized with clear section headers (CLI Tools subcommands + Workflow) and no nested references; per the simple-skills note this warrants a 5 without external file references.	5 / 5
	Total	19 / 20 Passed

Description

82%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 clearly and explicitly states both what the skill does and when to use it, with strong natural trigger terms and Svelte-specific distinctiveness. Its only weakness is that the action list ('documentation lookup and code analysis') is somewhat high-level rather than enumerating multiple concrete capabilities.

Suggestions

Expand the 'what' clause with more concrete actions (e.g., 'fetch Svelte/SvelteKit docs, detect rune and reactivity issues, suggest fixes') to lift specificity toward a 4 or 5.

Consider adding common natural synonyms like 'SvelteKit', 'runes', or 'reactivity' to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Svelte 5 documentation lookup and code analysis') with two concrete action categories, but 'code analysis' is generic and coverage is not comprehensive. Fits anchor 3 better than 4 because it lacks a fuller list of specific actions.	3 / 5
Completeness	Explicitly answers both what ('CLI tools for Svelte 5 documentation lookup and code analysis') and when ('MUST be used whenever creating, editing or analyzing any Svelte component') with concrete trigger phrases, matching anchor 5.	5 / 5
Trigger Term Quality	Strong natural triggers ('creating, editing or analyzing any Svelte component') plus file extensions (.svelte, .svelte.ts/.svelte.js) that users would naturally say. Solidly above anchor 3 but short of 5 because terms like 'SvelteKit', 'runes', or 'reactivity' are absent.	4 / 5
Distinctiveness Conflict Risk	Svelte-specific niche with concrete file extensions and explicit trigger guidance, giving it a clear niche with minimal conflict risk against other skills, matching anchor 5.	5 / 5
	Total	17 / 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: chattocorp/chatto
Path: .agents/skills/svelte-code-writer/SKILL.md
Commit: 967a9a1

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