activate-site
Activates and provisions a Power Pages website in a Power Platform environment via the Power Platform REST API. Use when the user wants to activate, provision, turn on, or enable a Power Pages website or portal.
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%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 with excellent trigger term coverage and a clear 'Use when' clause that explicitly lists multiple natural phrasings. The main weakness is that the capability description is somewhat narrow, listing only 'activates and provisions' as the core action, though this may accurately reflect a focused skill. Overall it would perform well in skill selection scenarios.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (Power Pages website) and the primary action (activates and provisions), but only describes one core action rather than listing multiple specific concrete actions like configuring settings, managing templates, or handling DNS. | 2 / 3 |
Completeness | Clearly answers both 'what' (activates and provisions a Power Pages website via Power Platform REST API) and 'when' (explicit 'Use when' clause listing multiple trigger scenarios). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'activate', 'provision', 'turn on', 'enable', 'Power Pages website', 'portal', and 'Power Platform'. These are the terms users would naturally use when requesting this task. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche — Power Pages website activation/provisioning via Power Platform REST API is a narrow, well-defined task unlikely to conflict with other skills. The combination of product name and specific action creates a clear identity. | 3 / 3 |
Total | 11 / 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 with excellent workflow clarity — clear phases, validation gates, error recovery loops, and comprehensive error handling. Its main weakness is moderate verbosity: the 'Output' summaries after each phase, the duplicative 'Key Decision Points' section, and some inline content that could be extracted to reference files inflate the token cost without proportional value. Overall it's a strong skill that could be tightened.
Suggestions
Remove the 'Output' subsections at the end of each phase — they restate what was already described in the Actions and add ~30 lines of redundancy.
Remove or significantly trim the 'Key Decision Points' section, as every point it makes is already stated in the relevant phase — this is pure duplication.
Consider extracting the Phase 4.2 error handling table and the Cloud-to-domain mapping table into a reference file to reduce the main skill's token footprint.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly 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 the phases, and some explanations (e.g., what Azure CLI login does) could be trimmed. However, most content is necessary given the complexity of the multi-phase workflow. | 2 / 3 |
Actionability | The skill provides fully executable commands throughout — specific bash commands, script invocations with exact argument flags, table-driven error handling with specific status codes and actions, and concrete examples of user prompts. Every step has clear, copy-paste-ready instructions. | 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 gate), error recovery loops (subdomain conflict → retry Phase 2.2), early termination conditions (already activated → stop), and a comprehensive error handling table in Phase 4.2 with specific actions for each failure mode. | 3 / 3 |
Progressive Disclosure | The skill references external scripts and a reference file for skill tracking, which is good. However, the content is quite long (~250 lines of detailed instructions) and could benefit from splitting some content (e.g., the cloud-to-domain mapping table, the detailed error handling table) into separate reference files. The 'Important Notes' section at the end adds bulk that partially duplicates earlier content. | 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.