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

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

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 what the skill does (creates Power Pages SPA sites with specific frameworks through a defined process), when to use it (explicit 'Use when' clause with natural trigger terms), and occupies a distinct niche. The description is well-structured, uses third person voice, and provides comprehensive trigger coverage without being verbose.

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. This is 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

Implementation

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 excellent workflow clarity, explicit gates, and validation checkpoints at every critical juncture. However, it is severely over-verbose — repeating instructions across phases, over-explaining simple concepts (git commands, JSON file writes, npm install), and inlining content that should be in reference files. The token cost is very high relative to the unique information density.

Suggestions

Extract the Live Preview Status Protocol into a separate reference file and replace the inline section with a one-line pointer — the protocol is repeated/referenced 5+ times across phases, inflating the document significantly.

Move the Example Workflow section to a separate reference file (e.g., references/create-site-example.md) — it adds ~80 lines that duplicate the phase descriptions already given.

Remove explanations of basic operations Claude already knows (e.g., how to run `git init`, `npm install`, `git add -A && git commit`, how JSON files work) and reduce to just the specific commands/values needed.

Consolidate repeated instructions — for instance, 'update scaffold-status.json before AskUserQuestion' and 'verify via browser_snapshot not screenshot' are each stated 4-5 times; state once in Core Principles and reference that.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~600+ lines. Extensively explains mechanics Claude already understands (how to run git commands, how to use npm, what CSS variables are, how to write JSON). Many sections repeat instructions already stated elsewhere (e.g., the Live Preview Status Protocol is explained in detail, then re-explained in Phase 3, Phase 4, and Phase 5). The scaffold-status.json protocol alone consumes enormous token budget with repetitive examples.	1 / 3
Actionability	Highly actionable with specific bash commands, exact file paths, concrete JSON schemas, specific tool names (mcp__plugin_power-pages_playwright__browser_navigate), exact AskUserQuestion table formats, and executable code blocks. Every phase has clear, copy-paste-ready instructions with specific parameters.	3 / 3
Workflow Clarity	Excellent multi-step workflow with explicit gates (e.g., 'GATE: Do NOT proceed to Phase 6 until...'), clear sequencing across 8 phases, validation checkpoints (Playwright verification after each change, axe-core re-run loops), error recovery (git revert instructions), and feedback loops (fix → re-verify → repeat until passing). Destructive operations are guarded.	3 / 3
Progressive Disclosure	References external files appropriately (design-aesthetics.md, framework-conventions.md, skill-tracking-reference.md, template assets), but the SKILL.md itself is a monolithic wall of text. The Live Preview Status Protocol, the full example workflow, and extensive implementation details could be split into separate reference files. Inline content is far too long for a single skill file.	2 / 3
	Total	9 / 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 (717 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: 48e49c4

Reviewed: 3 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.