Content
81%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A highly actionable, well-structured specialist skill with executable templates, explicit feedback loops, and disciplined use of its two reference files. Its main cost is length: repetitive GEO hedging and storytelling in the keyword-research section, plus several large sections kept inline that could be progressively disclosed.
Suggestions
State the GEO/AEO no-guarantee caveat once in that section and reference it from elsewhere (checklists, FAQPage notes) instead of repeating it five-plus times.
Trim the narrative examples from the keyword-research workflow steps (risoto/carne anecdotes, "peça a um amigo imparcial") to their actionable essence, leaving extended examples in references/keyword-research.md.
Move the self-contained local SEO, e-commerce, and international (hreflang) sections into separate reference files with one-line summaries and open-conditions inline, matching the pattern already used for keyword research.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and mostly earns its tokens, but the GEO/AEO no-guarantee caveat is restated five or more times, the FAQPage deprecation is repeated in three places, and the keyword-research steps carry narrative padding (risoto/carne storytelling, "peça a um amigo imparcial") that could be tightened. | 3 / 5 |
Actionability | Fully executable, copy-paste-ready guidance throughout: complete generateMetadata, JSON-LD, OptimizedImage, next/font, dynamic-import and next/script code, hreflang HTML, robots.txt and llms.txt templates, the KEI formula with a worked numeric example, and a concrete keyword output table covering the common cases. | 5 / 5 |
Workflow Clarity | The 7-step keyword-research workflow is clearly sequenced with coverage validation via the fan-out sub-question mapper, the Core Web Vitals section has an explicit fix-and-re-measure feedback loop, the audit path defines fallback behavior when /seo is unavailable, and the QA handoff plus multiple checklists provide explicit verification steps. | 5 / 5 |
Progressive Disclosure | Both bundle references (references/keyword-research.md, references/claude-seo.md) are real, one level deep, and clearly signaled with explicit open-only-when conditions, but the ~700-line body inlines several large self-contained sections (GEO/AEO, local, e-commerce, international) that would fit better as split reference files. | 4 / 5 |
Total | 17 / 20 Passed |