CtrlK
BlogDocsLog inGet started
Tessl Logo

svelte

Svelte 5 component and state-module patterns for Epicenter apps. Use when editing `.svelte`, `.svelte.ts`, or Svelte UI state code involving runes, `$props`, snippets, keyed lifecycles, `{#await}`, TanStack Query, `SvelteMap`/`SvelteSet`, `createSubscriber`, `$state.raw`, shadcn-svelte, or workspace observers.

70

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

72%

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

A well-structured, actionable Svelte 5 patterns skill with clean progressive disclosure and real reference files. The main weakness is verbosity in a few rationale-heavy bullets and the absence of explicit verification feedback loops in its grounding workflow.

Suggestions

Tighten the longest bullets (e.g. $state.raw, createSubscriber, SvelteSet): lead with the directive and move the 'why' rationale into the relevant reference file, keeping the overview directive-first.

Add an explicit validation checkpoint in Upstream Grounding (e.g. 'If local installed types contradict DeepWiki, the local types win — re-run the check before changing code') to give the grounding workflow a concrete feedback loop.

Consider trimming the per-bullet exemplar callouts in Core Decisions to a single named exemplar each; the second exemplars often repeat the same pattern and add tokens without new signal.

DimensionReasoningScore

Conciseness

The body is dense and free of generic 'what is Svelte' padding, but several bullets ($state.raw, createSubscriber, SvelteSet) embed lengthy rationale that could be tightened without losing the directive.

2 / 3

Actionability

Concrete directives with specific syntax ('label="Loading {name}"', SvelteMap, satisfies Record lookup, {@render}) and named exemplars (createPersistedState, from-kv, auth, from-table) make the guidance directly actionable even without full code blocks.

3 / 3

Workflow Clarity

The Source Checks and Upstream Grounding sections give a sequenced check-then-verify process, but there are no explicit error-recovery feedback loops and the validation checkpoints are largely implicit.

2 / 3

Progressive Disclosure

A focused overview with a Reference Map that signals one-level-deep references tied to specific change triggers; all three referenced files (lifecycle-and-reactivity.md, component-ui-patterns.md, mutations-and-workspace-inputs.md) exist in ./references/.

3 / 3

Total

10

/

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.

A concise, third-person description with explicit 'what' and 'when' clauses and a rich set of concrete, natural trigger terms. It cleanly distinguishes itself from sibling skills via Svelte 5 / Epicenter-specific triggers.

DimensionReasoningScore

Specificity

Names the domain ('Svelte 5 component and state-module patterns for Epicenter apps') and lists many concrete technologies — runes, $props, snippets, keyed lifecycles, {#await}, TanStack Query, SvelteMap/SvelteSet, createSubscriber, $state.raw, shadcn-svelte.

3 / 3

Completeness

Explicitly answers both what ('Svelte 5 component and state-module patterns for Epicenter apps') and when ('Use when editing .svelte, .svelte.ts, or Svelte UI state code involving...').

3 / 3

Trigger Term Quality

'Use when editing .svelte, .svelte.ts, or Svelte UI state code involving runes, $props, snippets...' are terms a developer naturally says when they need this skill, with strong coverage of natural variations.

3 / 3

Distinctiveness Conflict Risk

A clear Svelte 5 / Epicenter niche with highly specific rune and API triggers makes it unlikely to fire for the wrong skill.

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
EpicenterHQ/epicenter
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.