Agent skill · Backend & API

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.

majiayu000github.com/majiayu000GitHub ↗
claude-codecan modify filesMIT
Install
npx skills add majiayu000/claude-skill-registry --skill activate-site --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 12 KB
Bundled scripts: none
Allowed tools: ReadBashGlobGrepAskUserQuestionTaskCreateTaskUpdateTaskList
Path: skills/api/activate-site/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

> **Plugin check**: Run `node "${CLAUDE_PLUGIN_ROOT}/scripts/check-version.js"` — if it outputs a message, show it to the user before proceeding. # Activate Power Pages Site Provision a new Power Pages website in a Power Platform environment via the Power Platform REST API. > **Prerequisite:** This skill expects an existing Power Pages code site created via `/create-site`. Run that skill first if the site does not exist yet. ## Core Principles - **Cloud-aware URL resolution** — Never hardcode API base URLs or site URL domains. Always derive them from the Cloud value returned by `pac auth who`. - **Token handling** — Scripts acquire and refresh Azure CLI tokens internally. The agent only needs to verify the user is logged in to Azure CLI. - **Confirm before mutating** — Always present the full activation parameters to the user and get explicit approval before POSTing to the websites API. **Initial request:** $ARGUMENTS ## Workflow 1. **Phase 1: Verify Prerequisites** — PAC CLI auth + Azure CLI login + activation status check 2. **Phase 2: Gather Parameters** — Site name, subdomain, website record ID 3. **Phase 3: Confirm** — Present all parameters to user for approval 4. **Phase 4:

What's inside
Steps it walks through
  1. Core Principles
  2. Workflow
  3. Phase 1: Verify Prerequisites
  4. Actions
  5. Output
  6. Phase 2: Gather Parameters
  7. Phase 3: Confirm
  8. Phase 4: Activate & Poll
  9. Phase 5: Present Summary
  10. Important Notes
  11. Progress Tracking
  12. Key Decision Points
Ships with 1 file
  • metadata.json
Commands it runs
pac help
dotnet tool install --global Microsoft.PowerApps.CLI.Tool
pac auth who
az account show
node "${CLAUDE_PLUGIN_ROOT}/scripts/check-activation-status.js" --projectRoot "<PROJECT_ROOT>"
node "${CLAUDE_PLUGIN_ROOT}/skills/activate-site/scripts/generate-subdomain.js"
pac pages list
More from claude-skill-registry
All skills →
About this skill
What does the activate-site skill do?

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.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill activate-site --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going