CtrlK
BlogDocsLog inGet started
Tessl Logo

svelte5

Reviews Svelte components for idiomatic patterns, identifies anti-patterns carried over from React/Vue/Svelte 4, and suggests Svelte 5 refactorings. Use when writing or reviewing Svelte components, asking "is this idiomatic", "Svelte way", doing Svelte 5 migration, or encountering smells like: effect assigns state, prop copied to $state, global store by default, $bindable everywhere, clickable div, createEventDispatcher, export let, on:click, slot-shaped APIs, lifecycle-driven code, imperative DOM wiring, immutable-update ceremony, context value replacement, shadcn-svelte form structure, Field.* components, bits-ui form controls, or component APIs that hide ownership. This is the general-purpose entry point for Svelte component review; delegates to sveltekit for routes/load/actions/server concerns and to focused references for details.

100

1.12x
Quality

100%

Does it follow best practices?

Impact

100%

1.12x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tightly written, highly actionable overview that front-loads principles, gives a sequenced review workflow with a version-detection gate, and cleanly delegates detail to one-level-deep reference files that all exist. It matches the best reference examples across all four dimensions.

DimensionReasoningScore

Conciseness

Lean, opinionated prose that assumes Svelte competence; every numbered principle earns its place with a tight one-line rule plus a concrete do/don't example, with no padding explaining what Svelte or runes are.

3 / 3

Actionability

Provides fully executable, copy-paste-ready Svelte 5 snippets (e.g. `$derived(count * 2)`, `let { onSelect } = $props()`) with explicit bad/good pairs, plus a concrete review procedure and a smell-index table mapping each smell to a reference file.

3 / 3

Workflow Clarity

The 'Running a Review' section gives a clear 4-step sequenced procedure including a validation checkpoint ('Detect the version first') that gates which syntax set to apply, with feedback logic for version mismatches; the smell index provides a checkable scan list.

3 / 3

Progressive Disclosure

SKILL.md is a concise overview with 20 one-level-deep, clearly signaled references (all verified to exist as real files in references/), each linked inline from its principle and aggregated in a navigable smell-index table; detail is appropriately split out rather than inlined.

3 / 3

Total

12

/

12

Passed

Description

100%

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 is specific, trigger-rich, and explicitly scopes both what it does and when to use it, with a third-person voice and clear delegation boundaries. It is among the strongest descriptions in the reference set.

DimensionReasoningScore

Specificity

Names concrete review actions ('Reviews Svelte components', 'identifies anti-patterns', 'suggests Svelte 5 refactorings') and enumerates many specific smell categories, matching the 'multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what (reviews components, identifies anti-patterns, suggests refactorings) and when via a clear 'Use when...' clause with concrete triggering situations, satisfying the top anchor.

3 / 3

Trigger Term Quality

Lists natural trigger phrases users would actually say ('is this idiomatic', 'Svelte way', 'doing Svelte 5 migration') plus concrete code-smell terms (createEventDispatcher, export let, on:click, clickable div), giving broad natural coverage.

3 / 3

Distinctiveness Conflict Risk

Has a clear, narrow niche (Svelte 5 component idiomaticity) with distinct triggers and explicit scope boundaries ('delegates to sveltekit for routes/load/actions/server concerns'), making conflicts with other skills unlikely.

3 / 3

Total

12

/

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
joshuadavidthomas/agent-skills
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.