create-site
This skill should be used when the user asks to "create a power pages site", "build a code site", "scaffold a website", "create a portal", "make a new site", or wants to create a new Power Pages code site (SPA) using React, Angular, Vue, or Astro.
Install with Tessl CLI
npx tessl i github:microsoft/power-platform-skills --skill create-site77
Quality
74%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/power-pages/skills/create-site/SKILL.mdQuality
Discovery
72%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 distinctiveness, making it easy for Claude to identify when to use this skill. However, it's structured backwards - leading with 'when' rather than 'what' - and lacks specific capability details about what actions the skill actually performs beyond creating sites.
Suggestions
Restructure to lead with capabilities: 'Scaffolds Power Pages code sites (SPAs) using React, Angular, Vue, or Astro. Configures project structure, routing, and build setup.'
Add specific actions the skill performs, such as 'generates boilerplate', 'sets up authentication', 'configures deployment', or similar concrete capabilities.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Power Pages code site/SPA) and mentions frameworks (React, Angular, Vue, Astro), but doesn't list specific concrete actions like 'scaffold components', 'configure routing', or 'set up build pipeline'. | 2 / 3 |
Completeness | Strong on 'when' with explicit trigger phrases, but weak on 'what' - it only says it creates Power Pages code sites without explaining what capabilities or actions the skill provides beyond site creation. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'create a power pages site', 'build a code site', 'scaffold a website', 'create a portal', 'make a new site', plus framework names that users would mention. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche targeting Power Pages specifically with SPA frameworks. The combination of 'Power Pages' + 'code site' + specific framework names creates clear differentiation from generic website or scaffolding skills. | 3 / 3 |
Total | 10 / 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 including explicit gates, validation checkpoints, and git-based error recovery. The main weaknesses are verbosity (repeated instructions about screenshots, scaffold replacement explained multiple times) and the monolithic length that could benefit from splitting some content into reference files. The actionability is exemplary with concrete commands, specific tool calls, and a complete example workflow.
Suggestions
Consolidate repeated instructions (e.g., 'do NOT take screenshots' appears 5+ times) into a single 'Verification Guidelines' section referenced throughout
Move the detailed 'Example Workflow' section to a separate reference file to reduce main skill length
Remove redundant explanations of scaffold replacement concept - state it once clearly in Phase 2 and reference that explanation in Phase 5
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but verbose in places, with some redundant explanations (e.g., repeated reminders about Playwright verification, multiple restatements of 'do NOT take screenshots'). The scaffold replacement concept is explained multiple times across phases. However, it avoids explaining basic concepts Claude knows. | 2 / 3 |
Actionability | Highly actionable with specific commands (`npm install`, `git init`, `git add -A`), exact file paths, concrete table formats for user questions, and clear tool invocations (`mcp__plugin_power-pages_playwright__browser_navigate`). The example workflow demonstrates end-to-end execution. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with 7 clearly sequenced phases, explicit gates (e.g., 'GATE: Do NOT proceed to Phase 3 until ALL of the following are true'), validation checkpoints via Playwright after each change, and git commit checkpoints for error recovery. Feedback loops are well-defined. | 3 / 3 |
Progressive Disclosure | References external files appropriately (`design-aesthetics.md`, `framework-conventions.md`, `skill-tracking-reference.md`) with one-level-deep navigation. However, the main skill file is quite long (~400 lines) and some content (like the detailed example workflow) could potentially be split out. The structure is good but the monolithic length reduces discoverability. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (506 lines); consider splitting into references/ and linking | Warning |
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 | 8 / 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.