nuxthub
Use when building NuxtHub v0.10.6 applications - provides database (Drizzle ORM with sqlite/postgresql/mysql), KV storage, blob storage, and cache APIs. Covers configuration, schema definition, migrations, multi-cloud deployment (Cloudflare, Vercel), and the new hub:db, hub:kv, hub:blob virtual module imports.
90
86%
Does it follow best practices?
Impact
96%
1.18xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly identifies its niche (NuxtHub v0.10.6), lists concrete capabilities across multiple domains (database, storage, caching, deployment), and includes an explicit 'Use when' trigger. The inclusion of specific technology names, version numbers, and virtual module import patterns makes it highly discoverable and distinctive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and capabilities: database with Drizzle ORM (sqlite/postgresql/mysql), KV storage, blob storage, cache APIs, configuration, schema definition, migrations, multi-cloud deployment (Cloudflare, Vercel), and virtual module imports. | 3 / 3 |
Completeness | Clearly answers both 'what' (database, KV, blob, cache APIs, configuration, migrations, deployment) and 'when' with an explicit 'Use when building NuxtHub v0.10.6 applications' trigger clause at the start. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms a user would say: 'NuxtHub', 'Drizzle ORM', 'sqlite', 'postgresql', 'mysql', 'KV storage', 'blob storage', 'cache', 'migrations', 'Cloudflare', 'Vercel', 'hub:db', 'hub:kv', 'hub:blob'. These are highly specific and match what developers would naturally reference. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with the specific 'NuxtHub v0.10.6' version reference, specific virtual module imports (hub:db, hub:kv, hub:blob), and the combination of Drizzle ORM with NuxtHub. Very unlikely to conflict with generic database or deployment skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, comprehensive skill that covers NuxtHub's full feature set with excellent actionability and progressive disclosure. The code examples are complete and executable across all major features (database, KV, blob, cache, deployment). The main weakness is the lack of explicit validation checkpoints in multi-step workflows like database migrations and deployment, and some minor verbosity in explanatory notes that Claude wouldn't need.
Suggestions
Add explicit validation/verification steps to the migration workflow (e.g., 'After `npx nuxt db generate`, review the generated SQL in the migrations directory before applying with `npx nuxt db migrate`').
Remove repeated statements like 'auto-imported on server-side' which appears in multiple sections — state it once in a conventions section or the quick reference table.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient with good use of tables and code blocks, but includes some unnecessary explanations (e.g., 'remote mode' explanation, 'Database replica' explanation) and the 'All are auto-imported on server-side' is repeated multiple times. The content is dense but could be tightened in places. | 2 / 3 |
Actionability | Excellent actionability throughout — fully executable code examples for schema definition, CRUD operations, KV, blob, cache, migrations CLI commands, deployment config, and upload handlers. All examples are copy-paste ready with real imports and complete syntax. | 3 / 3 |
Workflow Clarity | Migration workflow is listed as CLI commands but lacks explicit validation checkpoints or error recovery steps. The deployment section provides configuration but doesn't sequence the steps clearly (create resources → configure → deploy → verify). For database schema changes involving migrations, there's no validate-then-proceed pattern. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a clear checklist for loading reference files (wrangler-templates.md, providers.md) only when needed, explicit 'DO NOT load all files at once' instruction, and well-signaled references throughout (e.g., 'See references/providers.md for detailed deployment patterns'). Content is well-organized with clear sections. | 3 / 3 |
Total | 10 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- popey/nuxt-skills
- Commit
6b12458
- 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.