CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nuxt-seo

Nuxt SEO v5 modules (robots, sitemap, og-image, schema-org, link-checker, seo-utils, site-config). Use when implementing SEO, robots.txt, sitemaps, Schema.org, or meta tags in Nuxt apps.

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

77%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 highly actionable with copy-paste-ready commands and configuration, and the Quick Start includes explicit verification steps backed by an error→fix recovery table. The main weaknesses are redundancy (version data in three places, known issues duplicating both Critical Rules and the existing troubleshooting.md reference) and a Bundled Resources section that advertises 11 agent/command files absent from the bundle. Progressive disclosure navigation is otherwise excellent, with a complete and accurate reference-loading table.

Suggestions

Remove the 'Bundled Resources' Agents and Commands tables (or add the actual files): all 11 listed resources (e.g. seo-auditor.md, /seo-audit) do not exist in the bundle, so the section currently directs users to phantom files.

De-duplicate version information: module versions appear in the Module Overview table, the 'Package Versions (Verified 2026-08-03)' JSON block, and assets/package-versions.json — keep one canonical location (the assets file) and drop the inline JSON section.

Move most of the 14 'Known Issues Prevention' entries into references/troubleshooting.md (which already exists) and keep only the top 3–4 most common fixes inline; also mention scripts/init-nuxt-seo.sh in the body, since it is currently undiscoverable.

DimensionReasoningScore

Conciseness

Mostly efficient (dense tables, compact Error|Fix pairs), but version data appears three times — the Module Overview table, the 'Package Versions (Verified 2026-08-03)' JSON section, and assets/package-versions.json — and Issues #11–#13 repeat the v5 breaking changes already stated in Critical Rules. Per the rubric guideline, time-sensitive version numbers not confined to a deprecated section penalize conciseness; this fits anchor 3 ('could be tightened') better than 2, since no space is spent explaining concepts Claude already knows.

3 / 5

Actionability

Fully executable throughout: 'npx nuxt module add @nuxtjs/seo', a complete copy-paste-ready defineNuxtConfig example, explicit verification URLs ('/robots.txt', '/sitemap.xml', '/__robots__/debug-production.json'), and concrete fixes like "disallow: process.env.NUXT_PUBLIC_ENV === 'staging' ? ['/'] : []". Matches anchor 5 ('copy-paste ready code or commands; specific examples cover the common cases') rather than 4, which allows minor gaps.

5 / 5

Workflow Clarity

The Quick Start is a clearly sequenced 3-step workflow (Install → Configure Site Settings → 'Restart and Verify') ending in an explicit validation checkpoint with debug URLs, and the 14 'Known Issues Prevention' entries provide error→fix feedback loops for recovery. This matches anchor 5 ('clear sequence with explicit validation steps; feedback loops for error recovery'); no destructive/batch-operation cap applies.

5 / 5

Progressive Disclosure

The 'When to Load References' table is exemplary (17 rows, every cited file verified to exist, one level deep), but scoring against the actual bundle per the rubric guideline reveals real defects: the 'Bundled Resources' section lists 5 agents (e.g. 'seo-auditor.md') and 6 commands (e.g. '/seo-audit') that do not exist anywhere in the bundle, scripts/init-nuxt-seo.sh exists but is never surfaced, and ~50 lines of Known Issues content duplicate references/troubleshooting.md. These go beyond anchor 4's 'minor organization gaps', landing at anchor 3 ('content that should be separate is inline'; navigation claims that don't match the bundle).

3 / 5

Total

16

/

20

Passed

Description

82%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 with an explicit 'Use when' trigger clause, good natural keywords, and tight Nuxt-specific scoping that minimizes conflict risk. The main weakness is that the capability statement is a noun catalog of module names rather than a list of concrete actions, and a few natural trigger synonyms (Open Graph, JSON-LD, broken links) are absent.

DimensionReasoningScore

Specificity

The what-statement 'Nuxt SEO v5 modules (robots, sitemap, og-image, schema-org, link-checker, seo-utils, site-config)' is a catalog of module names rather than concrete actions; capability verbs appear only in the trigger clause ('implementing SEO, robots.txt, sitemaps, Schema.org, or meta tags'). Coverage is comprehensive but few explicit actions are stated, fitting anchor 3 better than anchor 4's 'lists several specific actions'.

3 / 5

Completeness

It explicitly answers both what ('Nuxt SEO v5 modules' with all 8 modules enumerated) and when ('Use when implementing SEO, robots.txt, sitemaps, Schema.org, or meta tags in Nuxt apps') with concrete trigger phrases — the exact anchor-5 pattern; not 4, since the 'when' clause is already explicit and specific.

5 / 5

Trigger Term Quality

Natural terms users would say are present: 'SEO', 'robots.txt', 'sitemaps', 'Schema.org', 'meta tags', 'Nuxt'. Common synonyms are missing — 'Open Graph'/'social sharing' (only the module name 'og-image' appears), 'structured data'/'JSON-LD', 'broken links', 'canonical URLs' — so it fits anchor 4 ('good keyword coverage; a few natural terms missing') rather than 5.

4 / 5

Distinctiveness Conflict Risk

Scoped tightly to 'Nuxt apps' and the named Nuxt SEO modules, giving a clear niche with distinct triggers and minimal conflict risk against generic SEO or web-development skills — matches anchor 5.

5 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

Passed

Repository

secondsky/claude-skills

Path

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