svelte-docs

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

Quality

90%

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

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, highly actionable skill body that gives exact URLs, a clear progressive-fetch workflow, and clean argument handling with no token waste. It is essentially exemplary for a documentation-lookup skill.

Dimension	Reasoning	Score
Conciseness	The body is lean: it never explains what Svelte is or how libraries work, assumes Claude's competence, and every section (progressive fetch, package-specific URLs, WebFetch example, arguments) earns its place.	3 / 3
Actionability	It gives exact, copy-paste-ready URLs (llms-small/medium/full and per-package llms.txt endpoints) plus a concrete WebFetch invocation example and explicit argument-to-action mappings.	3 / 3
Workflow Clarity	The progressive fetch strategy is a clearly sequenced workflow (small -> medium -> full) with explicit escalation conditions ('If the answer is unclear...', 'only when necessary') serving as decision checkpoints; no destructive step requires heavier validation.	3 / 3
Progressive Disclosure	At under 50 lines with no bundle files needed (it fetches remote docs), the well-organized sections satisfy the simple-skill allowance for a top progressive-disclosure score.	3 / 3
	Total	12 / 12 Passed

Description

80%

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 concise, well-scoped description with strong trigger terms and an explicit use-when clause, weakened only by second-person phrasing that costs it a specificity point. Rewording to third person would raise it.

Suggestions

Rewrite in third person to avoid the second-person penalty, e.g. 'Looks up Svelte, SvelteKit, and Svelte CLI documentation. Use when the user asks about Svelte APIs, components, routing, or CLI commands.'

Name a few more concrete actions (e.g. 'find API signatures, code examples, and configuration options') to lift specificity beyond the single 'look up' verb.

Dimension	Reasoning	Score
Specificity	The description names the domain (Svelte, SvelteKit, Svelte CLI) and a single action ('look up ... documentation'), which would rate a 2, but it uses second-person voice ('you want to'), which the guidelines penalize by reducing specificity by one point.	1 / 3
Completeness	It states what the skill does ('look up ... documentation') and provides an explicit 'Use this if you want to...' trigger clause, answering both what and when.	3 / 3
Trigger Term Quality	'Svelte, SvelteKit, and Svelte CLI documentation' are exactly the natural terms a user would say when they need this skill, giving good coverage of likely trigger phrasing.	3 / 3
Distinctiveness Conflict Risk	The scoped trio of Svelte, SvelteKit, and Svelte CLI documentation is a clear niche with distinct triggers unlikely to conflict with other skills.	3 / 3
	Total	10 / 12 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: 65f65c3

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.