seo-specialist

Skill do Especialista SEO para otimização de páginas e sistemas para motores de busca. Use quando precisar otimizar meta tags, Open Graph, sitemap, schema markup, Core Web Vitals, performance, imagens, fontes, acessibilidade para SEO, ou qualquer decisão de ranqueamento. Trigger em: "SEO", "meta tags", "Open Graph", "sitemap", "schema markup", "Core Web Vitals", "performance", "LCP", "CLS", "ranking", "canonical", "robots.txt".

Quality

75%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/14-seo-specialist/SKILL.md

Quality

Discovery

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong skill description that clearly defines its SEO optimization domain with specific capabilities, explicit trigger guidance, and a comprehensive list of natural keywords. It follows the recommended pattern of stating what it does, when to use it, and providing explicit trigger terms. The only minor note is that 'performance' alone could overlap with general web performance skills, but the SEO context sufficiently disambiguates it.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: otimizar meta tags, Open Graph, sitemap, schema markup, Core Web Vitals, performance, imagens, fontes, acessibilidade para SEO, decisão de ranqueamento.	3 / 3
Completeness	Clearly answers both 'what' (otimização de páginas e sistemas para motores de busca, with specific capabilities listed) and 'when' (explicit 'Use quando precisar...' clause plus a dedicated 'Trigger em:' list with specific keywords).	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms users would say, including both broad terms ('SEO', 'ranking', 'performance') and specific technical terms ('LCP', 'CLS', 'canonical', 'robots.txt', 'Open Graph', 'schema markup'). These are terms users would naturally use when requesting SEO help.	3 / 3
Distinctiveness Conflict Risk	SEO optimization is a clear, well-defined niche. The specific trigger terms like 'schema markup', 'Core Web Vitals', 'canonical', 'robots.txt' are highly distinctive and unlikely to conflict with other skills. There's minor overlap potential with general 'performance' but the SEO context makes it distinguishable.	3 / 3
	Total	12 / 12 Passed

Implementation

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill excels at actionability with complete, executable Next.js code examples covering meta tags, schema markup, images, fonts, and performance optimizations. However, it is far too verbose for a SKILL.md — most of the component code and reference tables should be in separate files with the main skill serving as a concise overview. The workflow lacks explicit validation steps and feedback loops between implementation stages.

Suggestions

Move full component implementations (OptimizedImage, schemas, ThirdPartyScripts) and the HTML semantic reference table to separate referenced files, keeping only a brief summary and links in SKILL.md

Remove sections that explain concepts Claude already knows (Core Web Vitals descriptions, what semantic HTML elements mean) and keep only the targets/rules

Add an explicit implementation workflow with validation checkpoints: e.g., 1) Implement meta tags → 2) Validate with Open Graph Debugger → 3) Add schema → 4) Validate with Rich Results Test → 5) Optimize performance → 6) Run Lighthouse, fix if <90 → 7) Handoff

Consolidate the boilerplate governance sections (Quando Usar, Entradas/Saidas, Governanca) into 2-3 lines maximum

Dimension	Reasoning	Score
Conciseness	The skill is extremely verbose at ~300+ lines. It includes extensive boilerplate sections (Quando Usar/Nao Usar, Entradas/Saidas Esperadas, Governanca) that add little actionable value. The HTML semantic reference table, full component implementations, and exhaustive checklists could be split into referenced files. Many concepts (semantic HTML, Core Web Vitals definitions) are things Claude already knows.	1 / 3
Actionability	The skill provides fully executable, copy-paste ready TypeScript/JavaScript code for meta tags, schema markup, optimized images, fonts, lazy loading, and third-party scripts. All code examples are complete components with proper imports and type definitions, specific to Next.js.	3 / 3
Workflow Clarity	The skill has checklists and a handoff section that sequences work between roles, but lacks explicit validation checkpoints within the implementation workflow. There's no step-by-step process for applying SEO optimizations with verification gates (e.g., validate schema markup before proceeding, run Lighthouse after changes). The checklist is a static list rather than a guided workflow with feedback loops.	2 / 3
Progressive Disclosure	The skill references `docs/skill-guides/seo-specialist.md` for detailed templates and several policy files, showing awareness of progressive disclosure. However, the massive amount of inline content (full component code, semantic HTML reference, exhaustive checklists) should be in referenced files rather than in the main SKILL.md. The overview is buried under implementation details.	2 / 3
	Total	8 / 12 Passed

Validation

100%

Warnings & errors only

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: felvieira/claude-skills-fv
Commit: e9f6648

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.