CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nuxt-studio

This skill should be used when the user asks to "set up Nuxt Studio", "configure Studio OAuth", "deploy Studio to Cloudflare", "add visual editor to Nuxt", "configure studio.domain.com subdomain", "Studio authentication", "Nuxt CMS", or mentions visual content editing, Nuxt Studio module, TipTap editor, Monaco editor, or content management for Nuxt websites.

Quality

74%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/nuxt-studio/skills/nuxt-studio/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 well-structured, largely actionable overview with a real one-level-deep reference bundle, a validation checklist, and an error-recovery catalog. The main deductions are repetition (reference pointers and version/date info restated multiple times), a missing explicit capability statement carried over from the description, and five advertised template files that don't exist in the bundle.

Suggestions

Remove the five 'templates/' entries (they don't exist in the bundle) or actually ship the template files — dangling advertised assets break navigation and trust.

De-duplicate reference pointers: drop the repeated 'consult references/oauth-providers.md' / 'see references/cloudflare-deployment.md' lines and the 'When to Load References' section that restates them, keeping one clearly signaled pointer per topic.

Confine time-sensitive version info ('v1.0.0-beta.3 as of December 2025') to the Version Information section only, removing the inline repetition in the Installation section, and correct the script invocation path to match the actual bundle layout.

DimensionReasoningScore

Conciseness

The body is task-oriented and avoids explaining concepts Claude already knows, but has real tightening opportunities: the same reference is pointed to multiple times ('references/oauth-providers.md' twice in one section at lines ~100 and ~124; cloudflare-deployment.md three times), the 'When to Load References' section restates the inline load directives, and time-sensitive version info ('v1.0.0-beta.3 as of December 2025') is repeated in three places rather than confined to the Version Information section. Not a 2 because there is no concept-explaining filler; not a 4 because the duplication and scattered version/date references are more than minor.

3 / 5

Actionability

Mostly executable guidance: concrete install command ('npx nuxi module add nuxt-studio@beta'), exact env-var names (NUXT_OAUTH_GITHUB_CLIENT_ID, etc.), copy-paste nuxt.config.ts snippets, callback URL patterns, and per-error solutions. Not a 5 because subdomain/DNS guidance stays high-level (deferred entirely to the reference), the script invocation path ('$CLAUDE_PLUGIN_ROOT/skills/nuxt-studio/scripts/...') doesn't match the bundle layout, and the advertised templates/*.ts files don't exist in the bundle; not a 3 because the core setup path is genuinely copy-paste ready.

4 / 5

Workflow Clarity

Clear sequences for installation, local dev, and production deployment (numbered steps with verify steps like 'Check that nuxt.config.ts includes the Studio module'), plus a Validation Checklist, an error catalog with cause/solution feedback loops, and validation utility scripts. Not a 5 because mid-workflow validation within the OAuth and Cloudflare sections is deferred to reference files rather than given as inline checkpoints; not a 3 because explicit validation is present at multiple points (checklist, error-recovery catalog, prerequisite script).

4 / 5

Progressive Disclosure

Good structure scored against the actual bundle: all five referenced files in references/ exist, are one level deep, and are clearly signaled ('load references/...'); scripts/ contains the three advertised scripts. The main organization gap is that the five advertised 'templates/' files (nuxt.config.ts, wrangler.toml, studio-auth-*.ts) do not exist in the bundle — a dangling navigation path. Not a 5 because of those phantom references; not a 3 because the real reference split and signaling are strong and content is appropriately placed in the overview.

4 / 5

Total

15

/

20

Passed

Description

68%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 trigger-rich, highly specific 'when' clause with good synonym coverage, but the description omits any explicit statement of what the skill does. Adding a one-clause capability summary ('Sets up, configures, and deploys Nuxt Studio...') before the trigger list would make it complete. No first/second-person voice issues; third person is used correctly.

Suggestions

Open with a concrete capability statement in third person, e.g. 'Sets up, configures, and deploys Nuxt Studio (visual CMS for Nuxt Content) with OAuth authentication and custom subdomains', before the 'Use when...' trigger list.

Trim the broadest triggers ('Nuxt CMS', 'content management for Nuxt websites') or qualify them with 'Nuxt Studio' to reduce overlap with generic Nuxt/CMS skills.

DimensionReasoningScore

Specificity

The description names the domain concretely via quoted task phrases ('set up Nuxt Studio', 'deploy Studio to Cloudflare', 'configure studio.domain.com subdomain'), but never explicitly states what the skill itself does — the quoted phrases are user utterances, not skill capabilities. Not a 4 because no capability statement ('Sets up, configures, and deploys...') is present; not a 2 because the tasks named are concrete and domain-specific rather than generic.

3 / 5

Completeness

The 'when' is explicit and thorough ('should be used when the user asks to...'), but the 'what' is never stated — the description never says what the skill does (e.g., 'Sets up and deploys Nuxt Studio, configures OAuth and subdomains'). Per the guideline to score only what is explicitly stated, this sits between anchor 2 ('only when present without what') and a full both-parts answer; the rich, detailed 'when' and the implied tasks lift it above 2, but the missing explicit 'what' keeps it below 4.

3 / 5

Trigger Term Quality

Comprehensive natural-language coverage with synonyms: 'set up Nuxt Studio', 'Studio authentication', 'Nuxt CMS', 'add visual editor to Nuxt', 'configure studio.domain.com subdomain', plus product-specific terms (TipTap editor, Monaco editor, Nuxt Studio module). Matches the anchor's 'comprehensive coverage of natural terms including synonyms'; no common variation is obviously missing.

5 / 5

Distinctiveness Conflict Risk

Mostly a clear niche (Nuxt Studio) with distinct triggers like 'configure Studio OAuth' and 'deploy Studio to Cloudflare'. Minor overlap risk: broad triggers such as 'Nuxt CMS', 'content management for Nuxt websites', and bare 'TipTap editor'/'Monaco editor' mentions could fire on generic CMS or editor questions better served by other skills; not a 5 for that reason, not a 3 because the core triggers are unmistakably Studio-specific.

4 / 5

Total

15

/

20

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

Validation for skill structure

No warnings or errors.

Repository

secondsky/claude-skills

Path

plugins/nuxt-studio/skills/nuxt-studio/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.