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, includes a 'Use when' clause, and provides rich trigger terms spanning frameworks, ORMs, storage types, and deployment targets. The specificity of the version number and virtual module import names make it highly distinctive. Minor improvement could include mentioning user-facing task language like 'setting up a NuxtHub project' but overall this is well-crafted.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and capabilities: database with Drizzle ORM across multiple dialects, 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 version 'NuxtHub v0.10.6', specific technologies (Drizzle ORM, Cloudflare, Vercel), and unique virtual module imports (hub:db, hub:kv, hub:blob). Very unlikely to conflict with other 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 with excellent actionability and progressive disclosure. The code examples are concrete and executable across multiple dialects and providers. The main weaknesses are moderate verbosity (some explanatory text that Claude doesn't need) and missing validation/error-recovery steps in multi-step workflows like migrations and deployment.
Suggestions
Add explicit validation checkpoints to the migration workflow (e.g., 'verify migration SQL before applying' and 'check migration status after apply') to improve workflow clarity.
Trim explanatory sentences like 'remote mode: When enabled, connects to production...' and 'Database replica (v0.10.6+): Configure read replicas...' — Claude can infer these from the config comments and context.
| 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 content is quite long for a SKILL.md that already references external files. Some sections like WebSocket and Build-time Hooks could be more terse or offloaded to references. | 2 / 3 |
Actionability | Excellent executable code examples throughout - schema definitions, CRUD operations, CLI commands, upload handlers, deployment configs, and migration commands are all copy-paste ready with specific syntax for each dialect and provider. | 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 (create resources -> configure -> deploy -> verify). For database operations involving migrations and schema changes, there are no feedback loops for error handling. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a clear checklist at the top for loading reference files, explicit instructions not to load all files at once, and well-signaled one-level-deep references to wrangler-templates.md and providers.md. The main file serves as a comprehensive overview while deferring detailed provider configs to reference files. | 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
00fb59d
- 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.