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 opens with an explicit 'Use when' trigger clause. The inclusion of specific technology names, version numbers, and module import patterns provides excellent trigger term coverage and distinctiveness.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and capabilities: database with Drizzle ORM across sqlite/postgresql/mysql, KV storage, blob storage, cache APIs, configuration, schema definition, migrations, multi-cloud deployment, and virtual module imports. | 3 / 3 |
Completeness | Explicitly answers both 'what' (database, KV, blob, cache APIs, migrations, deployment) and 'when' ('Use when building NuxtHub v0.10.6 applications') with a clear trigger clause at the start. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'NuxtHub', 'Drizzle ORM', 'sqlite', 'postgresql', 'mysql', 'KV storage', 'blob storage', 'Cloudflare', 'Vercel', 'migrations', 'hub:db', 'hub:kv', 'hub:blob'. These cover many variations a developer would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with the specific 'NuxtHub v0.10.6' version, 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 — nearly every section has executable, copy-paste ready code. The progressive disclosure is well-handled with conditional file loading and cross-skill references. 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 running `npx nuxt db migrate`, verify with `npx nuxt db sql "SELECT name FROM sqlite_master"` to confirm tables exist')
Trim explanatory prose like the 'remote mode' and 'Database replica' paragraphs to single-line comments within the code blocks, since Claude can infer purpose from the config keys
| 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 deprecated section could be more terse. The provider tables and some config comments add mild verbosity but are mostly justified. | 2 / 3 |
Actionability | Excellent actionability throughout — executable code examples for every feature (schema definition, CRUD operations, KV, blob, cache, migrations), concrete CLI commands, specific environment variable names, and copy-paste ready configuration blocks. The upload helpers and Vue composables sections are particularly well-done. | 3 / 3 |
Workflow Clarity | Migration workflow is listed as commands but lacks explicit validation checkpoints or error recovery steps. The deployment section provides configuration but doesn't sequence the steps clearly (e.g., create resources → configure → deploy → verify). For database operations and deployment — both potentially destructive — the absence of validation/feedback loops caps this at 2. | 2 / 3 |
Progressive Disclosure | Well-structured with a clear checklist for loading reference files (wrangler-templates.md, providers.md), explicit guidance to not load all files at once, and appropriate cross-references to other skills (nuxt, nuxt-content). Content is organized into logical sections with a quick reference table and resources section for deeper exploration. | 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
- onmax/nuxt-skills
- Commit
3110745
- 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.