CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

svelte-docs

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

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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.

An exemplary lean skill body: executable commands with a real-world quoting example, concrete official doc URLs, an explicit escalation policy for detail level, and clear input-handling rules. No bundle files exist or are needed, and there is no padding or redundant explanation.

DimensionReasoningScore

Conciseness

Every line is load-bearing: executable commands, a non-obvious quoting gotcha ("Use single quotes for section names that contain `$`"), and a compact small/medium/full escalation policy; nothing explains concepts Claude already knows.

5 / 5

Actionability

Copy-paste-ready commands ("mise x -- npx @sveltejs/mcp list-sections", "get-documentation '$state,$derived,$effect'") plus concrete fallback URLs cover the common cases, matching the fully-executable anchor.

5 / 5

Workflow Clarity

A simple, single-purpose lookup skill with an unambiguous primary path (docs CLI) and a clearly signaled fallback (web index, escalating detail only when the short version cannot answer); it is read-only so the destructive/batch validation cap does not apply, and the simple-skill exception holds.

5 / 5

Progressive Disclosure

The body is under 50 lines, self-contained, and needs no external references; the flow (CLI, then web fallback, then input-handling rules) is well-organized with no nested references, which the rubric's short-skill guideline scores at 5.

5 / 5

Total

20

/

20

Passed

Description

65%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 concise, correctly third-person description with strong distinctiveness from naming the three Svelte products, but it omits any "when to use" trigger guidance and lists only a single generic action. Adding an explicit use-when clause and one or two more concrete actions would raise it substantially.

Suggestions

Add an explicit trigger clause, e.g., "Use when the user asks about Svelte, SvelteKit, or the Svelte CLI, or mentions runes like $state or $effect."

Enumerate one or two more concrete actions, e.g., "list and read specific documentation sections via the docs CLI, or fetch the full docs when the summary is not enough."

Include common user phrasings such as "Svelte 5", "runes", or ".svelte files" to broaden natural trigger-term coverage.

DimensionReasoningScore

Specificity

"Look up official Svelte, SvelteKit, and Svelte CLI documentation" names the domain and one concrete action (lookup), matching the 1-2-concrete-actions anchor; it does not list several specific actions (e.g., search sections, read full pages, fetch API references) that would justify a 4.

3 / 5

Completeness

The "what" is clear (look up official documentation) but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines; a 4 requires both what and when.

3 / 5

Trigger Term Quality

Natural terms "Svelte", "SvelteKit", and "Svelte CLI" are exactly what a user would say, with good keyword coverage; common variations like "docs", "Svelte 5", "runes", or "$state" are missing, so it is not a 5.

4 / 5

Distinctiveness Conflict Risk

Naming the three specific Svelte products establishes a clear niche with distinct triggers and minimal conflict risk against other documentation-lookup skills; it is not generic at any neighboring anchor.

5 / 5

Total

15

/

20

Passed

Validation

100%

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

Reviewed

Table of Contents

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.