seo-geo
SEO & GEO (Generative Engine Optimization) for websites. Analyze keywords, generate schema markup, optimize for AI search engines (ChatGPT, Perplexity, Gemini, Copilot, Claude) and traditional search (Google, Bing). Use when user wants to improve search visibility.
Overall
score
91%
Does it follow best practices?
Validation for skill structure
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 purpose, lists specific capabilities, and includes an explicit 'Use when' trigger. It covers both traditional SEO and the emerging GEO space with concrete platform names, making it highly distinguishable and easy for Claude to select appropriately.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Analyze keywords, generate schema markup, optimize for AI search engines' with named platforms (ChatGPT, Perplexity, Gemini, Copilot, Claude) and traditional search engines (Google, Bing). | 3 / 3 |
Completeness | Clearly answers both what (analyze keywords, generate schema markup, optimize for search engines) AND when ('Use when user wants to improve search visibility') with an explicit trigger clause. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'SEO', 'GEO', 'keywords', 'schema markup', 'AI search engines', 'search visibility', plus specific platform names that users might mention when seeking optimization help. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on SEO/GEO optimization with distinct triggers around search visibility, schema markup, and named AI/traditional search platforms - unlikely to conflict with general web development or content skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill with excellent progressive disclosure and clear workflows. The content provides concrete, executable commands and templates throughout. Minor verbosity in explanatory sections and some definitions Claude already knows prevent a perfect conciseness score.
Suggestions
Remove the 'Key Insight' explanation and GEO definition - Claude understands these concepts and they consume tokens without adding value
Condense the platform-specific section by moving detailed explanations to the referenced platform-algorithms.md file, keeping only the most critical differentiators inline
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient with good use of tables and code blocks, but includes some unnecessary explanations (e.g., 'GEO = Generative Engine Optimization' definition, 'Key Insight' that Claude would understand). The platform-specific section could be more condensed. | 2 / 3 |
Actionability | Excellent executable guidance with concrete bash commands, complete JSON-LD templates, specific meta tag examples, and copy-paste ready code. The WebSearch queries and validation commands are immediately usable. | 3 / 3 |
Workflow Clarity | Clear 5-step workflow with explicit validation in Step 5 (schema validation, indexing checks). Each step has clear purpose annotations ('Use this for:'), and the final report template provides a verification checklist. | 3 / 3 |
Progressive Disclosure | Excellent structure with concise overview in main file and clear one-level-deep references to detailed materials (platform-algorithms.md, schema-templates.md, geo-research.md). References are well-signaled with descriptive labels. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
- 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.