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 /power-pages:create-site.
Install with Tessl CLI
npx tessl i github:microsoft/power-platform-skills --skill add-seo85
Quality
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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 explicit 'Use when' guidance with numerous natural phrases users would say. The main weakness is that it focuses heavily on when to use the skill but could be more specific about the concrete actions performed (e.g., 'generates robots.txt', 'creates sitemap.xml'). The Power Pages context makes it highly distinctive.
Suggestions
Reframe to lead with concrete actions: 'Generates robots.txt, sitemap.xml, meta tags, and Open Graph tags for Power Pages sites' rather than starting with trigger conditions.
Use active verbs to describe capabilities: 'Creates SEO essentials including...' rather than 'add SEO essentials'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (SEO for Power Pages) and mentions specific deliverables (robots.txt, sitemap.xml, meta tags, open graph tags, favicon), but doesn't describe concrete actions like 'generates', 'creates', or 'configures'. | 2 / 3 |
Completeness | Explicitly answers both 'when' (opens with 'This skill should be used when...') and 'what' (add SEO essentials including robots.txt, sitemap.xml, meta tags to Power Pages sites). The trigger guidance is clear and comprehensive. | 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'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: SEO specifically for Power Pages code sites, with explicit reference to the prerequisite skill '/power-pages:create-site'. Unlikely to conflict with generic SEO or other CMS 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 excellent workflow clarity and validation checkpoints. The multi-phase approach with explicit approval gates and Playwright verification demonstrates good practice for complex operations. However, it could be more concise by removing explanations of concepts Claude already knows and potentially splitting detailed phase content into reference files.
Suggestions
Remove explanatory text about what robots.txt and sitemap.xml are for - Claude already knows these concepts
Consider moving the detailed XML/HTML templates to a separate reference file to reduce the main skill's length while keeping the workflow clear
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary verbosity, such as explaining what robots.txt and sitemap.xml do (Claude knows this), and repeating file paths multiple times across phases. The core principles section adds value but could be more concise. | 2 / 3 |
Actionability | Provides fully executable code examples for PowerShell commands, robots.txt content, sitemap.xml structure, HTML meta tags, and SVG favicon. All examples are copy-paste ready with clear placeholders for dynamic values. | 3 / 3 |
Workflow Clarity | Excellent multi-phase workflow with explicit validation checkpoints (Phase 3 approval gate, Phase 7.2 Playwright verification before commit). Clear sequencing with numbered phases and sub-steps, plus explicit decision points documented at the end. | 3 / 3 |
Progressive Disclosure | References external files appropriately (framework-conventions.md, skill-tracking-reference.md), but the skill itself is quite long with detailed inline content that could potentially be split. The structure is good but the monolithic nature of 7 detailed phases in one file reduces discoverability. | 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 | |
- 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.