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.

Quality

83%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

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 when the skill should be used. Its main weakness is that it focuses heavily on listing trigger phrases rather than concretely describing the specific actions the skill performs. The description could be improved by leading with explicit capability statements before the trigger list.

Suggestions

Lead with concrete action statements like 'Generates robots.txt, creates sitemap.xml, inserts meta tags and Open Graph tags into HTML head, and adds favicon references to Power Pages sites' before listing trigger terms.

Rewrite in third person active voice (e.g., 'Adds SEO essentials to Power Pages sites') rather than the current 'This skill should be used when...' framing to improve specificity.

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. The combination of SEO-specific triggers and the Power Pages context makes it very 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 sequencing and good validation checkpoints. Its main weakness is length — at ~250 lines it's verbose for what could be a more concise skill, with some structural repetition (Goal/Actions/Output per phase) and inline templates that could be referenced externally. The actionability and workflow clarity are strong, with concrete code examples and explicit decision points throughout.

Suggestions

Consider moving the detailed HTML/XML/SVG templates into a reference file (e.g., seo-templates.md) and referencing them from the main skill to reduce token footprint.

Remove the repeated 'Output' subsections at the end of each phase — these largely restate what the Actions section already makes clear and add ~30 lines of redundancy.

Dimension	Reasoning	Score
Conciseness	The skill is fairly well-structured but verbose for what it accomplishes. The phase-by-phase breakdown with repeated 'Goal', 'Actions', 'Output' sections adds structural overhead. Some content like the Core Principles section and the detailed AskUserQuestion table formats could be tightened. However, it avoids explaining basic concepts Claude already knows (SEO fundamentals, what robots.txt is, etc.).	2 / 3
Actionability	The skill provides concrete, executable code examples throughout — PowerShell commands for file discovery, exact robots.txt content, complete sitemap.xml templates, full HTML meta tag blocks, SVG favicon code, and specific git commands. Placeholder variables are clearly marked and the templates are copy-paste ready with substitution.	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 powerpages.config.json not found, if Playwright verification fails). Feedback loops are present for the approval phase and verification phase.	3 / 3
Progressive Disclosure	The skill references external files appropriately (framework-conventions.md, skill-tracking-reference.md) but the main content is quite long and monolithic. The detailed HTML templates, XML examples, and SVG code could potentially be split into reference files. However, the inline content is well-organized with clear headers and the references that exist are one-level deep and clearly signaled.	2 / 3
	Total	10 / 12 Passed

Validation

81%

Warnings & errors only

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: 66a61c6

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.