CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

sveltekit

Build full-stack web applications with SvelteKit — file-based routing, SSR, SSG, API routes, and form actions in one framework.

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/sveltekit/SKILL.md

The canonical home for this skill is sveltekit in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

68%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 well-structured, highly concrete SvelteKit tutorial skill whose body is mostly executable code with clear sequencing. Its main weaknesses are the total absence of validation checkpoints in the workflow, a deprecated scaffolding command, and Svelte 4-era syntax that predates the skill's 2026 date.

Suggestions

Add verification checkpoints to the workflow (e.g., after Step 1: run `npm run dev` and confirm the welcome page renders; after each code step: run `npm run check` for typecheck) so the sequence includes feedback loops.

Replace the deprecated `npm create svelte@latest` with the current `npx sv create` scaffolding command and update the interactive prompt options to match.

Update code examples to Svelte 5 / runes syntax (`let { data } = $props()` instead of `export let data`, `onclick` instead of `on:click`) so snippets run on current versions.

DimensionReasoningScore

Conciseness

The body is dominated by dense, executable code and concrete file-convention tables rather than padded prose. Minor trimmable material remains: the Overview paragraph restates the frontmatter description almost verbatim ("file-based routing, server-side rendering (SSR), static site generation (SSG), API routes") and adds marketing framing like "ships zero runtime overhead to the browser".

4 / 5

Actionability

Concrete, copy-paste-ready TypeScript/Svelte snippets cover setup, routing, load functions, +server.ts endpoints, form actions, layouts, hooks, and rendering modes. However, the primary scaffold command `npm create svelte@latest` is deprecated (replaced by `npx sv create` in 2024), and snippets use Svelte 4-era syntax (`export let data`, `on:click`) rather than Svelte 5 runes, so first-run and snippet currency on modern versions are minor gaps.

4 / 5

Workflow Clarity

Steps 1–7 (setup → routing → load → API routes → form actions → layouts → rendering modes) form a coherent, well-sequenced tutorial. But no validation or verification checkpoints appear anywhere — no dev-server smoke check, build, or typecheck after code changes — which leaves the sequence without explicit checkpoints. Not 4 because anchor 4 expects most checkpoints present.

3 / 5

Progressive Disclosure

No bundle files exist, and the single ~270-line file is cleanly sectioned (Overview, When to Use, steps, Examples, Best Practices, Security, Pitfalls, Related Skills) with no buried or nested references. Minor gap: at this length, Examples and Common Pitfalls could be offloaded to reference files to keep SKILL.md a leaner overview.

4 / 5

Total

15

/

20

Passed

Description

66%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 specific, third-person description that clearly states what the skill does and covers SvelteKit's headline capabilities with good natural keywords. Its main gap is the missing "when to use" trigger clause, which both caps completeness and slightly weakens trigger-term quality.

Suggestions

Append an explicit trigger clause, e.g., "Use when building or migrating apps with SvelteKit, or when the user mentions SvelteKit, Svelte routing, +page.svelte, load functions, or form actions."

Add "Svelte" as a synonym keyword so the description also fires when users say just "Svelte" while meaning the full-stack framework.

DimensionReasoningScore

Specificity

"Build full-stack web applications with SvelteKit" names a concrete action, and "file-based routing, SSR, SSG, API routes, and form actions" enumerates several specific capabilities. Not 5 because only one verb carries the action list and coverage omits load functions and hooks; not 3 because it goes well beyond naming 1–2 actions.

4 / 5

Completeness

"Build full-stack web applications with SvelteKit — file-based routing, SSR, SSG, API routes, and form actions" answers "what" clearly and concretely, but there is no "Use when…" clause or equivalent explicit trigger guidance, which the rubric caps at 3.

3 / 5

Trigger Term Quality

Includes natural terms users would say: "SvelteKit", "full-stack web applications", "SSR", "SSG", "API routes", "form actions". A few natural variations are missing, notably plain "Svelte" (users frequently say just "Svelte" when meaning SvelteKit) and "Svelte 5".

4 / 5

Distinctiveness Conflict Risk

Naming the specific framework "SvelteKit" gives a clear niche with distinct triggers. Minor overlap risk remains with a closely related plain-Svelte or generic full-stack skill, which matches anchor 4 rather than the minimal-conflict anchor 5.

4 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills/skills/sveltekit/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.