nuxtjs-project-starter
Scaffold a Nuxt 3.x project with auto-imports, layouts, `definePageMeta`, `useFetch`/`useAsyncData`, server routes, Nitro config, and SSR/SPA mode conventions.
79
71%
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/nuxtjs-project-starter/SKILL.mdQuality
Discovery
50%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 listing concrete Nuxt 3-specific features and APIs. However, it critically lacks any 'Use when...' guidance, which is essential for Claude to know when to select this skill from a large skill library. The trigger terms are technically accurate but could benefit from more natural user language variations.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks to create a Nuxt project, scaffold a Vue SSR application, or mentions Nuxt 3, Nitro, or server-side rendering with Vue.'
Include natural language variations users might say: 'Vue framework', 'create new Nuxt app', 'Nuxt starter', 'Vue SSR project'
Consider adding file patterns or commands users might mention: 'nuxt.config.ts', 'npx nuxi init', '.vue files with server routes'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and features: 'auto-imports, layouts, definePageMeta, useFetch/useAsyncData, server routes, Nitro config, and SSR/SPA mode conventions' - these are all specific Nuxt 3 capabilities. | 3 / 3 |
Completeness | Describes what the skill does (scaffold Nuxt 3 projects with various features) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes technical terms like 'Nuxt 3.x', 'useFetch', 'Nitro', 'SSR/SPA' that developers would use, but missing common variations like 'Vue framework', 'create Nuxt app', 'new Nuxt project', or file extensions. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche - 'Nuxt 3.x' is a specific framework, and the technical terms like 'definePageMeta', 'Nitro config' are unique to Nuxt, making conflicts with other skills unlikely. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
92%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, comprehensive Nuxt 3 starter skill with excellent actionability and conciseness. The code examples are complete and executable, covering the full stack from pages to server routes. The main weakness is the monolithic structure - the extensive patterns section could be split into separate reference files for better progressive disclosure.
Suggestions
Consider splitting 'Essential Patterns' into separate files (e.g., SERVER_ROUTES.md, LAYOUTS.md, DATA_FETCHING.md) and linking from the main skill
Add a brief 'Troubleshooting' or 'Common Issues' section for typical scaffold problems (port conflicts, module resolution errors)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is dense with actionable content and avoids explaining concepts Claude already knows (no explanations of what Vue is, what SSR means, etc.). Every section provides concrete code or configuration without padding. | 3 / 3 |
Actionability | Fully executable code examples throughout - scaffold commands, complete Vue components, TypeScript server routes, and configuration files are all copy-paste ready. No pseudocode or vague instructions. | 3 / 3 |
Workflow Clarity | Clear sequencing in 'First Steps After Scaffold' section with numbered steps. The project structure is well-documented, and the 'Common Commands' section provides explicit commands for each development phase. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's a monolithic document (~400 lines) that could benefit from splitting detailed patterns (server routes, composables, layouts) into separate reference files. Integration notes at the end hint at external modules but don't link to detailed guides. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 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.