CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

60

Quality

71%

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

63%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.

The body is well-structured and actionable with real bundle references and scripts, but it is hurt by duplicated sections, dead templates/ references, and inlined troubleshooting content that belongs in the existing reference file.

Suggestions

Remove the 'Working with Templates' section or create the referenced templates/*.ts files; do not advertise assets that are not in the bundle.

Consolidate the duplicate 'When to Use This Skill', 'When to Load References', and 'Development Workflow' sections so each piece of guidance appears once.

Move the inlined 'Top 5 Common Errors' into references/troubleshooting.md and replace it with a short pointer, since that reference already exists.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete code and commands, but several sections duplicate others ('When to Use This Skill' reuses description triggers, 'When to Load References' repeats inline per-section references, 'Development Workflow'/'Production Deployment' rehash earlier steps) and version info appears in multiple places.

3 / 5

Actionability

Provides concrete, mostly copy-paste-ready commands and code blocks (npx module add, nuxt.config.ts presets, env var patterns); minor gaps include the templates/ files that are referenced but absent from the bundle.

4 / 5

Workflow Clarity

Multi-step processes (Installation, Production Deployment) are clearly sequenced and a Validation Checklist exists, but the risky deployment/DNS workflow does not wire validate-config.sh in as an explicit validate->fix->retry checkpoint.

4 / 5

Progressive Disclosure

References and scripts are real, one-level-deep, and clearly signaled, but the 'Working with Templates' section points to five templates/*.ts files that do not exist in the bundle, and the ~70-line 'Top 5 Common Errors' is inlined rather than deferred to troubleshooting.md.

3 / 5

Total

14

/

20

Passed

Description

78%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, trigger-rich description that clearly signals when to use the skill and distinguishes it from peers. It would benefit from a concise declarative 'what this does' sentence and coverage of troubleshooting use cases.

Suggestions

Lead with a single declarative capability sentence (e.g. 'Sets up and deploys Nuxt Studio, a visual content editor for Nuxt Content sites.') before the trigger list.

Add troubleshooting triggers such as 'Studio authentication loop' or 'Studio build failure' to cover the diagnostic use cases the body addresses.

DimensionReasoningScore

Specificity

Enumerates several concrete actions ('set up Nuxt Studio', 'configure Studio OAuth', 'deploy Studio to Cloudflare', 'add visual editor to Nuxt', 'configure studio.domain.com subdomain') with comprehensive coverage of the domain, though troubleshooting/editor-config actions are absent.

4 / 5

Completeness

Explicit 'when' with concrete trigger phrases ('when the user asks to...') and an implicit 'what' conveyed through the enumerated actions, but lacks a single declarative capability statement.

4 / 5

Trigger Term Quality

Includes natural user phrases plus synonyms and component names ('set up Nuxt Studio', 'Nuxt CMS', 'TipTap editor', 'Monaco editor', 'studio.domain.com subdomain'); good coverage with a few natural variations missing.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Nuxt Studio) with distinct triggers (TipTap/Monaco editors, studio.domain.com subdomain) and minimal overlap risk with unrelated skills.

5 / 5

Total

17

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
secondsky/claude-skills
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.