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.
89
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
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 identifies the specific technology (Power Pages, PAC CLI), lists concrete actions in the deployment pipeline, and provides explicit trigger guidance with natural user terms. It is well-scoped and distinctive, making it easy for Claude to select appropriately from a large skill set.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: tooling verification, authentication, environment confirmation, building, and uploading. Also specifies the tool (PAC CLI) and the target (Power Pages environment). | 3 / 3 |
Completeness | Clearly answers both 'what' (deploys Power Pages code site using PAC CLI, handles tooling verification, authentication, environment confirmation, building, uploading) and 'when' (explicit 'Use when the user wants to deploy, upload, or publish their code site'). | 3 / 3 |
Trigger Term Quality | Includes natural trigger terms users would say: 'deploy', 'upload', 'publish', 'code site', 'Power Pages'. These cover the common variations of how a user would phrase a deployment request. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche: Power Pages deployment via PAC CLI. The combination of 'Power Pages', 'PAC CLI', and 'code site' makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable deployment skill with excellent workflow clarity and explicit validation checkpoints at every phase. Its main weakness is length — at 350+ lines it's a substantial document that could benefit from splitting some sections (troubleshooting, Phase 6 error handling) into separate reference files. The concrete CLI commands, decision trees, and error handling paths make it very effective for guiding Claude through a complex multi-step deployment process.
Suggestions
Extract the 'Troubleshooting: HTML Blocked Attachment Error' section and Phase 6 'Handle Blocked JavaScript' into a separate troubleshooting reference file to reduce the main skill's token footprint.
Tighten Phase 6.1's explanation — Claude doesn't need the full context of why JS is blocked; a brief note like 'JS attachments are blocked by default in Power Pages environments' suffices.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite long (~350+ lines) with some verbosity in explanations (e.g., Phase 6.1's explanation of blocked JS, the HTML troubleshooting section's detailed explanation of why the error is misleading). However, most content is necessary given the complexity of the multi-phase deployment workflow. Some sections like the AskUserQuestion tables add structural overhead but serve a clear purpose. Could be tightened in places but isn't egregiously padded. | 2 / 3 |
Actionability | Every phase includes specific, executable CLI commands (pac help, pac auth who, pac auth create, pac pages upload-code-site, etc.), concrete bash code blocks, and precise instructions for parsing output. Decision trees are explicit with clear if/then branching. The troubleshooting section includes specific file patterns and exact fix steps. | 3 / 3 |
Workflow Clarity | The 6-phase workflow is clearly sequenced with explicit validation at each step (verify PAC CLI → verify auth → confirm environment → deploy → verify → handle errors). Feedback loops are present throughout: build failures trigger fix-and-retry, upload failures branch to Phase 6 or troubleshooting, authentication failures loop back to verification. The progress tracking table with TaskCreate/TaskUpdate provides explicit checkpoints. Key decision points are enumerated in a summary list. | 3 / 3 |
Progressive Disclosure | The skill references external files (skill-tracking-reference.md, scripts like check-activation-status.js, clear-site-cache.js, check-version.js) and other skills (/audit-permissions, /activate-site, /test-site), which is good progressive disclosure. However, the SKILL.md itself is monolithic — the troubleshooting section, Phase 6 blocked JS handling, and the detailed AskUserQuestion tables could potentially be split into separate reference files. The content is well-organized with clear headers but everything is inline in one large file. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Repository
- microsoft/power-platform-skills
- Commit
48e49c4
- Reviewed
Table of Contents
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.