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

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/power-pages/skills/deploy-site/SKILL.md

Quality

Content

72%Weight 40%Scale 1-5

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

The skill is highly actionable and workflow-clarity is excellent with validation checkpoints and consent gates. The main weakness is progressive disclosure: the body references scripts and reference files that are not present in the bundle, breaking navigation and leaving dependent instructions unverifiable.

Suggestions

Include the referenced bundle files (scripts/check-version.js, scripts/check-activation-status.js, scripts/clear-site-cache.js, references/skill-tracking-reference.md) or remove the references so readers are not sent to missing paths.

Move the long blocked-extensions enumeration in Phase 6.3 into a reference file and keep only the parse-filter-rejoin instruction inline to improve token efficiency.

Tighten repeated 'Output:' summaries and verbose gate blockquotes, which restate information already covered in the preceding actions.

Dimension	Reasoning	Score
Conciseness	Mostly efficient phase-based structure, but the long blocked-extensions list, repeated 'Output' lines, and verbose gate callouts add padding that could be tightened without losing clarity.	3 / 5
Actionability	Fully executable guidance throughout: concrete bash commands (pac auth create, pac pages upload-code-site, pac env update-settings) with placeholders, exact AskUserQuestion tables, and specific scripts to invoke.	5 / 5
Workflow Clarity	Six phases are explicitly sequenced with clear validation checkpoints (pac help, pac auth who verification, build-fail handling, upload retry loops), and destructive operations are gated behind explicit consent with documented cancel-state semantics.	5 / 5
Progressive Disclosure	The body relies on several bundle paths (scripts/check-version.js, references/skill-tracking-reference.md, scripts/check-activation-status.js, scripts/clear-site-cache.js) but the references/, scripts/, and assets/ directories do not exist in the bundle, so the referenced files cannot be located or navigated to.	2 / 5
	Total	15 / 20 Passed

Description

86%Weight 40%Scale 1-5

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 explicitly answers both what and when with concrete actions and natural trigger terms. Minor room for improvement in adding synonyms or extension-style keywords.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('tooling verification, authentication, environment confirmations, building, and uploading') tied to a specific tool (PAC CLI), with only minor coverage gaps.	4 / 5
Completeness	Clearly states both what it does ('Deploys an existing Power Pages code site... Handles tooling verification, authentication... building, and uploading') and when to use it ('Use when the user wants to deploy, upload, or publish their code site').	5 / 5
Trigger Term Quality	Good natural keyword coverage ('deploy, upload, or publish their code site') that users would plausibly say, though it lacks common synonyms or file-extension variants.	4 / 5
Distinctiveness Conflict Risk	Narrowly scoped to Power Pages code sites via PAC CLI with distinct trigger verbs, making conflict with other skills minimal.	5 / 5
	Total	18 / 20 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
Path: plugins/power-pages/skills/deploy-site/SKILL.md
Commit: 4c284ab

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