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.

73

Quality

90%

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

93%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, highly actionable Svelte best-practices skill with executable examples and excellent progressive disclosure via real reference files. Its only soft spot is workflow clarity, which is inherently limited because it is a topical reference rather than a sequenced process.

DimensionReasoningScore

Conciseness

Lean topical sections assume Claude's competence; no padding explaining what Svelte or runes are, and every explanatory sentence conveys non-obvious Svelte-specific semantics (e.g. $state.raw trade-offs, derived writability).

5 / 5

Actionability

Executable, copy-paste Svelte code blocks throughout, reinforced with 'do this / don't do this' contrasts for $derived, $props, events, snippets, and styling that cover the common cases.

5 / 5

Workflow Clarity

A topical best-practices reference rather than a multi-step workflow, but each section is unambiguous and well-ordered; no destructive/batch operations exist to require validation checkpoints, so it sits just below 5.

4 / 5

Progressive Disclosure

SKILL.md is a concise overview with clearly signaled, one-level-deep markdown links to references/ (attach, bind, inspect, snippet, render, each, await-expressions, hydratable, svelte-reactivity), all of which resolve to real bundle files.

5 / 5

Total

19

/

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-scoped description that clearly states both capabilities and an explicit activation trigger for Svelte work. Minor keyword synonyms (file extensions, SvelteKit) would round it out.

DimensionReasoningScore

Specificity

Names the Svelte domain and several concrete capability areas ('reactivity, event handling, styling, integration with libraries'), plus write/edit/analyze actions; the trailing 'and more' keeps it from a comprehensive 5.

4 / 5

Completeness

Explicitly answers both 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') with concrete triggers.

5 / 5

Trigger Term Quality

Natural terms users would say ('Svelte project', 'Svelte component', 'Svelte module') are present with an explicit trigger clause, but synonyms like '.svelte' and 'SvelteKit' are missing.

4 / 5

Distinctiveness Conflict Risk

Scoped tightly to Svelte components/modules with Svelte-specific triggers, giving it a clear niche with minimal overlap risk against non-Svelte 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.