activate-site
This skill should be used when the user asks to "activate site", "provision website", "activate a Power Pages website", "activate portal", "provision portal", "turn on my site", "enable website", or wants to activate/provision a Power Pages website in their Power Platform environment via the Power Platform REST API.
78
74%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/power-pages/skills/activate-site/SKILL.mdQuality
Discovery
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.
The description excels at providing trigger terms and establishing a clear, distinctive niche for Power Pages website activation. However, it is heavily weighted toward 'when to use' guidance while lacking specificity about what concrete actions the skill performs (e.g., API calls made, configuration steps, outputs produced). Adding a brief 'what it does' section would significantly improve it.
Suggestions
Add specific capability descriptions before the trigger terms, e.g., 'Provisions and activates Power Pages websites by calling the Power Platform REST API, configuring site settings, and verifying deployment status.'
Restructure to lead with concrete actions (what it does) followed by the existing trigger guidance (when to use it).
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Power Pages website activation/provisioning via Power Platform REST API) but doesn't list multiple concrete actions beyond 'activate/provision'. It lacks detail on what specific steps or operations are performed. | 2 / 3 |
Completeness | The 'when' is very well covered with explicit trigger phrases, but the 'what' is weak — it only says activate/provision a Power Pages website via the REST API without describing what concrete steps or outputs the skill produces. The description is essentially all 'when' and minimal 'what'. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'activate site', 'provision website', 'activate a Power Pages website', 'activate portal', 'provision portal', 'turn on my site', 'enable website'. These are realistic variations of how users would phrase this request. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche — Power Pages website activation/provisioning via Power Platform REST API is highly specific and unlikely to conflict with other skills. The trigger terms are domain-specific enough to avoid false matches. | 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, highly actionable skill for a complex multi-phase provisioning workflow. Its greatest strengths are the comprehensive error handling with specific recovery actions and the clear phase-based workflow with explicit validation checkpoints. The main weakness is moderate verbosity — some content is duplicated between phases and summary sections, and the entire skill could benefit from offloading reference tables to separate files.
Suggestions
Remove the redundant 'Key Decision Points' section at the end, as each decision point is already clearly documented within its respective phase.
Consider moving the cloud-to-domain mapping table and the Phase 4.2 error handling table to a reference file to reduce the main skill's length.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly detailed and well-structured but includes some redundancy — the 'Output' sections at the end of each phase repeat what was already stated, the 'Key Decision Points' section at the end largely duplicates logic already described in each phase, and some instructions are more verbose than necessary for Claude (e.g., explaining what a GUID is implicitly through repeated labeling). However, most content is genuinely necessary for this complex multi-phase workflow. | 2 / 3 |
Actionability | The skill provides fully executable commands (pac help, pac auth who, az account show, node scripts with specific arguments), concrete parameter tables, specific error code handling with exact actions for each case, and copy-paste ready PowerShell/node commands with all required flags documented. | 3 / 3 |
Workflow Clarity | The 5-phase workflow is clearly sequenced with explicit validation checkpoints (Phase 1.4 activation status check, Phase 3 user confirmation before mutation, Phase 4.2 comprehensive error handling with feedback loops for subdomain conflicts and token expiry). The error recovery table in Phase 4.2 is particularly well-structured with specific actions for each failure mode. | 3 / 3 |
Progressive Disclosure | The skill references external scripts and one reference file (skill-tracking-reference.md), which is good, but the main file itself is quite long (~250 lines of content) with all phases fully inline. The cloud-to-domain mapping table, error handling table, and progress tracking details could potentially be split into reference files. However, the structure within the file is clear with good use of headers and phases. | 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
66a61c6
- 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.