$ ~/registry/skill/microsoft-plugins-code-apps-skills-deploy

SKILL

deploy

Name: deploy
Author: microsoft

Build and deploy a Power Apps code app to Power Platform.

Stars

★ 440

Source

GitHub

Updated

2026-07-11

// securityCaution

Prompt only, no code
Open source

Summary

This appears to be an open-source prompt-only deployment skill with no declared secrets, remote endpoints, or bundled executable component, so overall risk is low. Its instructions do guide a host agent to read project files and run build/deploy commands, but that is more of an operational concern at use time than a high-risk red flag in the skill package itself.

CredentialsLow risk

The material explicitly states there are no required keys or environment variables. The README only mentions re-authentication if `power-apps` login expires, with no indication that the skill embeds, collects, or exfiltrates credentials.

Network egressLow risk

No remote endpoints are declared, and as a prompt-only skill it does not directly make network requests. The documented `npx power-apps push` is an external deployment command aligned with the stated purpose, with no evidence of data being sent to unknown or unrelated endpoints.

Code executionLow risk

The system flags this as prompt-only, meaning the skill itself is not an executable component. Although the README instructs the host to run `npm run build` and `npx power-apps push`, this is textual workflow guidance rather than built-in local code execution by the skill package.

Data accessLow risk

The documentation references reading `memory-bank.md`, checking `dist/`, and possibly updating `power.config.json` or `memory-bank.md`, but these are instructional steps only. The skill itself does not declare direct file access or permissions beyond the deployment scenario.

Supply chainCaution

The source is an open-source GitHub repository under Microsoft's organization, which materially lowers risk because the code is auditable. However, the repo has 0 stars, no declared license, and unknown maintenance status, so some baseline supply-chain caution is still warranted.

Recommendations

Review the actual prompt content before enabling it to ensure it does not trigger build or deployment actions without confirmation.
Pin the repository to a specific commit or tag and review changes before upgrading.
Keep human approval in the host environment for deployment commands to avoid accidental pushes to production.
If actual use depends on `power-apps` CLI authentication, use a least-privilege account and audit deployment logs.

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

// install

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

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

// download

Download SKILL.mdInstall manifest ↗

// examples

Initial app deployment

Prompt

Build and deploy the current Power Apps code app to the target Power Platform environment, including pre-deployment checks, build steps, and a deployment result summary.

Expected

A completed build and initial deployment with deployment status, key steps, and any issue notes.

Redeploy an existing version

Prompt

Redeploy the existing Power Apps app to Power Platform, keep the current configuration, and report whether deployment succeeds.

Expected

A redeployment result showing success status, reused configuration, and error details if it fails.

Push app updates

Prompt

Build and deploy my latest changes to the Power Apps code app to Power Platform, then summarize the update contents and release result.

Expected

An updated deployment result with a summary of included changes and release status.

// docs

📋 Shared Instructions: shared-instructions.md - Cross-cutting concerns.

Deploy

Builds and deploys the app in the current directory to Power Platform.

Workflow

Check Memory Bank → 2. Build → 3. Deploy → 4. Update Memory Bank

Step 1: Check Memory Bank

Check for memory-bank.md in the project root. If found, read it for the project name and environment. If not found, proceed — the project may have been created without the plugin.

Step 2: Build

npm run build

If the build fails:

TS6133 (unused import): Remove the unused import and retry.
Other TypeScript errors: Report the error with the file and line number and stop. Do not deploy a broken build.

Verify dist/ exists with index.html before continuing.

Step 3: Deploy

Ask the user: "Ready to deploy to [environment name]? This will update the live app." Wait for explicit confirmation before proceeding.

npx power-apps push

Capture the app URL from the output if present.

If deploy fails, report the error and stop — do not retry silently. Common fixes:

Auth error / token expired → npx power-apps logout, then retry — the CLI will re-prompt browser login.
Environment mismatch → update environmentId in power.config.json to the correct value and retry.