CtrlK
BlogDocsLog inGet started
Tessl Logo

sveltekit

SvelteKit routing, load functions, server-only modules, form actions, hooks, cookies, env, adapters, and invalidation. Use when editing +page.ts, +page.server.ts, +layout.ts, +server.ts, hooks.server.ts, app.d.ts, or SvelteKit route behavior.

68

Quality

81%

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 concise, well-organized instruction-only reference with specific API-level guidance and a clear grounding/verification flow. It lacks executable code examples and most content is topical directives rather than sequenced workflows, capping actionability and workflow clarity at 2.

Suggestions

Add one short executable snippet per major area (e.g., a +page.server.ts load+form action with fail(), a hooks.server.ts locals setup) to move actionability toward copy-paste ready.

Framing the load/invalidation and server-vs-universal sections as an ordered decision process (choose file type -> place code -> declare dependencies -> validate) with an explicit verify step would raise workflow clarity.

Show the depends/invalidate tracking pattern concretely (e.g., depends('custom:tag') + invalidate) since the body warns not to assume server fetches are trackable without an explicit dependency.

DimensionReasoningScore

Conciseness

The body is a lean set of directive bullets that assumes Claude knows SvelteKit, with no padding or explanation of basic concepts; every line ('Use fail() for validation failures', 'Server load return values must be serializable') earns its place.

3 / 3

Actionability

Guidance names concrete APIs and files (depends, invalidate, fail(), use:enhance, event.locals, +page.server.ts, $types), but there are no executable code examples showing how the pieces fit together, so it is not copy-paste ready as the score-3 anchor requires.

2 / 3

Workflow Clarity

The Upstream Grounding section sequences 'ask DeepWiki -> verify against local installed types and source' with a checkpoint, but the rest of the skill is unsequenced topic directives rather than a structured multi-step workflow with validation feedback loops.

2 / 3

Progressive Disclosure

The body is under 50 lines with no bundle files, organized into well-labeled sections (Server Versus Universal Code, Loading/Invalidation/Forms, Types And Boundaries) and only one-level references (repo links, DeepWiki), satisfying the simple-skill guideline.

3 / 3

Total

10

/

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 tight, third-person description with an explicit 'Use when' trigger and concrete filename triggers, clearly distinguishing it from sibling skills. Its main weakness is enumerating capability topics rather than concrete actions, which caps specificity at 2.

DimensionReasoningScore

Specificity

It enumerates a comprehensive domain ('routing, load functions, server-only modules, form actions, hooks, cookies, env, adapters, and invalidation') but these are topics rather than concrete verb-actions like the score-3 anchor ('Extract... fill... merge'), so it lands at 'names domain and some actions'.

2 / 3

Completeness

It explicitly states both what ('routing, load functions... invalidation') and when ('Use when editing +page.ts... or SvelteKit route behavior'), matching the score-3 anchor with an explicit 'Use when' trigger.

3 / 3

Trigger Term Quality

The 'Use when editing +page.ts, +page.server.ts, +layout.ts, +server.ts, hooks.server.ts, app.d.ts' clause lists the exact filenames a SvelteKit user would naturally mention, giving strong coverage of natural trigger terms.

3 / 3

Distinctiveness Conflict Risk

SvelteKit-specific subsystems and filenames form a clear niche unlikely to trigger for unrelated skills; it would not conflict with the sibling 'svelte' component-runins skill.

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