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".
80
75%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/14-seo-specialist/SKILL.mdQuality
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 via 'Use quando' and 'Trigger em' clauses, and comprehensive natural keywords. The description uses third person voice appropriately and provides enough detail to distinguish it from related skills like general web development or performance optimization. Minor note: it's in Portuguese, but the structure and content quality are excellent.
| 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, ou qualquer decisão de ranqueamento.' These are concrete, specific SEO optimization tasks. | 3 / 3 |
Completeness | Clearly answers both 'what' (otimização de páginas e sistemas para motores de busca, with specific tasks listed) and 'when' (explicit 'Use quando precisar...' clause and a 'Trigger em:' section with specific keywords). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms explicitly listed: 'SEO', 'meta tags', 'Open Graph', 'sitemap', 'schema markup', 'Core Web Vitals', 'performance', 'LCP', 'CLS', 'ranking', 'canonical', 'robots.txt'. These are terms users would naturally use when needing SEO help. | 3 / 3 |
Distinctiveness Conflict Risk | SEO optimization is a clear, distinct niche. The specific trigger terms like 'schema markup', 'Core Web Vitals', 'LCP', 'CLS', 'canonical', 'robots.txt' are highly specific to SEO and unlikely to conflict with other skills such as general web development or content writing. | 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 in actionability with complete, executable Next.js code examples covering meta tags, schema markup, images, fonts, and performance optimizations. However, it is significantly too verbose — it explains concepts Claude already knows (semantic HTML, what Core Web Vitals metrics mean), includes large code blocks that should be in referenced files, and has boilerplate sections that don't add value. The workflow could benefit from explicit validation sequences rather than just checklists.
Suggestions
Move the full code examples (schema components, OptimizedImage, ThirdPartyScripts) to a referenced file like 'docs/skill-guides/seo-specialist.md' and keep only the most essential template (generateMetadata) inline with pointers to the rest.
Remove explanatory content Claude already knows: the Core Web Vitals description column, the semantic HTML correct/incorrect reference table, and the 'Responsabilidades' list which just restates what the code examples already demonstrate.
Add an explicit validation workflow: e.g., '1. Implement changes → 2. Run Lighthouse audit → 3. If score < 90, identify failing metrics → 4. Fix and re-audit → 5. Validate schema at Google Rich Results Test → 6. Only then hand off to QA'.
Remove boilerplate sections (Entradas Esperadas, Saidas Esperadas, Evidencia de Conclusao) that don't provide actionable guidance and consume tokens without adding value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~300+ lines. It explains concepts Claude already knows (what LCP/CLS/FID are, what semantic HTML is, correct vs incorrect HTML tags), includes boilerplate sections like 'Quando Usar/Nao Usar', 'Entradas Esperadas/Saidas Esperadas' that add little actionable value, and repeats information that could be referenced from external docs. The HTML semantic reference table and Core Web Vitals descriptions are unnecessary for Claude. | 1 / 3 |
Actionability | The skill provides fully executable, copy-paste ready TypeScript/JavaScript code examples for meta tags, schema markup, optimized images, fonts, lazy loading, and third-party scripts. All code is concrete, complete, and framework-specific (Next.js), with specific file paths indicated. | 3 / 3 |
Workflow Clarity | The skill provides checklists and handoff processes, but lacks explicit validation steps and feedback loops. For example, there's no step-by-step workflow for 'run Lighthouse → check scores → fix issues → re-run'. The checklist is comprehensive but doesn't sequence the work or include verification checkpoints between steps. | 2 / 3 |
Progressive Disclosure | The skill references external docs ('docs/skill-guides/seo-specialist.md') and policies, which is good. However, the main file is monolithic with extensive inline code and reference tables that should be in separate files. The schema markup section alone has three full component implementations that could be referenced externally. | 2 / 3 |
Total | 8 / 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.
d87ad31
Table of Contents
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.