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.
Install with Tessl CLI
npx tessl i github:microsoft/power-platform-skills --skill activate-site85
Quality
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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 description excels at trigger term coverage and completeness, providing explicit guidance on when to use the skill with multiple natural language variations. However, it focuses almost entirely on 'when' at the expense of 'what' - it could benefit from briefly describing what the activation process actually does or what capabilities it provides beyond just triggering the action.
Suggestions
Add 1-2 specific capabilities describing what the skill does during activation (e.g., 'Configures site settings, enables public access, validates licensing requirements')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description mentions 'activate/provision a Power Pages website' and references 'Power Platform REST API', naming the domain and general action, but doesn't list multiple specific concrete actions or capabilities beyond activation/provisioning. | 2 / 3 |
Completeness | Clearly answers both what (activate/provision Power Pages website via Power Platform REST API) and when (explicit 'Use when' equivalent with quoted trigger phrases). The description leads with when-to-use guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'activate site', 'provision website', 'activate portal', 'turn on my site', 'enable website' - includes multiple variations and synonyms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Power Pages/Power Platform website activation. The combination of 'Power Pages', 'Power Platform', 'portal', and 'provision' creates a distinct trigger profile unlikely to conflict with other skills. | 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-structured, highly actionable skill for activating Power Pages sites. The workflow is exceptionally clear with explicit phases, validation checkpoints, and comprehensive error handling. The main weakness is content density—some reference material (cloud mappings, detailed error tables) could be extracted to separate files to improve token efficiency.
Suggestions
Extract the Cloud-to-Site-URL-Domain mapping table to a shared reference file since it's likely reused across multiple Power Pages skills
Consider moving the detailed error handling table (Phase 4.2) to a troubleshooting reference file, keeping only the most common cases inline
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy (e.g., repeating cloud-to-domain mapping that could be in a reference file, verbose table formatting for simple decisions). The phase structure adds overhead but is justified for this multi-step workflow. | 2 / 3 |
Actionability | Provides fully executable commands with specific script paths, exact parameter names, and concrete PowerShell/node commands. Error handling tables give precise status codes and corresponding actions. Copy-paste ready throughout. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with explicit phases, validation checkpoints (Phase 1.4 activation status check, Phase 3 user confirmation), clear error recovery loops (subdomain conflict → retry), and a comprehensive decision point summary at the end. | 3 / 3 |
Progressive Disclosure | References external scripts and one reference file appropriately, but the main skill file is quite long (~200 lines of content). The cloud-to-domain mapping table and detailed error handling could be extracted to reference files. Structure is clear but content density is high. | 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.