create-site

Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new Power Pages website or portal.

Quality

81%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

62%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is exceptionally thorough and actionable with a well-structured 8-phase workflow, explicit validation gates, and concrete commands throughout. However, it is severely over-engineered for a SKILL.md — at 800+ lines it reads more like a full technical specification than a concise skill instruction. The content repeats itself frequently (screenshot warnings, commit instructions, status file updates) and includes extensive explanatory prose that Claude doesn't need, consuming significant context window budget.

Suggestions

Reduce the document by 50-60% by extracting detailed phase instructions into separate reference files (e.g., references/phase-2-scaffold.md, references/live-status-protocol.md) and keeping only summaries and key commands in SKILL.md.

Remove repeated instructions — consolidate 'do NOT take screenshots', commit patterns, and status file update instructions into a single 'Conventions' section referenced once.

Remove the gate annotation blocks (trigger/why/cancel-leaves) which add ~100 lines of metadata that Claude can infer from the workflow structure itself.

Move the Example Workflow section to a separate reference file or remove it entirely — it duplicates the phase instructions without adding new information.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~800+ lines. Extensively explains protocols Claude could infer (e.g., the entire Live Preview Status Protocol section, detailed explanations of what scaffold loaders do, repeated instructions about browser_snapshot vs screenshots). Many sections repeat the same instructions multiple times (e.g., 'do NOT take screenshots' appears 4+ times, commit instructions repeated in multiple phases). Gate annotations with trigger/why/cancel-leaves metadata add significant overhead.	1 / 3
Actionability	Highly actionable with specific bash commands, exact file paths, concrete JSON schemas, detailed table structures for AskUserQuestion prompts, specific tool names (mcp__plugin_power-pages_playwright__browser_navigate), and executable code examples. Every phase has clear, copy-paste-ready commands and precise file operations.	3 / 3
Workflow Clarity	Excellent multi-step workflow with 8 clearly sequenced phases, explicit gates between phases with specific conditions that must be met, validation checkpoints (axe-core audit with re-run loop), feedback loops (fix → re-verify → continue), and clear error recovery paths (git revert). The Phase 6 accessibility verification is a textbook example of validate → fix → retry.	3 / 3
Progressive Disclosure	References external files appropriately (design-aesthetics.md, framework-conventions.md, approval-gates.md, skill-tracking-reference.md), but the SKILL.md itself is monolithic — the entire 800+ line implementation guide is inline rather than splitting detailed phase instructions into separate reference files. The example workflow at the end duplicates information already covered in the phases. Without bundle files provided, we can't verify the referenced paths exist, but the structure would benefit from moving phase details into sub-files.	2 / 3
	Total	9 / 12 Passed

Description

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 communicates what the skill does, which frameworks it supports, the full workflow it covers, and when it should be triggered. It uses third person voice correctly, includes natural trigger terms, and occupies a distinct niche that minimizes conflict with other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: creating a new Power Pages code site (SPA), using specific frameworks (React, Angular, Vue, Astro), and enumerates the full process steps (requirements discovery, scaffolding, component planning, design, implementation, validation, deployment).	3 / 3
Completeness	Clearly answers both 'what' (creates a new Power Pages code site using specific frameworks, guiding through the full process) and 'when' (explicit 'Use when the user wants to create, build, or scaffold a new Power Pages website or portal').	3 / 3
Trigger Term Quality	Includes strong natural trigger terms users would say: 'Power Pages', 'create', 'build', 'scaffold', 'website', 'portal', 'SPA', 'React', 'Angular', 'Vue', 'Astro'. These cover common variations of how users would phrase requests for this task.	3 / 3
Distinctiveness Conflict Risk	The combination of 'Power Pages' with 'code site (SPA)' and specific framework names creates a very distinct niche. It's unlikely to conflict with general web development skills or other CMS-related skills due to the Power Pages specificity.	3 / 3
	Total	12 / 12 Passed

Validation

72%

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 — 8 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (815 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

Repository: microsoft/power-platform-skills
Commit: 180ed78

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.