Build Power Platform Apps With Microsoft's Official Agent Skills Marketplace

Power Platform development is a ceremony-heavy workflow: the pac CLI, environment selection, PA YAML app definitions. Microsoft now ships an official plugin marketplace that encodes those steps into skills, agents, and commands your coding agent can execute — so "build me a model-driven app for tracking equipment maintenance" becomes a guided pipeline instead of a documentation crawl.

Why This Skill Matters

microsoft/power-platform-skills is a plugin marketplace containing GitHub Copilot/Claude Code plugins for Power Platform services. The README's "Available Plugins" section enumerates eleven plugins — ten maintained in this repo (Power Pages, Model Apps, PCF, MCP Apps, Code Apps, Mobile Apps, Power Apps Mobile Extension, Canvas Apps, Power Automate, Process Intelligence) plus Dataverse, which is maintained in its own repo. Each plugin provides skills, agents, and commands for building on a specific service, with the stack documented per plugin: React + TypeScript + Fluent for Model Apps, Node.js 20+ and the Power Apps component framework for PCF, Expo + React Native for Mobile Apps, and so on.

The skills named in the README do the heavy lifting: /app-builder builds and edits a whole model-driven app from natural-language intent, /pcf:pcf scaffolds Microsoft-maintained templates and deploys with PAC, and Process Intelligence ships a family of analysis skills for Power Automate process mining data.

Installation

The quick installer sets up everything with auto-update enabled:

curl -fsSL https://raw.githubusercontent.com/microsoft/power-platform-skills/main/scripts/install.js | node

The installer installs the pac CLI if missing, detects available tools (GitHub Copilot CLI, Claude Code), registers the marketplace, installs all listed plugins except dataverse, and enables auto-update. Pass --include-dataverse to also install the Dataverse plugin — with the piped-script form, the - tells Node to read the script so the arguments after it reach the installer.

To install manually, run these commands inside a GitHub Copilot CLI or Claude Code session:

/plugin marketplace add microsoft/power-platform-skills
/plugin install model-apps@power-platform-skills
/plugin install process-intelligence@power-platform-skills

The README's manual-install list names all eleven; note that two plugin entries carry install names that differ from their section headings — code-apps-preview (listed under "Code Apps") and mobile-app (listed under "Mobile Apps").

Real Workflow: Build a Model-Driven App From an Intent

1. Install the Model Apps plugin and start a Claude Code or Copilot CLI session.
2. Ask for the app in natural language. The /app-builder skill builds and edits a whole app — tables, relationships, forms, views, charts, security roles, app + sitemap — from that intent.
3. When the app needs a generative page, /genpage builds one for an app that already exists. The README notes the two skills are independent — neither requires the other.
4. Deploy through the stack the plugin documents: React + TypeScript + Fluent, deployed through the headless cds-maker-sdk, with the PAC CLI signing you in and choosing the environment.

Real Workflow: Investigate Process Mining Data

The Process Intelligence plugin analyzes Power Automate Process Mining data. /analytics and /investigate-process guide open-ended analysis, while six skills answer focused questions: /analyze-performance, /analyze-variants, /analyze-drivers, /compare-cohorts, /derive-metric, and /analyze-objects. /setup and /report-issue handle connection setup and support drafts. This plugin needs Node.js 22 or 24 LTS and the Azure CLI, and the README states that GCC, GCC High, DoD and Mooncake are not supported yet.

Running Without Interruption

Plugins here may invoke multiple tools during a session, which can mean frequent approval prompts. The README documents two options per tool to reduce that, with a warning worth repeating: auto-approval options give the agent the same access you have on your machine, so only use them in trusted or sandboxed environments. On Claude Code, the recommended option is the acceptEdits permission mode — auto-approve file edits while still prompting for shell commands — with explicit allow rules for the commands your workflow needs:

{
  "defaultMode": "acceptEdits",
  "permissions": {
    "allow": [
      "Bash(npm run *)",
      "Bash(git *)",
      "Bash(pac *)"
    ]
  }
}

Tips

• The Dataverse plugin lives in microsoft/Dataverse-skills, and this marketplace installs it straight from that repository's default branch. If you already installed dataverse from the dataverse-skills marketplace, keep only one of the two installs so its skills are not loaded twice.
• Telemetry is default-on in four plugins (Power Pages, Mobile Apps, Model Apps, Power Automate). Opt out with /<plugin>:telemetry off — for example /power-pages:telemetry off — or set the POWER_PLATFORM_SKILLS_TELEMETRY_<PLUGIN>_OPTOUT environment variable, which takes highest precedence for automation and CI.
• Per-plugin requirements add up: PCF is preview status with Node.js 20+ and the .NET SDK, Canvas Apps authors PA YAML via an MCP server and requires the .NET 10 SDK, and Power Automate needs Node.js 18+ and az login.
• For local plugin development, clone the repo and launch your agent with --plugin-dir pointing at the plugin directory.

When Not to Use This

These plugins are Power Platform-specific: they drive Power Platform services through the pac CLI, platform MCP servers, and platform SDKs, so they add nothing to a project that never touches Dataverse, Power Apps, Power Automate, or Power Pages. And the plugins assume an environment to deploy into — a Power Platform tenant — not just a local codebase.

See the leaderboard for more skills.