deploy-site

Deploys an existing Power Pages code site to a Power Pages environment using PAC CLI. Handles tooling verification, authentication, environment confirmation, building, and uploading. Use when the user wants to deploy, upload, or publish their code site.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

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 well-structured, highly actionable deployment workflow with explicit sequencing, validation checkpoints, and consent gates. Its main weakness is conciseness: an inline ~150-extension blockedattachments list and partially duplicated notes pad the body, and the bundle files it points to are not verifiable from this workspace.

Suggestions

Move the full blockedattachments extension list out of the body (e.g., into a reference file or have the skill parse it from `pac env list-settings` output) to reclaim tokens; a short illustrative example plus 'parse the semicolon-separated value' is sufficient.

Trim the 'Important Notes' and 'Key Decision Points' sections that restate what the phases already specify, or keep only the unique guidance (e.g., the NEVER `pac pages upload` rule) to reduce duplication.

Confirm the referenced bundle files (skill-tracking-reference.md, check-activation-status.js, clear-site-cache.js, check-version.js) exist under PLUGIN_ROOT so the one-level-deep references are verifiable, which would let progressive_disclosure reach its top anchor.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and action-oriented, but the 486-line body includes padded material that does not earn its place — the giant verbatim blockedattachments extension list (~150 extensions) is reproduced inline, and 'Important Notes'/'Key Decision Points' duplicate content already covered in the phases, which could be tightened.	2 / 3
Actionability	Commands are concrete and copy-paste ready throughout (`pac help`, `pac auth create --environment ...`, `pac pages upload-code-site --rootPath ...`, `pac env update-settings ...`), with explicit branching on success/failure and a sharp, executable troubleshooting fix for the misleading HTML-block error.	3 / 3
Workflow Clarity	A clear six-phase sequence with explicit validation checkpoints (re-run `pac auth who`, re-run `pac help`, verify switch, evaluate upload/activation JSON), feedback loops (build fails → fix → retry; upload fails → route to Phase 6 or troubleshooting → retry), and consent gates, matching the top anchor.	3 / 3
Progressive Disclosure	Structure is well sectioned and references one level deep (`${PLUGIN_ROOT}/references/skill-tracking-reference.md`, several `${PLUGIN_ROOT}/scripts/*.js`), but the workspace has no references/scripts/assets bundle present to verify against, and a substantial chunk that could live separately (the inline blockedattachments list and duplicate notes) is kept inline rather than split out.	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 description: concrete actions, a clear narrow domain (Power Pages code site deployment via PAC CLI), and an explicit 'Use when' trigger clause. It answers both what and when without verbosity or buzzwords.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'tooling verification, authentication, environment confirmation, building, and uploading' — tied to a concrete domain (Power Pages code site via PAC CLI), matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers 'what' (deploys a code site via PAC CLI with the listed sub-tasks) AND 'when' via an explicit 'Use when the user wants to deploy, upload, or publish their code site' clause, satisfying the top anchor for both what and when.	3 / 3
Trigger Term Quality	Natural trigger phrasing 'Use when the user wants to deploy, upload, or publish their code site' uses the words users would actually say (deploy, upload, publish), giving good coverage of natural terms.	3 / 3
Distinctiveness Conflict Risk	The niche is narrow and specific — Power Pages code sites via PAC CLI — with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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 — 14 / 16 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	14 / 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.