CtrlK
BlogDocsLog inGet started
Tessl Logo

svelte-core-bestpractices

Guidance on writing fast, robust, modern Svelte code. Load this skill whenever in a Svelte project and asked to write/edit or analyze a Svelte component or module. Covers reactivity, event handling, styling, integration with libraries and more.

71

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

86%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, actionable Svelte best-practices reference with executable do/don't examples and a clean one-level-deep reference structure. The only soft spot is that, as a topic reference rather than a sequenced workflow, it has no explicit multi-step process or validation checkpoints.

DimensionReasoningScore

Conciseness

Lean, high-signal Svelte-specific guidance with efficient do/don't code blocks; the prose covers genuinely Svelte-specific semantics rather than concepts Claude already knows, with only minor trimmable explanation, so it sits just below the leanest 5 anchor.

4 / 5

Actionability

Provides concrete, executable code across the common cases ($derived, $props, events, snippets, each blocks, styling) with do/don't patterns, fully matching the copy-paste-ready top anchor.

5 / 5

Workflow Clarity

This is a best-practices reference rather than a multi-step workflow, with no destructive or batch operations, so the cap-at-3 rule does not apply; per-section guidance is unambiguous (do this / avoid that), but there is no overall sequenced workflow, holding it at 4.

4 / 5

Progressive Disclosure

A clear overview body with well-signaled, one-level-deep references/*.md links, all of which resolve to real bundle files, with content appropriately split between the overview and reference files.

5 / 5

Total

18

/

20

Passed

Description

87%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 strong, well-targeted description that explicitly states both what it covers and when to load it, scoped tightly to Svelte. The main weakness is mild buzzword fluff ("fast, robust, modern") and a vague "and more" trailing the coverage list.

DimensionReasoningScore

Specificity

Names the Svelte domain plus several specific covered areas ("reactivity, event handling, styling, integration with libraries") and concrete actions ("write/edit or analyze a Svelte component or module"), but "fast, robust, modern" is mild buzzword fluff and "and more" leaves a minor gap, so it stops short of 5.

4 / 5

Completeness

Explicitly answers both what ("Guidance on writing... Svelte code" plus the covered-topics list) and when with a concrete trigger phrase ("Load this skill whenever in a Svelte project and asked to write/edit or analyze a Svelte component or module"), matching the top anchor.

5 / 5

Trigger Term Quality

Includes natural terms a user would actually say ("Svelte project", "Svelte component", "write", "edit", "analyze") with good coverage, but misses the .svelte file extension and common synonyms, keeping it below 5.

4 / 5

Distinctiveness Conflict Risk

Targets a clear Svelte-specific niche with distinct triggers ("whenever in a Svelte project") and minimal overlap risk with other skills.

5 / 5

Total

18

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
chattocorp/chatto
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.