svelte-docs

Look up official Svelte, SvelteKit, and Svelte CLI documentation.

Quality

78%

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

Fix and improve this skill with Tessl

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

Quality

Content

100%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 an exemplary compact lookup skill: lean, fully executable, with explicit escalation and scope-handling guidance and clean organization that needs no bundle files.

Dimension	Reasoning	Score
Conciseness	The ~25-line body is lean and assumes Claude's competence (no explanation of what Svelte, mise, npx, or llms.txt are); every line — commands, the `$`-quoting tip, URLs, and escalation rule — earns its place.	5 / 5
Actionability	Copy-paste-ready commands (`mise x -- npx @sveltejs/mcp list-sections`, `get-documentation '$state,$derived,$effect'`) plus concrete index URLs cover the common lookup cases, with a specific quoting tip for `$`-named sections.	5 / 5
Workflow Clarity	As a simple single-purpose read-only lookup skill under 50 lines with clear routing (CLI list→get, web index fallback) and an explicit escalation checkpoint ('Read full documentation only if the short version cannot answer'), the simple-skill exception justifies a 5.	5 / 5
Progressive Disclosure	Under 50 lines with no need for external references (docs are fetched live via CLI/web, not bundled) and well-organized sections under a single heading, meeting the anchor for a compact skill that needs no file splitting.	5 / 5
	Total	20 / 20 Passed

Description

56%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 states what the skill does and names the Svelte ecosystem products well, but it lacks any explicit 'Use when...' trigger guidance and relies on a single generic verb, which limits specificity and completeness.

Suggestions

Add a 'Use when...' clause with concrete triggers, e.g. 'Use when the user asks about Svelte, SvelteKit, or Svelte CLI APIs, runes, or config options.'

Replace or augment the single generic verb 'Look up' with more concrete actions such as 'search, read, and reference official Svelte documentation'.

Include common synonyms users say ('docs', 'Svelte docs', 'SvelteKit docs') to strengthen trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Look up ... documentation" names the domain (Svelte, SvelteKit, Svelte CLI) but offers only a single generic action, matching the anchor 'Names the domain but actions are minimal or generic' rather than the two-action anchor 3.	2 / 5
Completeness	The "what" is clear (look up official Svelte docs) but there is no "Use when..." trigger clause and the "when" is not even weakly implied, so per the missing-trigger guideline completeness caps at 3.	3 / 5
Trigger Term Quality	"Svelte, SvelteKit, and Svelte CLI documentation" gives good coverage of the natural product names users say, though common synonyms like "docs" and action variants ("search"/"find") are absent.	4 / 5
Distinctiveness Conflict Risk	The three named Svelte products carve a clear niche, but the generic action "look up documentation" leaves minor overlap risk with a hypothetical general docs/web-search skill.	4 / 5
	Total	13 / 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: 5cbd584

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