add-seo
Adds SEO essentials to a Power Pages code site, including robots.txt, sitemap.xml, meta tags, Open Graph tags, and favicon configuration. Use when the user wants to improve search engine optimization or make their site more searchable.
89
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
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 articulates specific capabilities (robots.txt, sitemap.xml, meta tags, Open Graph tags, favicon), scopes them to a particular platform (Power Pages), and includes an explicit 'Use when' trigger clause. It uses third person voice correctly and provides both technical trigger terms and natural language equivalents.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: robots.txt, sitemap.xml, meta tags, Open Graph tags, and favicon configuration. These are clearly defined, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (adds SEO essentials including robots.txt, sitemap.xml, meta tags, Open Graph tags, favicon configuration) and 'when' (explicit 'Use when' clause specifying improving SEO or making site more searchable). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'SEO', 'search engine optimization', 'searchable', 'robots.txt', 'sitemap.xml', 'meta tags', 'Open Graph tags', 'favicon', and 'Power Pages'. Good coverage of both technical and natural language terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive by scoping to 'Power Pages code site' and specific SEO artifacts. The combination of platform (Power Pages) and domain (SEO essentials) creates a clear niche unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 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 multi-step workflow and proper validation checkpoints. Its main weakness is length — the detailed templates and repeated section structure (Goal/Actions/Output for each phase) make it verbose, though most content earns its place. The progressive disclosure could be improved by offloading some template content to reference files, and the Core Principles section adds little value for Claude.
Suggestions
Remove or significantly trim the 'Core Principles' section — Claude doesn't need to be told that misleading metadata harms rankings or that crawlability matters.
Consider moving the detailed HTML/XML templates (sitemap.xml, meta tags, favicon SVG) into a reference file to reduce the main skill's token footprint while keeping the workflow steps lean.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-structured but includes some unnecessary verbosity — the Core Principles section explains SEO concepts Claude already knows (e.g., 'misleading metadata harms rankings'), and the AskUserQuestion tables add bulk that could be more compact. The phase-by-phase structure is somewhat repetitive with 'Goal' and 'Output' sections for each phase. | 2 / 3 |
Actionability | The skill provides fully concrete, executable guidance throughout: specific file paths, complete code templates for robots.txt, sitemap.xml, meta tags, favicon SVG, and git commands. Placeholder variables are clearly marked and the instructions are copy-paste ready with appropriate framework-specific variations noted. | 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. Feedback loops are present (e.g., if Playwright verification fails, diagnose and fix before committing; if user wants changes to plan, revise and re-present). | 3 / 3 |
Progressive Disclosure | The skill references external files like `framework-conventions.md` and `skill-tracking-reference.md` appropriately, but the main SKILL.md itself is quite long (~250 lines of content) with detailed templates that could potentially be split into reference files. However, no bundle files were provided to verify the referenced paths exist, and the inline content is borderline for what should remain in the main file vs. be referenced. | 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
48e49c4
- 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.