microsoft/power-platform-skills

This repository is Microsoft's official plugin marketplace for Power Platform development inside AI coding agents. It packages skills, agents and commands that let a GitHub Copilot CLI or Claude Code session scaffold, build and deploy Power Pages sites, model-driven and canvas apps, code apps, mobile apps, PCF components, MCP tools, Power Automate flows and process-mining analysis Repository overview.

How it works

The marketplace manifest lists each plugin; installing one adds its skills and slash commands to the agent's session. The plugins also wire in MCP servers and platform tooling, so the agent can act on a real environment — for example, /app-builder creates tables, relationships, forms, views and security roles from a natural-language intent, then deploys through cds-maker-sdk while PAC CLI handles sign-in and environment selection Model Apps plugin.

A typical workflow is therefore intent-first: describe an app, let the skill generate the project, run its checks and deploy with PAC, then verify the registration. Plugin stacks differ — code apps use React + Vite + TypeScript, mobile apps use Expo + React Native, and canvas apps author .pa.yaml through the Canvas Authoring MCP server Repository overview.

Installation paths

The quick installer is the shortest route: it installs PAC CLI if missing, detects installed agents (GitHub Copilot CLI, Claude Code), registers the marketplace, installs every plugin except dataverse, and enables auto-update README installation. Passing --include-dataverse adds the external Dataverse plugin, which is maintained in a separate repository and installed from its default branch; if it was previously installed from another marketplace, only one copy should remain so skills do not load twice Dataverse note.

Manual installation uses /plugin marketplace add followed by /plugin install <name>@power-platform-skills inside an agent session. Local development can point an agent at a plugin directory with --plugin-dir.

Requirements and limits

Prerequisites are per plugin, not global: Node.js 18+ for Power Automate, Node.js 20+ plus .NET SDK and Azure CLI for PCF, .NET 10 SDK for canvas apps, and an admin enabling PCF for canvas apps in each environment Repository overview. PCF is explicitly marked Preview PCF plugin, and Process Intelligence does not yet support GCC, GCC High, DoD or Mooncake clouds Process Intelligence. Power Pages code sites currently cover SPAs built with React, Angular, Vue or Astro Power Pages plugin.

The plugins may call shell commands, MCP servers and file edits, producing approval prompts. The README offers auto-approval options but warns they grant the agent the same machine access as the user, so they belong only in trusted or sandboxed environments README permissions.

Four plugins (Power Pages, Mobile Apps, Model Apps, Power Automate) ship default-on telemetry. Power Pages events can include Dataverse organization and Entra tenant GUIDs and, when PAC exposes it, the user's Entra object ID; Power Automate's bundled server records per-invocation outcome, duration and error class/code, but never error messages. Users can opt out of transmission with /<plugin>:telemetry off, while a local diagnostic mirror is still written; the environment variable override takes precedence Telemetry guide. The code is MIT-licensed license.