add-seo
This skill should be used when the user asks to "add SEO", "add meta tags", "add robots.txt", "add sitemap", "improve SEO", "search engine optimization", "add open graph tags", "add favicon", "make site searchable", or wants to add SEO essentials (robots.txt, sitemap.xml, meta tags) to their Power Pages code site after creating it with /create-site.
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%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 description excels at trigger term coverage and completeness, providing an extensive list of natural user phrases and clearly stating both what the skill does and when to use it. Its main weakness is that the 'what' portion could be more specific about the concrete actions performed rather than just listing the artifacts. The description is functional and effective for skill selection despite being somewhat list-heavy in structure.
Suggestions
Replace the implied capabilities with explicit action verbs, e.g., 'Generates robots.txt, creates sitemap.xml, inserts meta tags and Open Graph tags into HTML head, and adds favicon references to Power Pages sites.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description mentions specific artifacts like robots.txt, sitemap.xml, meta tags, open graph tags, and favicon, but it doesn't clearly list the concrete actions performed (e.g., 'generates robots.txt', 'creates sitemap.xml', 'inserts meta tags into HTML'). The actions are implied rather than explicitly stated. | 2 / 3 |
Completeness | The description explicitly answers both 'what' (adds SEO essentials like robots.txt, sitemap.xml, meta tags to Power Pages sites) and 'when' (with a comprehensive list of trigger phrases starting with 'This skill should be used when...'). The 'when' guidance is very explicit. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'add SEO', 'add meta tags', 'add robots.txt', 'add sitemap', 'improve SEO', 'search engine optimization', 'add open graph tags', 'add favicon', 'make site searchable'. These are highly natural phrases a user would actually type. | 3 / 3 |
Distinctiveness Conflict Risk | The description is highly specific to SEO for Power Pages code sites created with /create-site, which is a very clear niche. The combination of SEO-specific terms and the Power Pages context makes it unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%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 clear workflow phases, explicit validation checkpoints, and concrete file templates. Its main weakness is verbosity — the detailed templates and repeated output sections make it longer than necessary, and some content (like basic robots.txt format) is knowledge Claude already possesses. The progressive disclosure could be improved by extracting some templates to reference files.
Suggestions
Trim the robots.txt and sitemap.xml template examples — Claude knows these formats; a brief specification of the rules (priority assignments, exclusion handling) without full XML/text blocks would suffice.
Remove the 'Output' subsections at the end of each phase — they restate what the actions already describe and add ~30 lines of redundant content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly well-structured but verbose for what it accomplishes. The robots.txt and sitemap.xml templates are straightforward content Claude could generate without detailed examples. The repeated 'Output' sections at the end of each phase and the extensive tables add bulk. However, the framework-specific guidance and decision points do earn their place. | 2 / 3 |
Actionability | The skill provides fully concrete, executable guidance throughout: specific file paths, complete file content templates (robots.txt, sitemap.xml, meta tags, favicon SVG), exact PowerShell commands, git commit commands, and specific AskUserQuestion configurations with options. Everything is copy-paste ready with clear placeholder conventions. | 3 / 3 |
Workflow Clarity | The 7-phase workflow is clearly sequenced with explicit validation checkpoints: Phase 3 requires user approval before implementation, Phase 7.2 includes Playwright verification before committing, and the Key Decision Points section provides clear stop/fix conditions (e.g., if Playwright verification fails, diagnose before committing). Feedback loops are present where needed. | 3 / 3 |
Progressive Disclosure | The skill references external files appropriately (framework-conventions.md, skill-tracking-reference.md) but the main body is quite long (~250 lines of content) with detailed templates that could potentially be extracted. The inline robots.txt, sitemap.xml, meta tag, and favicon templates make the document lengthy, though they are arguably necessary for actionability. | 2 / 3 |
Total | 10 / 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 — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- microsoft/power-platform-skills
- Commit
1132a35
- 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.