AD react-seo-skills
Guides SEO and AI-search visibility for Next.js, Astro, and React apps in Cursor, Claude Code, and Codex. Use when setting up metadata, Open Graph, Twitter cards, Schema.org JSON-LD, sitemaps, robots.txt, optional llms.txt, keyword research, clustering, auditing SEO, improving discoverability, or setting up structured data. Covers Next.js App Router, Pages Router, Astro, and Vite + React SPAs. Matches JavaScript or TypeScript to the project language.
Guides SEO and AI-search visibility for Next.js, Astro, and React apps in Cursor, Claude Code, and Codex. Use when setting up metadata, Open Graph, Twitter…
As a process D 45/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, failures and branches
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 12. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 45/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (react-seo-skills) differs from the folder (skill)
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 100Steps. 25 steps
- 100Execution cost. Instruction body is 2251 tokens
- 100Running it twice. No mutating operations
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (6 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +3Description length 454: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 25 items
- +4Reference files are cited in the instructions (9 of 10)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.