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.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-sequenced workflow skill with strong validation and error-recovery loops. The main weakness is conciseness: redundant decision-point restatements and verbose internal-implementation exposition in the ALM sections add tokens that don't aid execution.

Suggestions

Remove or compress the "Important Notes > Key Decision Points" block — it restates Phase 4.2's error-handling table and the phase summaries; reference those sections instead of duplicating them.

Trim section 5.2b to just the command, the marker fields, and the user-facing next-step behavior; drop internal implementation details like planData.activations writes and re-render mechanics that the agent does not need to act on.

Tighten the two inline gate HTML-comment prose blocks, which currently embed lengthy orchestration rationale that could be shortened to the gate purpose and cancel semantics.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and assumes Claude's competence (no concept over-explanation), but section 5.2b's internal-implementation prose (planData.activations, re-render mechanics) and the "Important Notes > Key Decision Points" section duplicating Phase 4.2's error table add noticeable padding.	3 / 5
Actionability	Every phase provides concrete, executable guidance: exact bash/script invocations with named arguments, a status-code-to-action table, and explicit subdomain validation rules — fully copy-paste ready.	5 / 5
Workflow Clarity	Five numbered phases are clearly sequenced with explicit validation checkpoints (1.4 already-activated check, Phase 3 confirm gate) and feedback loops (400 → re-pick subdomain, 401 → re-login, 429 → retry) for this mutating operation.	5 / 5
Progressive Disclosure	Phases are well-organized with a one-level-deep reference (skill-tracking-reference.md) and referenced scripts that exist in the bundle, but several referenced files are external to the bundle and a fair amount of detail is inlined rather than split out.	4 / 5
	Total	17 / 20 Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that concisely states what the skill does and when to use it, with rich natural-language trigger synonyms. The only minor gap is a somewhat narrow action inventory, keeping specificity at 4 rather than 5.

Dimension	Reasoning	Score
Specificity	"Activates and provisions a Power Pages website in a Power Platform environment via the Power Platform REST API" names the domain and concrete actions backed by a specific API; it falls just short of a 5 because the action set is limited to activate/provision rather than a broad multi-action inventory.	4 / 5
Completeness	It explicitly answers both what ("Activates and provisions... via the Power Platform REST API") and when ("Use when the user wants to activate, provision, turn on, or enable...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	"activate, provision, turn on, or enable a Power Pages website or portal" gives comprehensive natural coverage with multiple synonyms (turn on, enable) and the portal synonym, matching the top anchor.	5 / 5
Distinctiveness Conflict Risk	The Power Pages / Power Platform niche and specific activation triggers are clearly distinct from other skills with minimal conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: microsoft/power-platform-skills
Path: plugins/power-pages/skills/activate-site/SKILL.md
Commit: 4c284ab

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.