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.
41
39%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/nuxt-studio/skills/nuxt-studio/SKILL.mdQuality
Discovery
44%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is essentially a long list of trigger phrases with no explanation of what the skill actually does. While it excels at trigger term coverage and distinctiveness within the Nuxt Studio niche, it completely lacks any description of concrete capabilities or actions. A user or Claude selecting this skill would know when to pick it but not what it will accomplish.
Suggestions
Add a 'what it does' section listing concrete actions, e.g., 'Configures Nuxt Studio module, sets up OAuth authentication providers, deploys Studio to Cloudflare Workers, configures subdomain routing, and integrates TipTap/Monaco editors for visual content editing.'
Restructure to lead with capabilities first, then follow with 'Use when...' clause, e.g., 'Sets up and configures Nuxt Studio for visual content management, including OAuth authentication, Cloudflare deployment, and editor integration. Use when...'
Remove redundant trigger phrases and consolidate — e.g., 'Nuxt CMS' and 'content management for Nuxt websites' overlap significantly and could be combined to keep the description concise.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists no concrete actions or capabilities. It only describes when to use the skill via trigger phrases, but never explains what the skill actually does (e.g., 'Configures OAuth providers', 'Sets up Cloudflare deployment', 'Installs Nuxt Studio module'). | 1 / 3 |
Completeness | The description answers 'when' extensively but completely fails to answer 'what does this do'. There is no explanation of the skill's capabilities, actions, or outputs. Per the rubric, this is 'Missing what OR when' — the 'what' is entirely absent. | 1 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'set up Nuxt Studio', 'configure Studio OAuth', 'deploy Studio to Cloudflare', 'add visual editor to Nuxt', 'Studio authentication', 'Nuxt CMS', 'visual content editing', 'TipTap editor', 'Monaco editor', and more. These are realistic phrases a user would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | The description is highly specific to Nuxt Studio with distinct triggers like 'Studio OAuth', 'studio.domain.com subdomain', 'TipTap editor', and 'Nuxt Studio module'. This is a clear niche unlikely to conflict with other skills. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is well-structured in concept with good progressive disclosure design and a useful troubleshooting section, but suffers from significant verbosity and over-explanation. Many sections describe concepts rather than providing actionable instructions, and the referenced bundle files don't exist, undermining the progressive disclosure strategy. The workflow lacks explicit validation checkpoints between critical steps like OAuth configuration and deployment.
Suggestions
Cut the content by at least 50%: remove the Overview paragraph, 'When to Use This Skill' section, 'Integration with Other Skills', 'Additional Resources', and 'Version Information' sections — these waste tokens on information Claude can infer or that belongs in frontmatter.
Add validation checkpoints to the deployment workflow: after OAuth setup, include a concrete test command; after Cloudflare deployment, include a curl command to verify the endpoint responds correctly.
Provide the referenced bundle files (oauth-providers.md, cloudflare-deployment.md, etc.) or inline the critical content — currently the skill defers key actionable details to files that don't exist.
Move the troubleshooting section to the referenced troubleshooting.md file and keep only a brief 'common gotcha' note inline (e.g., OAuth callback URL must match deployment URL exactly).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~300 lines. It explains what Nuxt Studio is, what editors it provides, when to use the skill, and includes sections like 'Integration with Other Skills' and 'Additional Resources' that add little actionable value. Many sections describe rather than instruct, and Claude doesn't need explanations of what OAuth is or what editor types exist. | 1 / 3 |
Actionability | There are some concrete commands (npx nuxi module add, config snippets, env variable patterns) but much of the content is descriptive rather than executable. Key workflows like OAuth setup and Cloudflare deployment defer to reference files that don't exist in the bundle. The troubleshooting section provides solutions but some are vague (e.g., 'Check cookie settings in browser'). | 2 / 3 |
Workflow Clarity | The Development Workflow and Production Deployment sections provide numbered steps but lack validation checkpoints between steps. The validation checklist at the end is helpful but is disconnected from the workflow steps. There are no feedback loops (validate -> fix -> retry) for the deployment process, which involves potentially destructive/complex operations like DNS configuration and OAuth setup. | 2 / 3 |
Progressive Disclosure | The skill references multiple reference files (oauth-providers.md, cloudflare-deployment.md, editor-configuration.md, subdomain-setup.md, troubleshooting.md) and templates, which is good structure. However, no bundle files are provided, meaning all these references are broken. The main file also contains too much inline content that should be in references (e.g., the full troubleshooting section, prerequisites check, editor configuration). | 2 / 3 |
Total | 7 / 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
- secondsky/claude-skills
- Commit
5e92b71
- 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.