CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nuxt-data

| Nuxt 4 data management: composables, data fetching with useFetch/useAsyncData, and state management with useState and Pinia. Use when: creating custom composables, fetching data with useFetch or useAsyncData, managing global state with useState, integrating Pinia, debugging reactive data issues, or implementing SSR-safe state patterns.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-organized reference whose code examples are complete and executable, with excellent reference signaling via the 'When to Load References' section. Its weaknesses are noticeable content duplication (two anti-pattern sections repeat earlier material verbatim) and a broken reference: pinia-integration.md is referenced but missing from the bundle.

Suggestions

Consolidate duplicated content: the 'Using ref Instead of useState' and 'Mutating Shallow Refs' anti-patterns repeat the 'useState vs ref' and 'Shallow vs Deep Reactivity' sections verbatim — keep one copy each.

Create references/pinia-integration.md or remove the 'Load references/pinia-integration.md' block — the file is referenced in the body but does not exist in the bundle.

Trim the full useAuth and useCart composable listings to minimal exemplars and point to references/composables.md, which already covers advanced composable patterns in depth.

DimensionReasoningScore

Conciseness

The body is code-first and mostly efficient, but contains verbatim duplication: 'Using ref Instead of useState' repeats the earlier 'useState vs ref' section, 'Mutating Shallow Refs' repeats 'Shallow vs Deep Reactivity (v4 Change)', and the 'Simple counter' snippet repeats the useCounter example — clearly more than minor trimming.

3 / 5

Actionability

Fully executable, copy-paste-ready TypeScript throughout: useFetch with options, reactive params, transform, pick, error handling with status values, execute/refresh with immediate: false, getCachedData caching, lazy variants, complete useAuth/useCart composables, and end-to-end Pinia setup including the install command and nuxt.config.ts.

5 / 5

Workflow Clarity

As a pattern-reference skill with no destructive or batch operations it needs no validation checkpoints, and it is well organized: quick-reference tables, a 'When to Load References' decision section, topic sections, anti-patterns, and a symptom-to-fix troubleshooting section ('Data Not Refreshing When Params Change' → 'Ensure params are reactive'). Falls short of 5 only because there is no explicit multi-step workflow with checkpoints.

4 / 5

Progressive Disclosure

Good structure with an explicit 'When to Load References' section giving per-file trigger conditions and one-level-deep references that exist (composables.md, data-fetching.md, each with a TOC). However, the referenced references/pinia-integration.md does not exist in the bundle — following that guidance yields a file-not-found — keeping it below the anchor-5 'easy navigation' bar.

4 / 5

Total

16

/

20

Passed

Description

88%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that names the domain, version, and specific APIs, and pairs a clear capability statement with an explicit multi-trigger 'Use when' clause. Keyword coverage is good though not exhaustive, and there is minor overlap risk with the related nuxt skill family.

DimensionReasoningScore

Specificity

Lists multiple concrete actions tied to named APIs — 'creating custom composables', 'fetching data with useFetch or useAsyncData', 'managing global state with useState', 'integrating Pinia', 'debugging reactive data issues', 'implementing SSR-safe state patterns' — comprehensively covering the skill's domain with no notable gaps.

5 / 5

Completeness

Explicitly answers both questions: the 'what' ('Nuxt 4 data management: composables, data fetching with useFetch/useAsyncData, and state management with useState and Pinia') and an explicit 'Use when:' clause with six concrete trigger phrases.

5 / 5

Trigger Term Quality

Good coverage of natural Nuxt terms (composables, useFetch, useAsyncData, useState, Pinia, reactive data, SSR), but a few common user phrasings such as 'hydration', 'refresh/refetch', and 'caching' are missing, so it falls short of the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

Scoped to Nuxt 4 with framework-specific APIs (useState, useFetch, Pinia) giving a clear niche, but closely related sibling skills (nuxt-core, nuxt-server) mean minor overlap risk for triggers like general composable creation or server-side data fetching.

4 / 5

Total

18

/

20

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 — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (570 lines); consider splitting into references/ and linking

Warning

metadata_field

'metadata' should map string keys to string values

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

13

/

16

Passed

Repository

secondsky/claude-skills

Path

plugins/nuxt-v4/skills/nuxt-data/SKILL.md

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.