activate-site Skill
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. Published by microsoft in power-platform-skills.
Decision snapshot
Is this a fit?
Deployment, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Filesystem access, Shell access
Copy skill directory
2 months ago · MIT license
Access note: Local files. Access note: Shell access.
What is activate-site Skill?
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. Published by microsoft in power-platform-skills. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Deployment
- Deployment use cases
Declared skill metadata
- Source file: plugins/power-pages/skills/activate-site/SKILL.md
Allowed tools declared by source
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
- Local files
- Shell access
Requirements and access
Security and permissions
Review permissions before connecting any MCP server to an agent. Pay special attention to whether it can read local files, write data, call external services, or perform destructive actions.
When to use activate-site Skill
- Use it for deployment.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/power-platform-skills
- Skill file: plugins/power-pages/skills/activate-site/SKILL.md
What it does
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.
Skill instructions
Plugin check: Run node "${PLUGINROOT}/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: Ga
Verified compatibility and discovery
Frequently asked questions
What is activate-site?
activate-site is a open-source AI agent skill with Copy skill directory. Activates and provisions a Power Pages website in a Power Platform environment via the Power Platform REST API.
Who is activate-site best for?
activate-site is best for reusing agent instructions, scripts, and references, deployment workflows.
How do I install activate-site?
Install or run activate-site using Copy skill directory. Check activate-site for the latest setup command.
Is activate-site actively maintained?
activate-site may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
