CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

77%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 operational skill with excellent validation checkpoints and error-recovery loops. It is weakened by monolithic length — orchestration details that belong in reference files are inlined — and by repetition of the argument-based identity skip logic and stage-fallback explanation.

Suggestions

Move the ALM plan-refresh details (5.2b) and the status-file JSON schemas into a reference file under references/, keeping SKILL.md to the command and a one-line description of what it does.

State the SITE_IDENTITY_SOURCE="arguments" skip logic once (e.g. in Phase 1.4) and reference it from Phase 2.1 instead of repeating it; the same applies to the stageName-fallback explanation duplicated across 5.1b and 5.2b.

Drop the 'Workflow' numbered preview or the 'Progress Tracking' task table — they restate the same five phases twice before the phases are even presented.

DimensionReasoningScore

Conciseness

The body is mostly dense, non-obvious operational detail (cloud-to-domain table, error-code dispatch table, exact commands), but it repeats content: the SITE_IDENTITY_SOURCE="arguments" skip logic is stated three times in Phase 1.4 and again in Phase 2.1, the stageName-fallback explanation appears in both 5.1b and 5.2b, and the Workflow preview and Progress Tracking table duplicate the phase list. This fits 'mostly efficient but could be tightened' rather than the noticeably-verbose anchor.

3 / 5

Actionability

Fully executable throughout: exact node/pac/az commands with all flags, verbatim AskUserQuestion prompts and options, exact JSON payloads for the status file, a full cloud-to-domain mapping table, and a complete statusCode-to-action table covering common failure cases. Copy-paste ready.

5 / 5

Workflow Clarity

Five clearly sequenced phases with explicit validation checkpoints (auth check, tenant-alignment check with ok:true gate, already-activated early stop, user confirm gate) and genuine feedback loops (400 SubdomainConflict loops back to Phase 2.2, 429/5xx retries once, 401 re-login), plus a decision-point summary and progress-tracking checklist.

5 / 5

Progressive Disclosure

The referenced skill-level scripts exist in scripts/ (generate-subdomain.js, activate-site.js) and references are one level deep, but the body is a 425-line monolithic manual: the ALM-plan-refresh orchestration details and the status-file JSON schemas belong in a separate reference file, fitting 'content that should be separate is inline'.

3 / 5

Total

16

/

20

Passed

Description

86%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 description that clearly and concisely states both what the skill does and when to use it, with excellent natural-language trigger synonym coverage. Its only weaknesses are modest action specificity (the two listed actions are synonymous) and slight overlap risk with sibling Power Pages skills around the word 'provision'.

DimensionReasoningScore

Specificity

Names the domain ("Power Pages website in a Power Platform environment") and mechanism ("Power Platform REST API") with two concrete actions ("Activates and provisions"), but these are near-synonymous rather than several distinct actions, so it matches the '1-2 concrete actions' anchor rather than the 'several specific actions' anchor.

3 / 5

Completeness

It explicitly answers both questions: the 'what' ("Activates and provisions a Power Pages website ... via the Power Platform REST API") and the 'when' ("Use when the user wants to activate, provision, turn on, or enable a Power Pages website or portal") with concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

"activate, provision, turn on, or enable a Power Pages website or portal" enumerates four natural verb synonyms plus two noun variants, giving comprehensive coverage of how users would phrase this need; no common natural phrasing for this domain is missing.

5 / 5

Distinctiveness Conflict Risk

It carves out a clear niche with distinct activation triggers, but "provision" overlaps with closely related sibling skills in the same plugin suite (e.g. site creation/deployment), which is minor overlap risk rather than the 'minimal conflict risk' of the top anchor.

4 / 5

Total

17

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

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

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.