svelte-docs

Use this if you want to look up Svelte, SvelteKit, and Svelte CLI documentation.

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/svelte-docs/SKILL.md

Quality

Content

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

A tight, well-structured, actionable skill body with an effective progressive-fetch workflow and clean sectioning. Minor gains are available by removing the redundant WebFetch template and adding an explicit answer-completeness check.

Suggestions

Remove or merge the 'Using WebFetch' template block into the Instructions to eliminate redundancy, since the fetch calls are already specified inline.

Add an explicit verification step (e.g., 'If the fetched docs do not answer the question, escalate to the next size') to make the workflow's feedback loop explicit.

Provide one fully concrete WebFetch example with a real topic instead of the '[topic]' placeholder to reach copy-paste-ready actionability.

Dimension	Reasoning	Score
Conciseness	The body is lean, assumes Claude's competence, and avoids explaining concepts Claude already knows; it is not 5 because the 'Using WebFetch' block restates usage with a placeholder template that mildly duplicates the instructions above.	4 / 5
Actionability	Concrete fetch URLs and explicit WebFetch invocations are provided, plus exact argument mappings; it is not 5 because the WebFetch example uses a placeholder '[topic]' rather than a fully copy-paste-ready example.	4 / 5
Workflow Clarity	A clear progressive sequence (small → medium → full) with an explicit escalation condition is present; it is not 5 because there is no explicit verification/feedback loop confirming the retrieved answer is complete.	4 / 5
Progressive Disclosure	This is a simple skill under 50 lines with no bundle files and no need for external references, and its sections (Instructions, Package-Specific, Using WebFetch, Arguments) are well-organized, qualifying for the top anchor under the simple-skill exception.	5 / 5
	Total	17 / 20 Passed

Description

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

A clear, well-triggered description with strong distinctiveness, but it names only a single generic action ("look up") rather than enumerating concrete capabilities. Adding one or two specific actions would lift specificity and completeness.

Suggestions

Replace the generic 'look up' with concrete actions, e.g. 'Look up and extract Svelte, SvelteKit, and Svelte CLI API references, code patterns, and configuration docs'.

Add natural synonyms such as 'Svelte docs' alongside 'Svelte ... documentation' to broaden trigger coverage.

Clarify the 'what' explicitly (e.g., 'retrieves LLM-optimized docs from svelte.dev') so completeness reaches the top anchor.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Svelte, SvelteKit, and Svelte CLI documentation") but the only action is the generic "look up", matching the anchor 'Names the domain but actions are minimal or generic'; it does not reach 3 because no second concrete action is stated.	2 / 5
Completeness	It has both an explicit 'when' ("Use this if you want to look up...") and a clear 'what' (lookup documentation); it is not 5 because the 'what' could be more explicit about concrete actions, and not 3 because an explicit trigger clause is present.	4 / 5
Trigger Term Quality	"Svelte, SvelteKit, and Svelte CLI documentation" are natural terms users would actually say, giving good keyword coverage; it falls short of 5 because natural variants such as "Svelte docs" or informal synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	The scope is tightly scoped to Svelte-family documentation lookup, a clear niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	15 / 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-docs/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.