svelte-project-starter
Scaffold a SvelteKit 2.x project with Svelte 5 runes, file-based routing, load functions, form actions, and adapter configuration for multiple deployment targets.
77
72%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./frontend/svelte-project-starter/SKILL.mdQuality
Discovery
67%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 excels at specificity and distinctiveness by naming exact framework versions and concrete features. However, it lacks explicit trigger guidance ('Use when...') and could benefit from more natural user-facing keywords like 'create', 'new project', or 'setup' that users would actually say when requesting this skill.
Suggestions
Add a 'Use when...' clause with trigger scenarios like 'Use when the user wants to create a new SvelteKit project, scaffold a Svelte app, or set up a Svelte 5 application'
Include natural user keywords such as 'create', 'new project', 'setup', 'init', 'start', or 'bootstrap' that users commonly say when requesting project scaffolding
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Scaffold a SvelteKit 2.x project', 'Svelte 5 runes', 'file-based routing', 'load functions', 'form actions', and 'adapter configuration for multiple deployment targets'. These are all concrete, technical capabilities. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific scaffolding capabilities, but lacks any 'Use when...' clause or explicit trigger guidance for when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes relevant technical terms like 'SvelteKit 2.x', 'Svelte 5 runes', 'file-based routing', 'load functions', 'form actions', but missing common user variations like 'create Svelte app', 'new SvelteKit project', 'Svelte setup', or 'svelte init'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific framework versions (SvelteKit 2.x, Svelte 5) and unique features (runes, form actions). Unlikely to conflict with other project scaffolding skills due to precise technology stack identification. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%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 SvelteKit starter skill with excellent actionability - nearly every pattern includes complete, executable code examples with proper TypeScript typing. The workflow is clear for the scaffolding use case. Main weaknesses are the document length (could split advanced topics into separate files) and some minor verbosity in explanatory comments that Claude doesn't need.
Suggestions
Split advanced patterns (hooks, adapters, integration notes) into separate reference files like HOOKS.md, ADAPTERS.md, and link to them from the main skill
Remove explanatory comments like '# $state — reactive state (replaces `let x = ...` reactivity)' since Claude understands Svelte 5 runes
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy (e.g., explaining what file-based routing is when Claude knows this). The project structure section is thorough but could be trimmed. However, most content is practical code examples rather than explanations. | 2 / 3 |
Actionability | Excellent executable code examples throughout - scaffold commands, complete component examples, server load functions, form actions, API routes, and hooks are all copy-paste ready with proper TypeScript types and real-world patterns. | 3 / 3 |
Workflow Clarity | Clear sequenced workflow in 'First Steps After Scaffold' section with explicit verification step (npm run check). The scaffold command includes specific prompts to select. For a project starter skill, the workflow is appropriately simple and unambiguous. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's a monolithic document (~400 lines) that could benefit from splitting advanced patterns (hooks, adapters, integration notes) into separate reference files. No external file references are provided. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (520 lines); consider splitting into references/ and linking | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- achreftlili/deep-dev-skills
- Commit
181fcbc
- 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.