REPO PACKAGE
microsoft power-platform-skills
OFFICIAL68skills
2ready to use
LABSCO SUMMARY
Twenty-nine of the 69 total are Power Pages skills: creating and deploying a code site, wiring Dataverse tables, Web API calls, Cloud Flows, and AI summarization into it, then testing, security-scanning, and firewalling the result once it's live. Twenty-seven more build an Expo/React Native mobile app end to end — scaffolding, adding native device features (camera, GPS, PDF, pen input) through a shared add-native entry point, wiring an offline-sync profile table by table, debugging a running Metro session, and deploying to a tenant. The rest split three ways: seven wire a connector (Azure DevOps, Excel, Office 365, OneDrive, Teams, Copilot Studio) or scaffold a React/Vite "code app," four operate the separate Canvas Apps authoring MCP server, one builds an MCP App widget, and one — genpage — generates a React/Fluent generative page inside a model-driven app.
This is for a Microsoft shop already licensed for Power Platform, building through one or more of the six plugins — each installs separately (/plugin install power-pages@power-platform-skills, mobile-app@..., and so on), so a team that only wants the mobile-app track isn't forced to also take the Power Pages or Canvas Apps skills.
READ THE FULL ANALYSIS
Almost nothing here runs standalone. Thirty-one of the 69 need a stored account key — a signed-in Power Platform environment, mostly — another 31 need a local tool such as the PAC CLI or a running Metro bundler, four need a live MCP session, and only two come back ready with nothing further: generate-canvas-app and preview-screens. generate-canvas-app also ships with no description in what we captured.
Telemetry is opt-out, but only documented for one of the six plugins. The README says Power Pages skills gather anonymous usage signals by default, turned off per-plugin with /power-pages:telemetry off or a POWER_PLATFORM_SKILLS_TELEMETRY_POWER_PAGES_OPTOUT environment variable; it says nothing about whether the other five plugins — including the mobile-app track that's nearly as large — send anything at all.
ALSO IN THIS PACKAGE
PLUGINS
8 itemsPLUGIN
power-pages
Create and deploy Power Pages sites using modern development approaches. Supports code sites (SPAs) with React, Angular, Vue, or Astro.
PLUGIN
model-apps
Build model-driven Power Apps end to end: /app-builder authors whole apps (tables, relationships, forms, views, charts, security roles, app + sitemap) from a natural-language intent, and /genpage builds generative pages with specialist agents for planning, entity creation, and parallel code generation. Requires PAC CLI > 2.10.0 and Azure CLI (`az`).
PLUGIN
mcp-apps
Generate JavaScript server runtimes and CDN-free or CDN-enabled MCP App widgets.
PLUGIN
canvas-apps
Build Power Apps Canvas Apps using the Canvas Authoring MCP server.
PLUGIN
code-apps-preview
Build and deploy Power Apps code apps using React, Vite, and Power Platform connectors.
PLUGIN
mobile-app
Build and deploy Power Apps code apps for mobile using Expo (React Native), with native device functionality and Power Platform connectors
PLUGIN
power-apps-mobile-extension
Build third-party Power Apps Mobile (PAM) controls into a prebuilt .ppmplugin binary (Android DEX + flat iOS .framework + manifest.json) for the wrap runtime. Public tooling only; recommended build entry point /generate-ppmplugin.
PLUGIN
power-automate
Build, edit, run, and debug Power Automate cloud flows via the FlowAgent MCP server — connection lifecycle, surgical edits, copy across environments, run management, and validated expressions.
AGENT PERSONALITIES
20 itemsAGENT PERSONALITY
canvas-app-planner
Produces implementation plans for approved Canvas App creation and complex edits. Discovers controls, APIs, and data sources, then writes a compact dispatch index, shared conventions, and one screen-specific brief per target file.
AGENT PERSONALITY
canvas-screen-builder
Implements or modifies one Canvas App screen from a shared plan and a screen-specific brief. Writes exactly one .pa.yaml file and performs self-QA without compiling.
AGENT PERSONALITY
code-app-architect
Power Apps Code App Architect specializing in React/Vite architecture, Dataverse integration, connector patterns, and Power Platform deployment. Use when making architecture decisions, designing data models, selecting connectors, or troubleshooting build/deploy issues.
AGENT PERSONALITY
data-model-architect
Use when an orchestrator needs a Dataverse data model proposed (existing-table reuse, new tables in dependency-tier order, Mermaid ER diagram) for embedding in native-app-plan.md. Read-only — proposes, never mutates.
AGENT PERSONALITY
native-app-planner
Use when the orchestrator needs architecture approval before conditional Dataverse modeling and screen planning for a Power Apps mobile app. Read-only — proposes everything, mutates nothing.
AGENT PERSONALITY
offline-profile-architect
Use when the orchestrator needs an offline profile design proposed (per-table row scope, recommended relationships, selected columns, sync frequency) for embedding in native-app-plan.md ## Offline Profile section. Read-only — proposes, never mutates.
AGENT PERSONALITY
screen-builder
Use when an orchestrator needs ONE screen of a Power Apps mobile app implemented from a per-screen spec in native-app-plan.md. Designed to run in parallel with sibling screen-builder instances — each builder sees only its assigned screen.
AGENT PERSONALITY
screen-planner
Use when an orchestrator needs a screen graph + per-screen specs (navigation pattern, components, data, native capabilities) and a plan-time HTML preview or screen-plan delta for a Power Apps mobile app. Read-only — does NOT write TSX.
AGENT PERSONALITY
genpage-connector-builder
Owns ALL GenPage connector work: it is the single owner of the connectors rollback gate, performs connector discovery (connections, connection references, datasets, tables, operations, and schema), creates Dataverse connection references when needed, and produces the ## Connector Bindings contract. Invoked only by the top-level genpage orchestrator from BOTH the create and edit flows; never invoked by planners or directly by users.
AGENT PERSONALITY
genpage-customapi-builder
Owns ALL GenPage Dataverse Custom API (plug-in) work: it is the single owner of the custom-api feature-flag gate, discovers the Custom APIs a page can bind to (Global and entity-bound Actions/Functions) plus their declared request-parameter kinds, and produces the ## Custom API Bindings contract. Invoked only by the top-level genpage orchestrator from BOTH the create and edit flows; never invoked by planners or directly by users.
AGENT PERSONALITY
genpage-edit-planner
Plans edits to an existing generative page. Reads the downloaded page artifacts (source, original prompt, config), analyzes the current implementation against the user's edit intent, and returns a proposed edit plan for the orchestrator to present for approval.
AGENT PERSONALITY
genpage-entity-builder
Creates Dataverse entities (tables, columns, relationships, choices) specified in genpage-plan.md using the plugin's Node.js Web API scripts. Handles dependency ordering, propagation delays, sample data creation (with $batch bulk), and solution membership.
AGENT PERSONALITY
genpage-page-builder
Generates a single complete .tsx generative page from a plan document and schema. Reads genpage-plan.md for page specification, RuntimeTypes.ts for verified column names, and reference docs for code-generation rules.
AGENT PERSONALITY
genpage-planner
Plans generative page creation for model-driven apps. Validates prerequisites, authenticates with PAC CLI, gathers requirements, detects which Dataverse entities and model-driven apps exist, and returns a proposed plan for the orchestrator to present for approval.
AGENT PERSONALITY
ai-webapi-integration
Use this agent when the user needs to integrate one of the Power Pages generative-AI summarization APIs into their frontend code. The agent supports two APIs: 1.
AGENT PERSONALITY
ai-webapi-settings-architect
Use this agent when the user wants to configure Power Pages generative-AI summarization site settings (search summary, data summarization, case-page Copilot preset), enable the Summarization APIs, or register maker-defined prompts for the `/_api/summarization/data/v1.0/` endpoint. Trigger examples: "enable data summarization", "set up case summary prompt", "configure AI summary settings", "add generative AI site settings", "register summarization prompt for products".
AGENT PERSONALITY
data-model-architect
Use this agent when the user needs to design, plan, or analyze a data model for their Power Pages site. Trigger examples: "design a data model", "what tables do I need", "plan my Dataverse schema", "analyze my data requirements", "propose tables for my site", "show me existing tables", "create an ER diagram", "what entities should I use", "map out my database".
AGENT PERSONALITY
table-permissions-architect
Use this agent when the user wants to set up table permissions for their Power Pages site, configure CRUD access for web roles, or define permission scopes. Trigger examples: "set up table permissions", "configure table permissions", "add table permissions", "set up CRUD permissions", "configure web role access", "add permissions for my tables".
AGENT PERSONALITY
webapi-integration
Use this agent when the user needs to integrate Power Pages Web API for a specific Dataverse table into their frontend code. Trigger examples: "integrate web api for products table", "add api calls for orders", "connect my site to the blog posts table", "implement crud for categories", "set up web api client", "create a service for the products table", "add data fetching for my table", "hook up the products api".
AGENT PERSONALITY
webapi-settings-architect
Use this agent when the user wants to configure Web API site settings for their Power Pages site, enable Web API access for tables, or specify which columns to expose via the Web API. Trigger examples: "enable web api", "set up web api", "configure web api settings", "add web api access", "enable api access for products table", "configure web api fields".
MCP SERVERS
4 itemsMCP SERVER
canvas-authoring
stdio · dnx Microsoft.PowerApps.CanvasAuthoring.McpServer --yesMCP SERVER
microsoft-learn
Official Microsoft Learn MCP Server and CLI tool – powering LLMs and AI agents with real-time, trusted Microsoft docs & code samples.
http · https://learn.microsoft.com/api/mcpMCP SERVER
microsoft-learn
Official Microsoft Learn MCP Server and CLI tool – powering LLMs and AI agents with real-time, trusted Microsoft docs & code samples.
http · https://learn.microsoft.com/api/mcpMCP SERVER
microsoft-learn
Official Microsoft Learn MCP Server and CLI tool – powering LLMs and AI agents with real-time, trusted Microsoft docs & code samples.
http · https://learn.microsoft.com/api/mcpWHAT'S INSIDE
68 showing · 68 totalReady to use
Nothing else to set up — install it and go.
68 of 68
SETUP
Showing all 68 skills
activate-site
A Power Pages site you have built stays invisible to the world until this turns it on and gives it a public web address.
add-ai-webapi
Puts AI-written summaries onto a Power Pages website, so a long record or a page of search results comes back to the visitor as a short paragraph.
add-azuredevops
Wires a Power Apps app into Azure DevOps, so the team's work-tracking data is available inside the app itself.
add-camera
Writes the camera code for a Power Apps mobile app — the part that opens the camera, reaches the photo gallery and reads barcodes — so a screen can call it in one line.
add-cloud-flow
Lets a page on a Power Pages website kick off one of your Power Automate flows, and settles who is allowed to trigger it.
add-connector
The catch-all for connecting a Power Apps mobile app to an outside service when there is no dedicated skill for that particular one.
add-data-source
Adding data to a canvas app can only be done by hand in Power Apps Studio — this talks you through the clicks, then checks the connection really arrived before work carries on.
add-datasource
You say what your mobile app needs to do; this decides which kind of data connection fits and hands you to the skill that sets it up.
add-dataverse
Puts a company's own business records behind a mobile app — the customer, order or job tables kept in Dataverse — and builds or widens those tables when they do not exist yet.
add-excel
A spreadsheet becomes the app's database: rows are read out of an Excel workbook and new ones written back into it.
add-geolocation
Location tracking that does not stop when the user closes the app — each position is held on the phone and pushed up into Dataverse.
add-mcscopilot
Connects an app to the chatbots an organisation has already built in Copilot Studio, so the app can put work to them instead of reimplementing them.
add-native
The way into the phone's own hardware from a Power Apps mobile app: camera, files, sharing, PDF printing, signature capture, location in the background.
add-office365
An app that needs to email somebody, or look at their diary, borrows Outlook to do it rather than building its own mail and calendar.
add-onedrive
File storage for an app without building any: the user's own OneDrive becomes the place its documents are kept and fetched back from.
add-pdf-report
The app prints its own paperwork: it turns data it already holds into a PDF on the device, which the user can then send on or keep.
add-pdf-viewer
Gives a Power Apps phone app its own built-in PDF reader, so documents open inside the app instead of being handed off elsewhere.
add-pen-input
Lets someone sign or draw with a finger or stylus inside a Power Apps phone app, and hands the drawing back as an image file.
add-sample-data
Fills a brand-new app's tables with believable made-up records, so nothing looks blank the first time someone opens it.
add-seo
Sets up a Power Pages website so search engines can find and list its pages, and so links to it look right when someone shares them.
add-server-logic
Moves part of a Power Pages website's code off the visitor's browser and onto the server, where passwords and keys stay out of sight.
add-sharepoint
Connects a Power Apps phone app to SharePoint, so it can read and update the lists and documents a team already keeps there.
add-table-to-offline-profile
Makes one more set of records download to the phone, so that part of the app keeps working when there's no signal.
add-teams
Gives a Power Apps app a way to send messages into Microsoft Teams.
assign-offline-profile
Names the people and teams who actually get an app's offline mode — until this is done the setup exists but nobody's phone uses it.
audit-permissions
Checks who is allowed to read or change each piece of data on a Power Pages site, and reports back where that is too loose, too tight, or missing.
canvas-app
Builds or changes the screens of a Power Apps canvas app, then checks every button and feature it was asked for actually works before handing it back.
configure-canvas-mcp
The setup step that points the editing tools at whichever Power Apps app you currently have open in your browser, so they can change it.
configure-env-variables
Lets a website setting hold a different value in the test copy than in the live one, so nobody has to edit it by hand at each release.
create-code-app
Builds a Power Apps business app as an ordinary web app and puts it live, ending with a link people can open.
create-mobile-app
Turns a description of an app into a working iPhone and Android app, with its screens, its data and its use of the camera or GPS already built in.
create-site
Builds a whole Power Pages website from a description — real text, real photos and a chosen look — and puts it online.
create-webroles
Defines the kinds of visitor a Power Pages site has — editor, member, signed-out guest — so access can be granted to a group rather than one person at a time.
debug-app
Watches a mobile app while it runs, finds what is going wrong — a crash, or a list that just comes up empty — and fixes it.
deploy
Packages a Power Apps phone app for iPhone and Android and pushes the finished build up to the company's Power Platform.
deploy-pipeline
Moves a finished Power Pages site up the chain — from the copy you build on, to a testing copy, to the one real customers use.
deploy-site
Takes the Power Pages site sitting on your machine and puts it on the live web address people visit.
design-system
Settles how a mobile app will look — its colours, its type, its spacing — once, so every screen built afterwards matches.
diagnose-deployment
Works out why publishing a Power Pages site failed, matches the error against a list of ones seen before, and offers the fix for you to accept.
edit-app
Changes one part of a mobile app you already built — a screen, its data, its look — without starting the whole thing over.
edit-offline-profile
Changes one detail of how an app stores data on the phone for use without a signal, instead of walking the whole setup again for a one-line edit.
enable-tables-offline
Turns on the two switches a set of records needs before it can be taken offline at all — without them the rest of the offline setup simply refuses it.
ensure-pipelines-host
Makes sure there is a central place set up to run automated releases — finding one that already exists, or creating it with your say-so.
export-solution
Packs everything a Power Pages site is made of into a single file you can carry to another Power Platform environment and load there.
force-link-environment
Detaches an environment from the release setup it is currently tied to and attaches it to a different one — the old one loses it.
generate-mcp-app-ui
Makes a small visual panel — a chart, a map, a table — so a tool's answer shows up as a picture in the chat instead of raw text.
genpage
Adds new screens to a Power Apps business app that already exists, builds them against its real data, and puts them live.
import-solution
Loads a packaged-up Power Pages site into another environment, with the option to check first for anything it depends on that isn't there yet.
integrate-backend
Decides which of several ways a Power Pages site could reach its data suits what you're building, says why, then hands the job to whoever builds it.
integrate-webapi
Writes the code that lets a Power Pages site's pages read and save records, and sets the permissions that let those calls through.
list-connections
Finds the saved sign-in a Power Apps mobile app uses to reach an outside service like Teams or SharePoint — or creates one if there isn't one yet.
manage-firewall
Turns on and tunes the filter that sits in front of a live Power Pages site and blocks hostile traffic before it reaches the pages.
manage-headers
Checks the safety rules a Power Pages site hands to the browser — what it may load, who may embed it, how its cookies behave — and fixes the gaps.
open-wrap-url
Jumps straight to the Power Apps page for turning one app into a packaged mobile app, instead of navigating there by hand.
plan-alm
Agrees up front how a Power Pages site will travel from the build copy to the live one, and writes it down for the tools that do the moving to follow.
preview-offline-scope
Tells you how much data each phone would have to download, and how often, before you switch offline use on for anyone.
preview-screens
Turns every screen of a mobile app into pictures in a single web page, so you can look at the whole app without installing anything.
report-issue
Writes up a bug report about this toolkit for you, with the details of your machine and setup already gathered — and private files left out.
scan-site
Probes a live Power Pages site the way an attacker would and reports back, in plain words, what it managed to find.
security-review
Runs every security check on a Power Pages site at once and puts the whole picture in one report, instead of six separate ones.
set-app-registration-native
Connects a Power Apps mobile app to Microsoft work sign-in, by taking the identifier you copy from the Power Apps page and writing it into the app.
setup-auth
Gives a Power Pages site a working sign-in and sign-out, and controls what each kind of signed-in visitor is shown.
setup-datamodel
Designs the database behind a Power Pages site — what is stored, in what fields, and how the pieces link — and builds it once you approve.
setup-offline-profile
A Power Apps mobile app normally needs a live connection; this works out which data should be copied down to the phone and how often it refreshes, so the app still runs with no signal.
setup-pipeline
Sets up an automatic route that carries a Power Pages site from one environment to the next and out to the live one, running inside Power Platform itself with no build server to install.
setup-solution
A Power Pages site is made of many separate pieces scattered across the platform; this collects them into one package stamped with your organisation's name, so the whole site can travel as a unit.
telemetry
Some people would rather their tooling did not report how they use it; this is the on/off switch for that in Power Pages, and it will also tell you where the switch currently sits.
test-site
Opens your published Power Pages site in a real browser, clicks through every page it can find, and reports what broke — it only looks, and never changes the site.
No skill in this package matches that.
HOW TO GET IT
WHOLE PACKAGEInstall the whole package (68 skills)
npx skills add microsoft/power-platform-skillsSINGLE SKILLOr install a single skill
npx skills add microsoft/power-platform-skills --skill <name> --full-depthPick the skill name from the Skills tab — each entry there installs independently.
PLUGIN MARKETPLACEAdd the marketplace, 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 mcp-apps@power-platform-skillsTyped inside the agent's own prompt, not in a terminal. The marketplace lists 8 plugins; three are shown. Every one installs the same way, with its own name before @power-platform-skills.