power-platform-skills: agent plugins for building on Microsoft Power Platform
A plugin marketplace for GitHub Copilot and other AI agents that provides Power Platform development plugins, including reusable skills, agents, and commands for building and deploying solutions.
At a glance
- What is it?
- Microsoft's power-platform-skills repository is a plugin marketplace that gives GitHub Copilot and Claude Code a set of skills, agents and commands for Power Platform work, covering Power Pages, model-driven apps, PCF components, code apps, canvas apps, Power Automate and process mining. It suits a developer who builds on the Power Platform and wants the agent to know the deployment tooling, and the plugin set spans several different toolchains.
- Who is it for?
- power-platform-skills suits a developer who already works on the Power Platform and wants the agent to know the PAC CLI workflow, the plugin SDK and the per-product tooling, and who is prepared to give the agent credentials for a tenant.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 3 days ago.
- What is it written in?
- Mainly JavaScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on October 19, 2026, and from our analysis. They are not legal advice.
Editorial analysis
A marketplace, not one assistant
power-platform-skills is described as a plugin marketplace for GitHub Copilot and other AI agents that provides Power Platform development plugins, including reusable skills, agents and commands for building and deploying solutions. The overview is explicit that this repository contains GitHub Copilot and Claude Code plugins for Power Platform services, and that each plugin provides skills, agents and commands to help developers build on the Power Platform.
That structure has an immediate consequence. You are not installing one thing, you are choosing from a catalogue, and the plugins are organised by Power Platform product rather than by task. The repository top level shows the shape of it, with a plugins/ directory holding each plugin, a marketplace.json describing the catalogue, and a shared/ directory plus scripts/ for the common parts and the installer. There is a .claude-plugin/ directory and a .claude/ directory for the Claude Code side, an evals/ directory for evaluating the skills, an AGENTS.md, a CODEOWNERS file, and the usual governance files with SECURITY.md, SUPPORT.md, CONTRIBUTING.md and a CODE_OF_CONDUCT.md.
The scope is broad. The plugins listed cover Power Pages, Model Apps, PCF, MCP Apps, Code Apps, Mobile Apps, Power Apps Mobile Extension, Canvas Apps, Power Automate, Process Intelligence, and Dataverse, which is external and lives in its own repository.
The licence is MIT, the primary language is JavaScript, and the homepage is at aka.ms/ppskills.
The installer sets up the CLI, detects the agent and registers the marketplace
The quick install is a single piped command, and there is a Windows PowerShell form for people who do not have curl in the shell.
curl -fsSL https://raw.githubusercontent.com/microsoft/power-platform-skills/main/scripts/install.js | nodeiwr https://raw.githubusercontent.com/microsoft/power-platform-skills/main/scripts/install.js -OutFile install.js; node install.js; del install.jsThe installer does four things automatically. It installs the pac CLI if it is not already there, it detects which tools you have available, meaning the GitHub Copilot CLI and Claude Code, it registers the plugin marketplace and installs all the listed plugins except dataverse, and it enables auto-update so the plugins stay current.
The dataverse plugin is excluded by default and has to be requested explicitly, with the --include-dataverse flag.
curl -fsSL https://raw.githubusercontent.com/microsoft/power-platform-skills/main/scripts/install.js | node - --include-dataverseThe README explains the dash, which tells Node to read the piped script from standard input, so the arguments after it reach the installer rather than being interpreted by Node. That detail is easy to miss and it is the difference between the flag working and not.
The manual route is available if you would rather not pipe a script into a runtime. Inside a GitHub Copilot CLI or Claude Code session, you add the marketplace and then install the plugins you want.
/plugin marketplace add microsoft/power-platform-skills/plugin install power-pages@power-platform-skills
/plugin install model-apps@power-platform-skills
/plugin install pcf@power-platform-skillsEach plugin pins a different stack, which is the real cost
The catalogue reads like a list of separate products that happen to share a marketplace, and the Stack lines in the README make that explicit.
Power Pages is for creating and deploying Power Pages sites with modern development approaches, and currently supports Code Sites, meaning single page applications, with React, Angular, Vue or Astro. Model Apps builds model-driven Power Apps end to end and the generative pages that go in them, with the /app-builder skill building and editing a whole app, tables, relationships, forms, views, charts, security roles, app and sitemap, from a natural language intent, and /genpage building generative pages for an app that already exists. The two can be used independently, and neither requires the other. The stack is React with TypeScript and Fluent, deployed through PAC CLI and the headless cds-maker-sdk.
PCF is for Power Apps component framework code components, and it carries a status line: Preview, with a link to a capabilities document. Its stack is Node.js 20 and later, the component framework, PAC CLI, the .NET SDK and the Azure CLI for verification and inventory. The README also notes that canvas apps need an admin to turn on Power Apps component framework for canvas apps in each environment, which is a permission step, not a code step.
Then the list diverges sharply. MCP Apps generates self-contained JavaScript server runtimes, JSON Schema registration metadata and interactive single-file MCP App widgets, with the skill /generate-mcp-app-ui creating an HTML widget that embeds its runtime by default for hosts that block public URLs, while retaining an opt-in CDN mode. Code Apps is React with Vite and TypeScript deployed via PAC CLI. Mobile Apps is Expo with React Native and TypeScript deployed through Power Apps Wrap. The Power Apps Mobile Extension plugin builds third-party native controls in Kotlin and Objective-C packaged as .ppmplugin bundles. Canvas Apps uses PA YAML authored via a Canvas Authoring MCP server and requires the .NET 10 SDK. Power Automate works through the FlowAgent MCP server on Node.js 18 and later with the Azure CLI. Process Intelligence analyses Power Automate Process Mining data and needs Node.js 22 or 24 LTS.
So the footprint is Node in several versions, .NET, the Azure CLI, the PAC CLI, plus whatever the agent runtime needs.
MCP servers are the backbone of the newer plugins
A thread runs through the catalogue, and it is worth naming on its own because it explains why the plugin set looks the way it does.
Several plugins are built on Model Context Protocol servers rather than on prompts alone. Canvas Apps is authored through a Canvas Authoring MCP server, and Power Automate is built, edited, run and debugged via the FlowAgent MCP server, which the README describes as a self-contained MCP bundle. Process Intelligence analyses bottlenecks, variants, cohorts, rework and object-centric executions through guided MCP workflows, with skills for /analytics, /investigate-process, /analyze-performance, /analyze-variants, /analyze-drivers, /compare-cohorts, /derive-metric and /analyze-objects, plus /setup and /report-issue for connection setup and support drafts.
The MCP Apps plugin works in the same direction from the other end. The /generate-codeful-mcp-tool skill creates a named runTool server entry point with its description, MCP behaviour annotations, input schema and structured output schema, and verified Dataverse access, while /generate-mcp-app-ui creates the HTML widget. The design note is that the widget embeds its runtime by default for hosts that block public URLs, with a CDN mode kept as an opt-in.
The Dataverse plugin is marked as an external plugin maintained in the Dataverse-skills repository, covering connecting to an environment, querying and changing records, managing tables and columns, and handling security, administration and solutions. It is not part of this repository and has to be installed separately, which is why the installer excludes it by default.
The Process Intelligence plugin is the one with an explicit gap. The README states that GCC, GCC High, DoD and Mooncake are not supported yet, which tells you the plugin covers the standard environments only and that the sovereign cloud variants need different handling.
Where power-platform-skills is the wrong tool
Three cases argue against it. The first is a developer who wants one coherent assistant across a product. The plugins are separate, with separate stacks, separate prerequisites and separate skills, and a task that crosses products, a canvas app that also needs a flow and a page, means the agent is working with several plugin sets whose toolchains do not match. Node 20 for PCF,.NET 10 for canvas apps, Node 18 for Power Automate and Node 22 or 24 for process intelligence is not a single environment you can assume is present.
The second case is someone who wants to evaluate the Power Platform. These skills encode the platform's own idioms and deployment path, so they are useful to a team already committed to it and no use to a team deciding between it and something else. The value is in the specifics, the PAC CLI, the solution deployment, the Dataverse tables, and a team without a tenant gets nothing from that.
The third case is a security restricted environment. The installer enables auto-update for the plugins and registers a marketplace, which means the agent's behaviour can change under you, and several plugins expect credentials for a tenant or an environment, and canvas apps need an administrator to enable a feature per environment. The evaluation should therefore start with one plugin in a non-production environment rather than the full installer.
There is a further consideration about the plugin count itself. Installing all listed plugins by default gives the agent a large surface of skills covering eleven products, and an agent with that many capabilities can pick a slower path through a task than one with a single focused plugin. The README's own note that the plugins can be installed individually suggests that selectivity is the intended usage, and a team that wants one thing should install one thing.
On maintenance, the repository has no GitHub releases despite the tagged version style of similar projects, the last push was on 2026-10-19, and the PCF plugin is marked as Preview, so its surface is expected to move.
Editorial conclusion
power-platform-skills suits a developer who already works on the Power Platform and wants the agent to know the PAC CLI workflow, the plugin SDK and the per-product tooling, and who is prepared to give the agent credentials for a tenant. It does not suit someone who wants one coherent assistant experience, since each plugin targets a different product with a different stack, and it does not suit an evaluation of the Power Platform itself, since these skills assume you are building on it. Before you install, check which plugins you need and which tools each one expects, and note that the last push was on 2026-10-19 with no tagged releases in the repository.
Frequently asked questions
How do I install the Microsoft Power Platform skills?
Run the quick installer, which curls the install.js script from the repository and pipes it to node, or on PowerShell download install.js and run it with node. It installs the pac CLI if needed, detects GitHub Copilot CLI or Claude Code, registers the marketplace, installs the plugins except dataverse, and enables auto-update.
How do I install the Dataverse plugin?
It is excluded from the default install because it is an external plugin maintained in the separate microsoft/Dataverse-skills repository. Pass the --include-dataverse flag to the installer, and note that the dash in the node - invocation is what lets the arguments reach the script.
Which Power Platform products do the plugins cover?
The marketplace lists Power Pages, Model Apps, PCF, MCP Apps, Code Apps, Mobile Apps, Power Apps Mobile Extension, Canvas Apps, Power Automate and Process Intelligence, with Dataverse available as an external plugin.
What does the Process Intelligence plugin need?
Node.js 22 or 24 LTS, the Azure CLI and a self-contained MCP bundle, and the README states that GCC, GCC High, DoD and Mooncake are not supported yet.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/microsoft-power-platform-skills)