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.
71
88%
Does it follow best practices?
Impact
—
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 SEO-related actions for Power Pages sites, includes natural trigger terms users would use, and provides an explicit 'Use when' clause. The description is concise yet comprehensive, with a well-defined niche that minimizes conflict risk with other skills.
| 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 deliverables. | 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 due to the specific combination of 'Power Pages code site' and SEO-specific artifacts. The scope is narrow and well-defined, making it unlikely to conflict with general web development or other CMS 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 workflow sequencing and proper validation checkpoints. Its main weakness is verbosity — the content could be tightened by removing explanatory text Claude doesn't need (core principles, repeated output summaries) and potentially moving templates to reference files. The concrete code templates and explicit user interaction points are strong.
Suggestions
Remove the 'Core Principles' section — Claude already understands SEO fundamentals, and these principles are implicitly enforced by the workflow steps themselves.
Remove the per-phase 'Output' bullet lists — they restate what the actions already describe and add token overhead without new information.
Consider moving the HTML/XML templates (robots.txt, sitemap.xml, meta tags, favicon SVG) into a reference file to reduce the main skill's length while keeping the workflow steps lean.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly well-structured but verbose for what it accomplishes. The tables for AskUserQuestion calls, the repeated 'Output' sections at the end of each phase, and the 'Important Notes' section at the bottom largely restate what was already covered in the workflow. The core principles section explains things Claude already understands (e.g., 'misleading metadata harms rankings'). However, the concrete code examples and templates earn their place. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste-ready templates for robots.txt, sitemap.xml, meta tags, Open Graph tags, favicon SVG, and git commands. Each phase has concrete actions with specific file paths, exact HTML/XML content, and clear variable placeholders. The AskUserQuestion calls are specified with exact question text and options. | 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/redirect conditions. The feedback loop for plan revision (Phase 3) and Playwright failure diagnosis (Phase 7.2) are explicitly stated. | 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 all implementation details inline. The phase-by-phase structure provides some organization, but the meta tag templates, sitemap templates, and robots.txt templates could potentially be in reference files to keep the main skill leaner. | 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
b4c46e9
- 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.