microsoft/power-platform-skills
33 skills2.5k installs11.5k starsGitHub
Install
npx skills add https://github.com/microsoft/power-platform-skillsSkills in this repo
1Add SharepointAdd SharePoint is a Microsoft Power Platform skills agent reference for solo builders and consultants automating SharePoint list and column setup through the Microsoft Graph API. It assumes Azure CLI authentication: verify az account show, run az login if needed, then obtain an access token for graph.microsoft.com and attach Authorization and Content-Type headers on REST calls. The readme walks through resolving a SharePoint site URL into a site ID, reusable PowerShell functions such as Get-SiteId, and the header table teams need for create/list/update operations on SharePoint entities. Use it when an agent must add SharePoint backing storage for Power Apps, internal workflows, or migration scripts without clicking through the admin UI. Complexity is intermediate because tenant permissions, site collection rights, and Graph consent still require human setup. The skill pattern is integration with shell and network permissions for az and Graph HTTPS calls.107installs2Add DataverseAdd-dataverse is a reference-style agent skill for solo builders and small teams connecting custom agents, automation, or backends to Microsoft Dataverse without wrestling Power Platform auth. It documents how to confirm Azure CLI login, resolve your org’s Web API endpoint from make.powerapps.com developer resources, mint a bearer token scoped to that environment URL, and assemble OData 4.0 headers for JSON CRUD against /api/data/v9.2. The flow suits indie SaaS that syncs leads, tickets, or custom tables into Dynamics-backed data models, or agents that patch records during build iterations. It assumes you already have a Dataverse environment and appropriate Azure AD rights—not greenfield schema design. Pair it with Microsoft’s broader Power Platform skills when you move from auth wiring to entity modeling, plugins, or Power Apps UI.98installs3Create Code Appcreate-code-app is a prerequisite and workflow reference for standing up Microsoft Power Apps code apps with AI coding agents. It tells solo builders exactly which runtimes and accounts they need—Node 22 or newer, an enabled Power Platform tenant, a known environment GUID—and maps the Bash capabilities agents should request in plan mode so scaffolding, dependency install, production build, and power-apps init/list-connections/add-data-source steps succeed without blocked tools. The skill complements template-driven degit flows where the CLI arrives as an npm dependency rather than a manual global install. Use it when you are turning a spec into a deployable code app inside a governed enterprise environment but still want agent-driven iteration. It does not implement UI components; it ensures permissions, versions, and CLI verbs align so later skills can focus on features, connectors, and packaging.90installs4Add Office365Add Office 365 Outlook is an agent skill for Microsoft Power Apps code apps that walks you through registering the Office 365 connector, binding it to an existing environment connection, and folding the generated service into your build. It assumes you are already co-building in a Power Platform repo with Memory Bank discipline: check memory-bank.md, list connections for an API name containing office365, run the add-data-source command, then review generated service code, configure auth and usage, build, and sync Memory Bank. Solo and indie builders use it when a low-code or pro-code app must send mail, surface inbox data, or sync calendar events without hand-rolling Graph plumbing. The skill is user-invocable and expects shell access for the Power Apps CLI and routine repo edits for configuration and generated artifacts.87installs5Configure Canvas McpConfigure Canvas MCP is an agent skill that links Microsoft’s Canvas Authoring MCP server—which the Power Platform plugin registers automatically—to your live Power Apps canvas studio session. Builders invoke it when coauthoring MCP calls fail, the canvas-authoring server is not connected, or they need a first-time MCP bind after opening an app in make.powerapps.com. The flow enforces .NET 10 SDK or higher, then collects the studio URL from the browser so the configure tool can attach the session. It is narrowly scoped setup work for Claude Code and similar agents that expose the canvas-authoring MCP namespace, not a substitute for building screens or data models. Small teams benefit the same way solo builders do: one scripted checklist instead of guessing MCP registration versus session pairing.86installs6Generate Canvas Appgenerate-canvas-app is a deprecated Microsoft Power Platform agent skill that used to produce a complete Power Apps canvas application from natural-language direction. Solo and indie builders who automate citizen-developer workflows should not invoke it directly anymore: SKILL.md states it was replaced by the unified canvas-app skill, which handles both creating and editing canvas apps in one flow. When an agent still routes here, the expected behavior is to switch to /canvas-app, which detects an empty app and runs the full generation workflow. Tag it for discoverability and migration clarity, not as the primary path for new work. Pair it with current Power Platform documentation skills and canvas-app for end-to-end low-code delivery.81installs7Add McscopilotAdd Microsoft Copilot Studio is a Power Platform agent skill for solo and indie builders shipping Power Apps code apps who need Copilot Studio agents callable from app code. Install it when you are invoking agents, sending prompts, or surfacing agent responses inside a canvas or code-first app. The skill enforces a short ritual: check the memory bank, locate or create a Microsoft Copilot Studio connection, add the data source with the CLI, ask which agents and settings apply, then build and record updates. It sits in the build integrations lane because it is about wiring platform connectors—not writing marketing copy or production monitoring. Compared to ad-hoc Copilot REST experiments, this path keeps environment IDs, connection IDs, and plugin shared instructions aligned so the agent does not skip authentication or misname connectors.79installs8Activate Siteactivate-site packages the provisioning step for Power Pages as an executable Node workflow backed by shared validation helpers for auth tokens, cloud-to-API mapping, and HTTP. Solo builders automating Power Platform setups invoke it when they need a named site and subdomain bound to a specific organization and environment GUID, then wait on asynchronous Operation-Location polling rather than assuming instant readiness. Output is machine-readable JSON on stdout, which agent loops can branch on—success with siteUrl, failure with SubdomainConflict or HTTP status, or a running state after long polls. It sits early in a typical Microsoft stack: after environment selection and often alongside or before Dataverse modeling, and before PAC CLI code-site deploy. The skill readme is script-centric, so agents should treat CLI argument validation and token refresh as part of the integration contract, not optional niceties.78installs9Add Sample DataAdd Sample Data is a Power Platform reference skill for indie builders prototyping Dataverse-backed Power Apps or plugins who need repeatable seed scripts—not manual form entry. It encodes OData v9.2 patterns: resolve entity set names that differ from logical names, POST JSON bodies with correct field types, wire lookups, and capture OData-EntityId from responses. Authentication and retry live in a shared OData doc the agent must read first, which keeps token refresh consistent across Microsoft skills. Use it during Build when tables exist but screens and agents need realistic projects, accounts, or custom entities. It is phase-specific backend work; it does not replace production ETL or operate-time data migration governance.78installs10Deploy Sitedeploy-site is a workflow-oriented agent skill for Microsoft Power Pages developers who already have a code site repository and need to push it live with PAC CLI. It treats deployment as a gated sequence rather than a single command: confirm the PAC CLI plugin and version messaging, authenticate, validate the chosen Power Platform environment, then build and upload the site while surfacing blockers clearly. The skill is built for Claude Code-style agents that can run Bash, read project files, and ask the user targeted questions when credentials or environment IDs are ambiguous. Solo and indie builders on Power Pages benefit because it encodes Microsoft’s operational expectations—verify before act, never silently tweak tenant settings—and pairs naturally with sibling skills that provision Dataverse models or activate the site record first. Use it when the user asks to deploy, upload, or publish a code site, not when they are still designing tables or creating the website resource from scratch.78installs11Setup Datamodelsetup-datamodel is a reference-backed agent skill for defining Dataverse structure through the OData Web API at version 9.2. It encodes Microsoft’s preferred deep-insert pattern so agents create tables and columns in one round trip rather than chaining dozens of fragile requests. Solo builders on Power Pages or model-driven apps use it when requirements mention custom entities, lookups, or relationships that must exist before portals bind to data. The skill defers cross-cutting OData concerns—authentication, retries, HTTP semantics—to odata-common.md while this document holds copy-paste-ready EntityMetadata shapes with SchemaName, localized labels, and collection names. Intermediate complexity reflects Dataverse naming rules, solution prefixes, and error surfaces that punish small JSON mistakes. Chain it ahead of site activation or deploy when the product needs custom tables, not only standard entities.78installs12Add ExcelAdd Excel is a Power Platform agent skill for Power Apps code apps that need Excel Online (Business) as a data source. It targets solo builders shipping internal tools or lightweight SaaS-style apps on Power Apps who must bind OneDrive or SharePoint workbooks without guessing connector IDs or skipping project memory. The documented workflow starts by checking memory-bank.md, asks where the workbook lives, which file to use, and which tables to expose, then adds the connector using an existing connection from the list-connections skill or guides the user to create one in the right Power Apps environment. Configuration and build steps follow platform conventions in shared instructions and connector reference material. The skill is integration-focused: it orchestrates connector addition and setup rather than designing your entire data model or governance policy. Use it when your agent should read or write tabular Excel data from a code app and keep memory bank state aligned across sessions.77installs13Add Seoadd-seo is a Power Platform companion checker for solo builders using agent workflows on Power Pages code sites. It runs at the end of a session to confirm that basic technical SEO files landed under public/: robots.txt with crawler directives and a sitemap reference, plus sitemap.xml for URL discovery. If the project is not Power Pages or the session never touched SEO, it approves and exits so normal work is not blocked. When SEO work was attempted, missing or incomplete assets surface as explicit errors so you fix them before considering the site ready for search engines. Pair it with whichever skill or prompt actually authors those files; this package only enforces quality gates. Ideal when you want repeatable Launch-phase hygiene on Microsoft’s stack without manually re-reading every public asset after each agent run.77installs14Create WebrolesCreate Webroles is a small Node.js generator for Microsoft Power Pages code sites. It is aimed at solo builders and small teams who manage Power Platform sites as code and need repeatable web-role definitions instead of hand-editing YAML. You invoke it when you are adding or splitting roles for anonymous versus authenticated visitors and want a valid file name, UUID, and schema-ready YAML in the project’s web-roles folder. The script enforces prerequisites: both project root and role name are required, and it refuses to run if the web-roles directory is missing—typically because the environment has not been deployed yet. Output is machine-friendly JSON for chaining into other automation or agent steps. It does not design your permission model or table security; it only materializes one role file. Pair it with broader Power Platform skills for connectors, pages, and deployment when you are building a full portal.77installs15Deploydeploy is a workflow skill for solo builders maintaining Microsoft Power Apps code apps in-repo. It standardizes how an agent prepares a release: read optional memory-bank.md for project and environment context, run npm run build, verify dist/ includes index.html, ask for explicit approval before touching the live environment, then run npx power-apps push and record outcomes back into the memory bank. Build failures such as unused imports get targeted fixes; other TypeScript errors halt the pipeline so broken bundles never ship. The skill fits the moment you move from Validate/Build iterations to a real environment update, and again whenever you operate production after fixes or features. It assumes the Power Apps CLI toolchain and npm scripts are already configured in the project—agents orchestrate commands and guardrails, not substitute for tenant admin setup.77installs16Integrate Webapiintegrate-webapi is a Build-phase validation skill for Microsoft Power Pages code apps where agents generate TypeScript clients and services against the platform Web API. After integration work, it checks that a shared API client exists, that at least one service module was created, and that those modules reference /_api/ paths so calls align with Dataverse and Power Pages conventions. It skips validation when no integration artifacts are present, avoiding noise on unrelated edits. When integration was the goal, missing clients, empty service folders, or API-free services produce clear blockers. Solo builders use it to stop half-finished agent output from merging—especially when prototyping portals that read and write business data through authenticated platform endpoints rather than ad-hoc fetch snippets scattered in components.77installs17Setup Authsetup-auth is a Microsoft Power Platform companion skill aimed at solo and indie builders who automate Power Apps and connector workflows through an agent. It focuses on establishing a trusted CLI authentication session so later skills can list connections, add data sources, and operate against the correct environment without repeated manual sign-in failures. Use it at the start of a Power Platform automation session or whenever tokens expire and Bash-backed skills start failing with auth errors. For builders shipping low-code extensions or code apps that talk to Dataverse and connectors, treating auth as an explicit skill step reduces friction compared to debugging opaque non-zero exits mid-task. Prism lists it as part of the curated power-platform-skills chain rather than a general OAuth guide.77installs18List Connectionslist-connections is an agent skill for solo builders shipping Power Apps code apps who need real Connection IDs from the tenant before adding a connector. The skill runs the Power Apps CLI to enumerate connections in the configured environment, presents the list for copy into subsequent CLI flags, and walks through creating a new connection in the maker portal when the target connector is absent. It assumes haiku-class models for cost-efficient listing and defers cross-cutting Windows CLI and memory-bank guidance to shared-instructions in the plugin root. Authentication gaps trigger browser login rather than opaque failures, with explicit STOP rules on other non-zero exits. For indie teams automating low-code delivery through agents, this skill closes the gap between documentation and the exact identifier required on the command line.76installs19Add ConnectorAdd Connector is a Microsoft Power Platform skill for solo builders and citizen developers extending Power Apps code apps with external services. It follows a repeatable ritual: load project context from memory-bank.md, name the connector (or ask), add it through the platform tooling, inspect generated bindings, configure operations, run a build, and persist decisions back to the memory bank. Prefer narrower skills when they exist—Dataverse, Teams, SharePoint, and similar—to avoid guesswork. This generic path still leans on list-connections patterns and official connector catalogs so agents do not hallucinate unsupported APIs. Intermediate users already in a Power Apps code app repo with power.config.json and an environment ID benefit most. It is integration glue, not a replacement for licensing, DLP policies, or solution architect review in enterprise tenants.75installs20Add TeamsAdd Teams is a focused Microsoft Power Platform skill for solo builders who need Teams messaging or channel posts from a Power Apps code app. It mirrors the standard connector ritual: confirm memory-bank.md context, obtain a Teams connection ID through list-connections or the make.powerapps.com connections page for your environment, run the power-apps CLI to register Teams as a data source, ask which operations matter—such as posting to a conversation—and complete a build before updating the memory bank. It is narrower than add-connector and should be chosen whenever Teams is the target integration. You still need appropriate tenant permissions and an existing or creatable Teams connection. The skill is procedural for agents with Bash and edit access, not a substitute for Teams app policies or admin approval workflows in locked-down organizations.75installs21Create SiteCreate Site is a Power Platform agent skill for solo builders spinning up a new code app from a known Angular scaffold instead of hand-copying angular.json and folder layout. It targets the Build phase when you already chose Power Apps and need a named site slug, source roots, and build/serve architect blocks wired for production hashing versus dev source maps. The readme material is essentially the application blueprint: projectType application, prefix app, assets from public, and dual configurations so your agent can run serve in development and ship a bounded production bundle. Use it once per new site before you route users through add-datasource or custom components. It does not pick connectors, Dataverse tables, or auth—that comes next. For Prism shoppers comparing paths, this is scaffolding glue in the Microsoft power-platform-skills family, not a generic Next.js or Vercel starter. Intermediate familiarity with Angular CLI concepts helps even though the agent does the file generation.75installs22Add DatasourceAdd Data Source is a router agent skill in Microsoft's power-platform-skills pack for solo builders wiring Power Apps code apps to real data without memorizing connector taxonomy. It follows shared cross-cutting instructions, optionally loads memory-bank context, and starts from the user's outcome—search company info, manage tasks, send messages—then maps that intent to Dataverse, SharePoint, or other appropriate connectors with a short rationale. That makes it ideal when you already ran create-site and need the next integration step but do not want to mis-pick a premium connector. The workflow explicitly supports skipping the discovery question when arguments are already provided, then delegates to specialized child skills via the Skill tool. It is user-invocable and tuned for Sonnet-class agents with broad repo and shell permissions, so you should run it in a trusted app repo. It does not replace security review of connection strings, environment permissions, or ALM pipelines—those remain your Operate and Ship concerns after the datasource is attached.74installs23Add Azuredevopsadd-azuredevops is a Microsoft Power Platform agent skill that adds the Azure DevOps connector to a Power Apps code app and walks through memory-bank checks, connection discovery, CLI data-source registration, a mandatory HttpRequest fix, configuration, build, and memory-bank updates. Solo builders and small teams building on Power Apps use it when work items, bug creation, pipeline management, or raw ADO REST calls must live inside the app—not as a one-off script. The skill assumes an active Power environment (from `power.config.json` or context), existing or creatable connections in the Power Apps maker portal, and familiarity with shared plugin instructions. It is integration-first procedural knowledge, not a standalone ADO client; success means a wired connector and corrected request layer ready for feature code.73installs24Add Onedriveadd-onedrive is a Microsoft Power Platform skill that walks your agent through adding the OneDrive for Business connector to a Power Apps code app. Solo builders automating document workflows—uploads, downloads, folder listing, or file creation—need a repeatable sequence instead of guessing Power CLI flags or connection GUIDs. The workflow starts by checking memory-bank.md, then resolves an existing OneDrive connection via the list-connections skill or sends the builder to the environment-specific Connections URL to create one. The agent runs power-apps add-data-source with the onedriveforbusiness alias, configures operations with the user, implements app logic, and updates the memory bank so later sessions stay consistent. It references shared-instructions for cross-cutting concerns and connector-reference for ID lookup patterns. Install when you are in Build integrating Microsoft 365 storage, not when you only need a static mock UI without real files.73installs25Audit Permissionsaudit-permissions is a Microsoft Power Platform agent skill aimed at reviewing and understanding permission assignments across your tenant, environments, and solutions. Solo and indie builders shipping low-code apps often inherit broad admin roles or shared service principals; this skill gives your coding agent a focused playbook to surface risky grants before users touch production data. Install it when you are hardening a Power Apps rollout, preparing for security questionnaires, or reconciling connector identities after a merge from dev to test. It sits in the Ship phase under security because the payoff is confidence at launch—not ideation or growth experiments. Published metadata in the catalog is thin relative to sibling skills; pair it with list-connections, environment docs, and your own org policy. After audits, typical next steps are remediation in the admin center, updating memory-bank notes for the app, and re-running checks when you add new data sources or shared teams.73installs26Test Sitetest-site is an agent skill for Microsoft’s Power Platform stack that exercises a deployed, activated Power Pages site at runtime using Playwright MCP tools. Solo builders and citizen developers use it when they want to verify, smoke-test, or audit a live portal after deployment: open the site URL, walk pages, follow internal links, watch network traffic for API failures, and capture evidence such as screenshots and console messages. The workflow assumes prior deploy and activation steps in the same plugin family, which keeps it anchored on the Ship testing shelf rather than greenfield Build frontend work. It is user-invocable with an argument hint for site URL and targets Opus-class models for multi-step browser tasks. Installers should confirm plugin version output and treat browser automation as privileged; use Prism’s Security Audits panel before enabling MCP Playwright in production tenant contexts.72installs27Add Data SourceAdd Data Source is a Microsoft Power Platform agent skill for solo builders extending canvas apps with new business data. Because Power Apps requires human action in Studio for connections, the skill does not pretend to automate provisioning; it classifies what the user asked for, gives Studio steps, and uses MCP canvas-authoring tools to confirm the source or API appears. It fits the Build phase when you need SharePoint lists, Dataverse tables, SQL, Excel on OneDrive, or connector APIs available to formulas and controls. Triggers include phrases like add a connection, connect to Dataverse, or add an API. Skip it when you only need to enumerate what is already wired—those calls should go straight to list_data_sources or list_apis per the skill guardrails.68installs28Add Cloud Flowadd-cloud-flow enables developers to connect, configure, and orchestrate cloud services and data flows visually. Solo builders use it when integrating multiple cloud platforms or automating workflows between backend systems. It matters because it reduces the complexity of managing cloud infrastructure and service-to-service communication, letting you focus on business logic instead of plumbing.64installs29Generate Mcp App Uigenerate-mcp-app-ui is a Microsoft Power Platform agent skill that turns a described visual plus verified MCP tool output into a focused MCP App widget—self-contained HTML that renders inside chat conversations. Solo builders shipping custom MCP tools use it when a JSON dump is not enough and they need charts, comparison tables, maps, or other Fluent-themed views without hand-writing ext-apps boilerplate. The skill explicitly blocks generation until you supply real test output or a schema, which avoids broken widgets from invented fields. It leans on bundled references for MCP Apps technical patterns and design-guidelines theme tokens, and supports user invocation with argument hints for what the widget should display. Best fit for indie agents extending Power Platform or generic MCP stacks where tool calling is already working and the gap is presentation.63installs30Integrate BackendThis skill analyzes your backend integration needs and recommends the right approach—Web API for straightforward data operations, Server Logic for server-side processing and secure business rules, Cloud Flows for async background work, or combinations when needed. Use it when deciding how to connect a Power Pages site to backend systems, databases, or services. It matters because choosing the right backend architecture upfront saves rework and ensures security, performance, and maintainability.63installs31Add Server Logicadd-server-logic is a Microsoft Power Platform agent skill aimed at solo builders and citizen developers who have outgrown button-and-formula apps and need real server-side behavior. Prism lists it for the Build phase when you extend Dataverse, Power Apps, or related cloud components with plugins, automated actions, or integration hooks that must run reliably on the platform rather than in the user’s browser. The public skills.sh entry confirms it as part of the curated microsoft/power-platform-skills bundle, so agents can pull consistent procedural steps alongside sibling skills for tables, apps, and deployment. Because full SKILL.md body was not inlined in the ingest snapshot, treat descriptions here as name- and publisher-aligned guidance and validate steps in the GitHub source before production tenants. Use when your indie CRM, ops tool, or internal SaaS on Power Platform needs validated writes, external system calls, or reusable server routines your canvas app cannot express safely alone.61installs32Canvas AppCanvas App is a Microsoft skill that drives Power Apps canvas authoring through an MCP coauthoring session. Indie builders and small teams use it when they want to generate a new canvas app from requirements or update screens and logic without hand-editing every control. After sync, the skill chooses CREATE mode for empty apps—wizard plus parallel builders—or EDIT mode for existing apps, splitting small inline changes from complex multi-screen work that needs a planner. It expects agent tooling already wired to canvas-authoring MCP and typical repo operations. Best when you live in Power Platform and want agent-assisted .pa.yaml and app structure changes; less ideal if you are building a custom React SaaS with no Microsoft stack.55installs33Edit Canvas AppEdit Canvas App is a Microsoft Power Platform agent skill for solo builders and small teams who already have a canvas app or pa.yaml and need reliable, incremental changes without breaking studio sync. You invoke it when the user asks to modify, update, or edit an existing Canvas App. The workflow deliberately separates quick formula or property tweaks from heavier structural work: simple paths stay inline, while multiple screens, new screens, or new data sources trigger specialist sub-agents. Every run starts by carving out a dedicated kebab-case folder, syncing the live app into that directory via MCP, then editing and compiling from there so file operations stay scoped and reviewable. It pairs well with Claude Code or any agent that exposes the canvas-authoring MCP tools, and it assumes you are comfortable with Bash folder setup and YAML-first canvas source rather than clicking only in the maker portal.34installs