deploy-site
This skill should be used when the user asks to "deploy to power pages", "upload site", "publish site", "deploy site", "push to power pages", "upload code site", or wants to deploy/upload an existing Power Pages code site to a Power Pages environment using PAC CLI.
Install with Tessl CLI
npx tessl i github:microsoft/power-platform-skills --skill deploy-site78
Quality
74%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/power-pages/skills/deploy-site/SKILL.mdDiscovery
72%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 description excels at trigger term coverage and distinctiveness, making it easy for Claude to identify when to select this skill. However, it inverts the typical structure by focusing heavily on 'when' while neglecting 'what' - it doesn't explain what concrete actions the skill performs during deployment. The description would benefit from adding specific capabilities.
Suggestions
Add specific actions the skill performs, e.g., 'Deploys Power Pages code sites using PAC CLI, including authentication, site packaging, and upload to target environments.'
Restructure to lead with capabilities before the trigger phrases: 'Packages and deploys Power Pages code sites to environments using PAC CLI. Use when...'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Power Pages deployment) and mentions using PAC CLI, but doesn't list specific concrete actions beyond 'deploy/upload'. Missing details about what the deployment process actually involves. | 2 / 3 |
Completeness | Strong on 'when' with explicit trigger phrases, but weak on 'what'. The description focuses almost entirely on when to use it rather than explaining what capabilities it provides or what steps it performs. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'deploy to power pages', 'upload site', 'publish site', 'deploy site', 'push to power pages', 'upload code site'. These are phrases users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche with 'Power Pages' and 'PAC CLI' as distinct identifiers. Unlikely to conflict with other deployment skills due to the specific platform targeting. | 3 / 3 |
Total | 10 / 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-crafted deployment skill with excellent actionability and workflow clarity. The six-phase structure with explicit validation checkpoints, error handling paths, and user confirmation points demonstrates strong workflow design. The main weakness is length—some content (troubleshooting sections, repeated command blocks) could be extracted to reference files to improve token efficiency.
Suggestions
Extract the 'Troubleshooting: HTML Blocked Attachment Error' section to a separate TROUBLESHOOTING.md file and reference it inline
Consider consolidating repeated AskUserQuestion table formats into a single reference pattern at the top, then use shorthand references throughout
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy (e.g., repeating 'pac pages upload-code-site' command multiple times, verbose explanations of AskUserQuestion tables). Some sections could be tightened, though it avoids explaining basic concepts Claude already knows. | 2 / 3 |
Actionability | Provides fully executable PowerShell commands throughout, specific PAC CLI syntax, exact file paths, and concrete examples. Commands are copy-paste ready with clear placeholders for user-specific values. | 3 / 3 |
Workflow Clarity | Excellent multi-phase workflow with explicit validation checkpoints (verify auth before deploy, confirm environment, validate build before upload). Includes clear error recovery paths (Phase 6 for blocked JS, HTML error troubleshooting) and feedback loops for retry scenarios. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear phases and headers, but the skill is monolithic (~350 lines) with detailed troubleshooting inline. The HTML blocked attachment troubleshooting and Phase 6 could be separate reference files. References to external files (skill-tracking-reference.md, check-activation-status.js) are appropriately one-level deep. | 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 | |
- 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.