CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

svelte

Apply Epicenter’s Svelte 5 patterns for runes, components, lifecycles, and workspace-backed state. Use when editing `.svelte`, `.svelte.ts`, or Svelte UI state.

Quality

89%

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

78%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.

This is a high-quality patterns skill: every rule names exact APIs and project-specific conventions with do/don't contrast, verification checkpoints are built into the grounding and source-check procedures, and a Reference Map routes each kind of change to substantive one-level-deep reference files. The only notable weakness is a few over-long prose bullets that could be tightened or split for token efficiency.

DimensionReasoningScore

Conciseness

The body is dense and prescriptive with no teaching of concepts Claude already knows (no 'what is Svelte' padding), assuming competence throughout. It is not 5 because several bullets carry long justification clauses and one (the capabilities bullet in Core Decisions) is a multi-clause wall of prose that could be split or trimmed; not 3 because there is no real padding or unnecessary explanation.

4 / 5

Actionability

Concrete, executable guidance is pervasive: exact APIs (`SvelteMap`, `createSubscriber` from `svelte/reactivity`, `reactive(capability)` from `@epicenter/svelte/reactive`), inline code (`bind:value={get, set}`, `Snippet<[Row]>`, `const todo = todos.edit({ id })`, `label="Loading {name}"`, `satisfies Record` lookups), and specific file paths (`src/lib/app.ts`). It is not 5 because there are no complete copy-paste-ready code blocks covering common cases end-to-end; not 3 because the guidance is specific and executable, far beyond pseudocode or high-level hints.

4 / 5

Workflow Clarity

As a decision/patterns skill it provides clear procedures with verification checkpoints: the Source Checks section lists check-before-change gates per topic, and Upstream Grounding specifies 'verify decisive details against local installed types, source, or official docs before changing code' plus when to skip DeepWiki. It is not 5 because there is no explicit multi-step sequence with error-recovery feedback loops; not 3 because validation checkpoints are present and no risky batch/destructive operation lacks gating.

4 / 5

Progressive Disclosure

The body is an overview that routes detail to four real, substantive reference files (140-867 lines each), each linked inline with descriptive anchors and again in a dedicated Reference Map section that maps change types to the right file. References are one level deep with only lateral sibling cross-links, matching the anchor-5 'clear overview with well-signaled one-level-deep references; easy navigation' example.

5 / 5

Total

17

/

20

Passed

Description

95%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.

The description is a strong two-sentence pattern: a specific capability statement naming four concrete areas, followed by an explicit 'Use when' clause with file-extension triggers. It is concise, in third person, and highly distinguishable from other skills.

DimensionReasoningScore

Specificity

"Apply Epicenter's Svelte 5 patterns for runes, components, lifecycles, and workspace-backed state" lists four specific capability areas, matching the 'several specific actions; minor gaps' anchor. It stays at 4 rather than 5 because it uses a single verb ('Apply') over topic nouns instead of a comprehensive set of distinct concrete actions, and at 4 rather than 3 because it well exceeds naming just 1-2 items.

4 / 5

Completeness

Both halves are explicit: what it does ("Apply Epicenter's Svelte 5 patterns for runes, components, lifecycles, and workspace-backed state") and when to use it ("Use when editing `.svelte`, `.svelte.ts`, or Svelte UI state") with concrete trigger phrases. This directly matches the anchor-5 example structure of what + when with concrete triggers.

5 / 5

Trigger Term Quality

Natural terms users would say are comprehensively covered: "runes", "components", "lifecycles", "Svelte UI state", plus file extensions ".svelte" and ".svelte.ts" — mirroring the anchor-5 pattern of including extensions like '.pdf'. Not 4 because no commonly used synonym or phrasing for triggering this skill is missing.

5 / 5

Distinctiveness Conflict Risk

"Epicenter's Svelte 5 patterns" carves a clear org-specific niche, and the triggers (runes, `.svelte`/`.svelte.ts` file extensions, Svelte UI state) are distinct and unlikely to fire for unrelated skills. Not 4 because no meaningful overlap risk with closely related skills is apparent from the description itself.

5 / 5

Total

19

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

EpicenterHQ/epicenter

Path

.agents/skills/svelte/SKILL.md

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.