$ ~/registry/skill/microsoft-plugins-power-pages-skills-deploy-site

SKILL

deploy-site

Name: deploy-site
Author: microsoft

Build and deploy an existing Power Pages code site to a target environment.

Stars

★ 440

Source

GitHub

Updated

2026-07-11

// securityCaution

Prompt only, no code
Open source

Summary

Overall this is an open-source, prompt-only skill with no declared secrets or remote endpoints, and no concrete red flags beyond ordinary local deployment actions via PAC CLI. It is caution-level rather than high risk.

CredentialsLow risk

No keys or environment variables are required, and the material does not describe credential harvesting or forwarding; it only uses an existing PAC CLI session with no explicit credential-abuse red flag.

Network egressCaution

No custom remote endpoint is declared; however, the deployment flow uses PAC CLI to interact with Power Pages/PAC services and upload site content, which is normal outbound connectivity for this tool.

Code executionCaution

The README asks the user to run local commands such as `pac help` and `pac auth who`, and may build/upload; this is normal local tool execution with no sign of arbitrary code execution or extra system privileges.

Data accessCaution

The skill reads local site source files and deploys them to the target environment, which is typical data access/write scope; there is no indication it accesses files or resources beyond what deployment requires.

Supply chainCaution

The source is an auditable GitHub open-source repository, but it has 0 stars, unknown maintenance status, and no declared license; supply-chain trust is moderate at best and warrants caution.

Recommendations

Deploy only after confirming the target environment and site contents.
Verify the PAC CLI version and that the logged-in account is the intended one.
Review repository updates, license, and dependencies before production use.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "deploy-site" skill from askskill:
1. Download https://raw.githubusercontent.com/microsoft/power-platform-skills/main/plugins/power-pages/skills/deploy-site/SKILL.md
2. Save it as ~/.claude/skills/deploy-site/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// examples

Deploy site to a test environment

Prompt

Use the deploy-site skill to deploy my existing local Power Pages code site to a test environment. First verify PAC CLI is available, confirm authentication and the target environment, then build and upload the site and tell me the result.

Expected

Verifies tooling, authentication, and environment, then builds and deploys the site and returns the deployment status or any errors.

Publish the latest code to production

Prompt

Publish the Power Pages site code in the current repository to the production environment. Reconfirm the target environment name before deployment to avoid mistakes; if authentication or dependencies are missing, prompt and handle them first.

Expected

Confirms the production environment, handles missing prerequisites if needed, and outputs the final publishing result.

Troubleshoot a failed deployment

Prompt

My Power Pages code site deployment failed. Use the deploy-site skill to rerun the process and specifically check PAC CLI, authentication status, environment selection, build steps, and upload stage, then tell me the root cause and how to fix it.

Expected

Reruns the deployment flow, identifies the failing step, and provides clear error details with recommended fixes.

// docs

Plugin check: Run node "${CLAUDE_PLUGIN_ROOT}/scripts/check-version.js" — if it outputs a message, show it to the user before proceeding.

Deploy Power Pages Code Site

Guide the user through deploying an existing Power Pages code site to a Power Pages environment using PAC CLI. Follow a systematic approach: verify tooling, authenticate, confirm the target environment, build and upload the site, and handle any blockers.

Core Principles

Verify before acting: Always confirm PAC CLI availability, authentication status, and the target environment before attempting any deployment.
Use TaskCreate/TaskUpdate: Track all progress throughout all phases — create the todo list upfront with all phases before starting any work.
Never change environment settings without consent: If deployment requires modifying environment configuration (e.g., unblocking JavaScript attachments), always explain the change and get explicit user permission first.

Initial request: $ARGUMENTS

Phase 1: Verify PAC CLI

Goal: Ensure PAC CLI is installed and available on the system PATH

Actions:

Create todo list with all 6 phases (see Progress Tracking table)
Run pac help to check if the PAC CLI is installed and available on the system PATH.
```
pac help
```
If the command succeeds: PAC CLI is installed. Proceed to Phase 2.
If the command fails (command not found / not recognized):
1. Inform the user that PAC CLI is required but not installed.
2. Fetch installation instructions from https://aka.ms/PowerPlatformCLI using the following approach:
  - Tell the user: "PAC CLI is not installed. You can install it by running:"
```
dotnet tool install --global Microsoft.PowerApps.CLI.Tool
```
  - If dotnet is also not available, direct the user to https://aka.ms/PowerPlatformCLI for full installation instructions including .NET SDK setup.
3. After installation, verify by running pac help again.
4. If it still fails, stop and ask the user to resolve the installation manually.

Output: PAC CLI installed and verified

Phase 2: Verify Authentication

Goal: Ensure the user is authenticated with PAC CLI and has a valid session

Actions:

Run pac auth who to check the current authentication status.
```
pac auth who
```
If authenticated: Extract the following values from the output:
- Environment name and URL
- Environment ID — the GUID after Environment ID:
- Cloud — the value after Cloud: (e.g., Public, UsGov, UsGovHigh, UsGovDod, China)
Proceed to Phase 3.

If not authenticated:

Inform the user they are not authenticated with PAC CLI.

Use AskUserQuestion to ask for the environment URL:

Question	Header	Options
You are not authenticated with PAC CLI. Please provide your Power Pages environment URL (e.g., `https://org12345.crm.dynamics.com`) so I can authenticate you.	Auth	(free text input via "Other")

Provide two placeholder options to guide the user:

"I'll paste the URL" (description: "Select 'Other' below and paste your environment URL")
"I don't know my URL" (description: "You can find it in the Power Platform admin center under Environments > your environment > Environment URL")

Once the user provides the URL, run the authentication command:
```
pac auth create --environment "<USER_PROVIDED_URL>"
```
This will open a browser window for the user to sign in.
After the command completes, verify by running pac auth who again.
If authentication succeeds, proceed to Phase 3.
If authentication fails, present the error to the user and help them troubleshoot.

Output: Authenticated PAC CLI session with environment name and URL extracted

…

View full docs ↗

Integrate Power Pages Web API into frontend with permissions and deployment.

microsoftGet→

$ loading_