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.

72

Quality

88%

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

87%

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 Svelte 5 best-practices skill with executable do/don't examples and well-structured one-level-deep references. Its only gap is the absence of any multi-step workflow with validation checkpoints, which is partly inherent to its reference-skill nature.

Suggestions

For the few process-like sections (e.g. Async Svelte), add an explicit prerequisite check (verify `experimental.async` is enabled in svelte.config.js before using await expressions) to strengthen workflow clarity.

Consider a short 'Validation' note for cases where misapplying a pattern silently breaks reactivity (e.g. confirming a derived re-evaluates after a change), to introduce a lightweight feedback loop.

DimensionReasoningScore

Conciseness

The body is lean: it assumes Claude knows Svelte, uses tight do/don't code pairs, and reserves prose for genuine trade-offs (e.g. the $state proxy overhead note) rather than restating basics. Not a 2 because there is no padding or unnecessary explanation of known concepts.

3 / 3

Actionability

Sections give executable, copy-paste-ready examples with explicit do/don't contrast (e.g. `$derived` vs `$effect`, keyed each blocks, `style:--columns`) plus concrete replacement mappings in "Avoid legacy features". Not a 2 because the guidance is concrete and complete rather than pseudocode or abstract direction.

3 / 3

Workflow Clarity

This is a best-practices reference rather than a multi-step process, so there is no sequenced workflow with validation checkpoints; topics are organized but lack the validate->fix->retry feedback loops the 3 anchor expects. Not a 1 because the content is clearly organized by topic and contains conditional guidance (e.g. the Async Svelte version/option prerequisite), but it does not qualify as a 3 workflow.

2 / 3

Progressive Disclosure

SKILL.md acts as an overview with nine inline, one-level-deep reference links (e.g. [snippet.md](references/snippet.md), [@attach.md](references/@attach.md)), all of which exist as real bundle files, with detail appropriately split out. Not a 2 because references are clearly signaled, real, and only one level deep rather than nested.

3 / 3

Total

11

/

12

Passed

Description

90%

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 that answers both what and when with natural Svelte-specific language. The only weakness is mild specificity fluff ("fast, robust, modern") and topic-list framing rather than enumerated concrete actions.

Suggestions

Replace the fluffy "fast, robust, modern" framing with one or two more concrete capabilities (e.g. "Optimize reactivity, handle events, scope styles, and integrate third-party libraries in Svelte 5 runes code").

List the concrete actions the skill performs rather than only the topic areas it covers, to push specificity toward the 3 anchor.

DimensionReasoningScore

Specificity

Names the Svelte domain and lists several concrete areas ("reactivity, event handling, styling, integration with libraries"), but these are topic categories rather than the multiple specific concrete actions (e.g. "extract text, fill forms, merge") that anchor a 3, and "fast, robust, modern" is mildly fluffy. It is not a 1 because the domain and several sub-areas are explicit.

2 / 3

Completeness

It explicitly answers what ("Guidance on writing fast, robust, modern Svelte code... Covers reactivity, event handling, styling, integration with libraries") and when ("Load this skill whenever in a Svelte project and asked to write/edit or analyze a Svelte component or module"), matching the anchor for both what AND when with explicit triggers. Not a 2 because the when-clause is explicit rather than implied.

3 / 3

Trigger Term Quality

"in a Svelte project", "write/edit or analyze a Svelte component or module" are natural phrases a user would actually say, giving good coverage of trigger terms within the Svelte niche. Not a 2 because it goes beyond a single keyword to several natural variations.

3 / 3

Distinctiveness Conflict Risk

The skill is tightly scoped to Svelte with distinct triggers ("Svelte project", "Svelte component or module"), making it unlikely to fire for non-Svelte skills. Not a 2 because the niche is unambiguous rather than broadly overlapping.

3 / 3

Total

11

/

12

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.