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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

77%

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

A highly actionable, well-sequenced multi-phase workflow with strong validation feedback loops. Its main weakness is conciseness: significant cross-phase repetition and a monolithic body with sections that could be split into references.

Suggestions

Deduplicate guidance repeated across phases (no-screenshots rule, commit cadence, design-reference reads) by stating each once in Core Principles and referencing it from phases.

Move the full Live Preview Status Protocol into a references file and keep a one-paragraph summary plus the JSON shape in SKILL.md to reduce body length.

Replace the Example Workflow section with a brief pointer or drop it, since it restates the eight phases already detailed above.

Dimension	Reasoning	Score
Conciseness	Content is operational rather than generic, but there is notable duplication — the "no screenshots" rule, commit guidance, and design-reference reads each repeat across phases, and the "Important Notes" and "Example Workflow" sections restate the phase content — so it could be tightened rather than earning a 3.	2 / 3
Actionability	Provides copy-paste-ready bash (npm install, git init, npm run dev), exact script invocations with full paths, named MCP tools, AskUserQuestion option tables, JSON file shapes, and per-framework marker syntax — fully executable guidance.	3 / 3
Workflow Clarity	Eight clearly sequenced phases with explicit GATE checkpoints and a validate→fix→re-run feedback loop (axe-core audit re-run until exit code 0, Playwright snapshot after each change), matching the score-3 anchor.	3 / 3
Progressive Disclosure	Real, well-signaled one-level-deep references exist (references/design-aesthetics.md, scripts/axe-audit.js, asset templates), but the 815-line body is monolithic with the full Live Preview Status Protocol and Example Workflow inline that could be externalized, so it does not fully meet the score-3 "content appropriately split" bar.	2 / 3
	Total	10 / 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.

A strong, third-person description that concisely states concrete capabilities, supported frameworks, and an explicit Use-when trigger clause. It satisfies every dimension without padding or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment") and names the specific supported frameworks (React, Angular, Vue, Astro), matching the score-3 anchor.	3 / 3
Completeness	Explicitly answers both what (creates a Power Pages code site, guides the full process) and when ("Use when the user wants to create, build, or scaffold a new Power Pages website or portal"), satisfying the score-3 anchor.	3 / 3
Trigger Term Quality	Natural user-facing verbs and nouns appear ("create, build, or scaffold a new Power Pages website or portal") — terms a user would actually say; not a 2 because coverage includes create/build/scaffold plus website/portal variations.	3 / 3
Distinctiveness Conflict Risk	The Power Pages code-site niche with framework-specific triggers is clearly distinct from generic web skills and unlikely to fire for the wrong skill.	3 / 3
	Total	12 / 12 Passed

Validation

75%

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 — 12 / 16 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
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	12 / 16 Passed

Repository: microsoft/power-platform-skills
Commit: 55fa377

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.