Builder Skills

Every skill an AI Builder uses to close the loop — from picking up a work item or bug in Azure DevOps, to building across the whole Power Platform, to shipping it back. The commands are the same whether you drive them from Claude Code or GitHub Copilot; only the way you install them differs.
On this page
▶ Watch — the Power Platform AI skills in a few minutes

Skills & plugins — the 30-second model

  • A skill is a single job your agent knows how to do the right way — e.g. /create-flow builds a Power Automate cloud flow; /dv-metadata creates Dataverse tables and columns.
  • A plugin bundles the skills for one product (Dataverse, Power Pages, Power Automate…). You install the plugins you need; you only pay context for the skill you actually invoke. A few capabilities (like Azure DevOps) come as MCP servers instead — same idea, added as a server.
  • The commands are the same in every AI client. How you install each plugin differs by client (Claude Code vs GitHub Copilot) — that's covered in the setup guides.

The catalog

Dataverse GA 8 skills

Reads your real schema through the Dataverse MCP and manages the full lifecycle via the Python SDK, PAC CLI + Web API — schema, data, solutions, security, and environment admin.

View on GitHub ↗
/dv-adminEnvironment-level Dataverse administration — bulk delete, retention/archival, organization settings, OrgDB settings, recycle bin, audit, and the 37 allowlisted PPAC toggles.
/dv-connectOne-step setup for a Dataverse environment — installs tools, authenticates, registers the MCP server, and writes `.env`.
/dv-dataRecord-level CRUD and bulk operations via the Python SDK — create, update, delete, upsert, CSV import, multi-table foreign-key loads, AI-generated sample data.
/dv-metadataDataverse schema authoring via the Python SDK and Web API — tables, columns, relationships, forms, and views.
/dv-overviewTool routing and cross-cutting rules for Dataverse work — which skill applies to which task, environment-confirmation, and pull-to-repo.
/dv-queryBulk reads, multi-page iteration, and analytics over Dataverse data via the Python SDK and Web API.
/dv-securitySecurity-role assignment, user access, application users, business units, and admin self-elevation in Dataverse environments.
/dv-solutionDataverse solution lifecycle — create, export, import, promote across environments, and validate deployments.
Power Pages GA 28 skills

Code-first Power Pages Code Sites — SPAs built with React, Angular, Vue, or Astro and wired to Dataverse. Covers the full lifecycle from data model to ALM pipelines and deployment. (Code Sites only — not classic Liquid portals.)

View on GitHub ↗
/activate-siteActivates and provisions a Power Pages website in a Power Platform environment via the Power Platform REST API.
/add-ai-webapiIntegrates Power Pages generative-AI summarization APIs (PREVIEW) into a Single Page Application (SPA) site — the Search Summary API and the Data Summarization API — on any record-detail or list page.
/add-cloud-flowIntegrates Power Automate cloud flows into a Power Pages site.
/add-sample-dataPopulates Dataverse tables with sample records for testing and demoing a Power Pages site.
/add-seoAdds SEO essentials to a Power Pages code site, including robots.txt, sitemap.xml, meta tags, Open Graph tags, and favicon configuration.
/add-server-logicCreates, edits, and manages Power Pages Server Logic files — server-side JavaScript that runs securely on the Power Pages runtime.
/audit-permissionsAudits existing table permissions on a Power Pages site by analyzing them against site code and Dataverse metadata.
/configure-env-variablesConfigures environment variables for Power Pages site settings to support ALM across environments.
/create-siteCreates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro.
/create-webrolesCreates and configures web roles for a Power Pages code site.
/deploy-pipelineTriggers a Power Platform Pipeline deployment run for a Power Pages solution.
/deploy-siteDeploys an existing Power Pages code site to a Power Pages environment using PAC CLI.
/diagnose-deploymentSurfaces PAC CLI upload errors and Dataverse async operation errors, pattern-matches against a known failure catalog, and optionally auto-fixes identified issues.
/export-solutionExports a Dataverse solution containing Power Pages site components as a zip file, ready for deployment to another environment.
/import-solutionImports a Dataverse solution zip into a target environment, with optional staged import for dependency checking before committing.
/integrate-backendAnalyzes the user's business problem and recommends the right backend integration approach — Web API, AI Web API (generative summaries / grounded search), Server Logic, Cloud Flows, or a combination — for a Power Pages site, then routes to the appropriate specialized skill.
/integrate-webapiIntegrates Power Pages Web API into a site's frontend code with proper permissions and deployment.
/manage-firewallInspects and configures the web application firewall (WAF) in front of a Power Pages production site.
/manage-headersInspects and configures the security headers a Power Pages site sends to browsers — Content Security Policy, frame and clickjacking protection, cross-origin sharing, cookie behavior, and related site settings.
/plan-almCreates an ALM (Application Lifecycle Management) plan for deploying a Power Pages site across environments.
/scan-codeScans a Power Pages site project for security issues in source code and dependencies.
/scan-siteRuns a security scan on a deployed Power Pages site, fetches the latest scan report, and produces a plain-language summary.
/security-reviewRuns a guided, end-to-end security review of a Power Pages site and consolidates every finding into one HTML report covering source code and dependencies, the live site, browser headers, firewall, authentication, and role-based permissions.
/setup-authUse when the user asks to "set up authentication", "add login", "add logout", "add sign in", "enable auth", "add role-based access", "add authorization", "protect routes", "configure identity provider", "configure Entra ID", "configure Entra External ID", "configure OpenID Connect", "add OIDC", "set up SAML", "set up WS-Federation", "set up local login", "add username password", "add Facebook login", "add Google sign in", "add Microsoft Account", "set up invitation login", or otherwise wants to set up authentication (login/logout) and role-based authorization for their Power Pages code site using any supported identity provider (Microsoft Entra ID, Entra External ID, OpenID Connect, SAML2, WS-Federation, local authentication, Microsoft Account, Facebook, or Google).
/setup-datamodelCreates Dataverse tables, columns, and relationships for a Power Pages site based on a data model proposal.
/setup-pipelineSets up a Power Platform Pipeline for automated Power Pages deployments.
/setup-solutionCreates a Dataverse publisher and solution, then adds Power Pages site components to the solution for ALM and deployment management.
/test-siteTests a deployed, activated Power Pages site at runtime using browser-based navigation, page crawling, and API request verification via Playwright.
Canvas Apps GA 3 skills

Generates and edits .pa.yaml — the source-controllable Canvas representation — via the Canvas Authoring MCP.

View on GitHub ↗
/canvas-appCreates or edits a Power Apps Canvas App through the Canvas Authoring MCP coauthoring session.
/configure-canvas-mcpConfigure the Canvas Authoring MCP server for the current coauthoring session.
/generate-canvas-app[DEPRECATED — use canvas-app instead] Generate a complete Power Apps canvas app.
Power Automate ✨ New GA 9 skills

Build, edit, run, and debug cloud flows in natural language — powered by the FlowAgent MCP server. Also manages Power Automate Desktop (RPA) flows.

View on GitHub ↗
/browse-flowsBrowse Power Automate environments and flows interactively.
/build-flowAutonomously build a complete Power Automate flow from a description.
/create-flowGuided flow creation wizard.
/debug-flowDebug a failed Power Automate flow run.
/diagnose-flowDeep autonomous diagnosis of a failed flow run.
/manage-desktop-flowsManage and run Power Automate Desktop (RPA) flows and machine groups.
/manage-flowsManage flow lifecycle - publish, test, batch operations, inventory reports.
/route-environmentsManage environment resolution — check which environment you create flows in by default, list available environments, and set your working environment.
/setupSet up Power Automate CLI prerequisites.
Model-Driven Apps GA 1 skill

Generative pages — React + Fluent UI v9 pages that live inside model-driven apps.

View on GitHub ↗
/genpageCreates, updates, and deploys Power Apps generative pages for model-driven apps using React v17, TypeScript, and Fluent UI V9.
Copilot Studio ✨ New 🟡 Preview 22 skills

Author Copilot Studio agents as YAML — create, edit, validate, and test agents, topics, actions, knowledge sources, and evals from your coding agent. Agent-orchestrated (you describe what you want in natural language). From Microsoft's Copilot Studio CAT team.

View on GitHub ↗
add-actionGuide users through adding a new connector action to a Copilot Studio agent.
add-adaptive-cardGenerate and insert an Adaptive Card into a Copilot Studio topic using AdaptiveCardPrompt.
add-generative-answersAdd generative answer nodes (SearchAndSummarizeContent or AnswerQuestionWithAI) to a Copilot Studio topic.
add-global-variableAdd a global variable to a Copilot Studio agent.
add-knowledgeAdd a knowledge source (public website or SharePoint) to a Copilot Studio agent.
add-nodeAdd or modify a node in an existing Copilot Studio topic.
add-other-agentsAdd child agents, connected agents, or other multi-agent patterns to a Copilot Studio agent.
analyze-evalsAnalyze exported evaluation results from Copilot Studio's Evaluate tab.
chat-with-agentDEPRECATED: Use /copilot-studio:detect-mode then /copilot-studio:chat-directline or /copilot-studio:chat-sdk instead.
clone-agentClone a Copilot Studio agent from the cloud.
create-evalCreate plugin development eval scenarios (JSON files with natural prompts and deterministic checks for testing plugin skills).
create-eval-setCreate a test set CSV file for import into Copilot Studio's in-product Evaluate tab.
edit-actionEdit an existing action (TaskDialog) in a Copilot Studio agent.
edit-agentEdit Copilot Studio agent settings, instructions, or configuration.
edit-triggersModify topic triggers — trigger phrases and model description.
list-topicsList all topics in the Copilot Studio agent with their trigger types, phrases, and action counts.
manage-agentPush/pull Copilot Studio agent content via the VS Code extension's LanguageServerHost LSP binary.
new-topicCreate a new Copilot Studio topic YAML file.
run-evalRun evaluations against a Copilot Studio agent via the Power Platform Evaluation API.
run-tests-kitRun a batch test suite via the Copilot Studio Kit (Dataverse API).
test-authAuthenticate for Copilot Studio evaluation API and SDK chat.
validateValidate Copilot Studio agent YAML files using the LSP binary's full diagnostics (YAML structure, Power Fx, schema, cross-file references).
Code Apps 🟡 Preview 13 skills

A React + Vite + Fluent UI v9 surface with one skill per connector — scaffold the app, add typed connector services, then build & deploy.

View on GitHub ↗
/add-azuredevopsAdds Azure DevOps connector to a Power Apps code app.
/add-connectorAdds any Power Platform connector to a Power Apps code app.
/add-datasourceAdds a data source or connector to a Power Apps code app.
/add-dataverseAdds Dataverse tables to a Power Apps code app with generated TypeScript models and services.
/add-excelAdds Excel Online (Business) connector to a Power Apps code app.
/add-mcscopilotAdds Microsoft Copilot Studio connector to a Power Apps code app.
/add-office365Adds Office 365 Outlook connector to a Power Apps code app.
/add-onedriveAdds OneDrive for Business connector to a Power Apps code app.
/add-sharepointAdds SharePoint Online connector to a Power Apps code app.
/add-teamsAdds Microsoft Teams connector to a Power Apps code app.
/create-code-appCreates Power Apps code apps using React and Vite.
/deployBuilds and deploys a Power Apps code app to Power Platform.
/list-connectionsLists Power Platform connections in the current environment.
Mobile Apps ✨ New GA 17 skills

Build and deploy native mobile Power Apps with device capabilities and full offline support.

View on GitHub ↗
/add-connectorUse when the user wants to add a Power Platform connector to a mobile app and there is no dedicated /add-* skill for that connector (Dataverse and SharePoint have their own skills).
/add-datasourceUse when the user wants to add a data source to a mobile app but hasn't said which kind (Dataverse table, SharePoint list, or other connector).
/add-dataverseUse when the user wants to add Dataverse tables (existing or new) to a Power Apps mobile app, extend an existing Dataverse table with new columns, or apply an approved data model plan.
/add-nativePublic entry point for native device capabilities and native controls — camera, image picker, barcode/QR scanner, document picker, file picker, secure storage, file system, sharing, PDF generation/viewing, pen/signature capture, background GPS/geolocation tracking, or supported local file workflows — in a Power Apps mobile app.
/add-sample-dataUse when the user wants to seed Dataverse tables with realistic sample records so a freshly-scaffolded code app shows real-looking data on first launch.
/add-sharepointUse when the user wants to read or write SharePoint lists, manage documents in a SharePoint document library, or create a new SharePoint list from a Power Apps mobile app.
/create-mobile-appUse when the user wants to start a new Power Apps mobile app (Expo / React Native / TypeScript, targeting iOS and Android) from scratch.
/debug-appUse when the user has finished building a mobile app, started it with `npm run dev`, and wants the running app monitored for runtime errors AND silent failures (empty lists, blank screens, swallowed network errors) and fixed autonomously.
/deployUse when the user wants to deploy / publish / push a Power Apps mobile app to a Power Platform tenant so others can run it.
/design-systemCreates and manages the brand design system for a Power Apps mobile app.
/edit-appUse when the user wants to iterate on an existing generated Power Apps mobile app after /create-mobile-app: update the plan, data model, native capabilities, design, screens, generated app code, and preview without restarting the full project flow.
/list-connectionsUse when the user asks to find, create, or look up a Power Platform connection ID or connection reference for the current environment.
/open-wrap-urlUse when the user wants to open the Power Apps Wrap page for an app ID in the active environment.
/preview-screensUse when the user wants to preview generated screens in a browser without starting Metro / a simulator — for example after /create-mobile-app finishes or after /edit-app regenerates a screen.
/set-app-registration-nativeUse when the user wants to wire a Power Apps Wrap mobile app to an Entra ID app registration by opening the Power Apps Wrap app-registration page, pasting the resulting client ID, and updating auth.config.json.
/setup-datamodelUse when the user wants to design or redesign the Dataverse schema and connector plan for an existing mobile app, or has an ER diagram (image, Mermaid, or text) to apply.
/setup-offline-profileUse when the user wants to enable offline mode for a Power Apps mobile app and create a Mobile Offline Profile in Dataverse — designs per-table row scope, relationships, columns, and sync frequency through a 3-gate approval flow.
MCP Apps ✨ New GA 1 skill

Generate interactive MCP App widgets — rich UI surfaces for your MCP tools.

View on GitHub ↗
/generate-mcp-app-uiGenerate an MCP App widget (self-contained HTML) for an MCP tool.
Microsoft Docs GA 3 skills

Grounds the agent in official Microsoft Learn documentation — verify API signatures, fix SDK errors, and pull current code samples.

View on GitHub ↗
/microsoft-code-referenceFind working code samples, verify API signatures, and fix Microsoft SDK errors using official docs.
/microsoft-docsUnderstand Microsoft technologies by querying official documentation.
/microsoft-skill-creatorCreate agent skills for Microsoft technologies using official documentation.
Azure DevOps ✨ New MCP server 8 skills

The intake-and-delivery hub that closes the loop. An MCP server (not slash commands) — your agent calls it in natural language to pull the work item or bug it needs to fix, browse repos and pull requests, run and check pipelines, and manage wikis and test plans. Works in Claude Code and GitHub Copilot.

View on GitHub ↗
work itemsRead, create, and update Azure Boards work items and bugs — the task your agent starts from.
boards & iterationsQuery boards, sprints, iterations, and team assignments.
repositoriesBrowse Azure Repos, branches, and file contents.
pull requestsList, review, comment on, and manage pull requests.
pipelinesTrigger builds and read pipeline and run status.
wikisCreate, update, and retrieve project wiki pages.
test plansList and manage test plans, suites, and cases.
searchSearch code, work items, and wikis across the organization.

Start with Dataverse + Microsoft Docs, then add the asset-type plugins as the work demands. Each plugin you skip is one fewer thing competing for context in your session.

Installing them — pick your AI client

The skills above are identical across clients. What changes is the install command and how the MCP servers get wired. Full step-by-step setup lives inside the Inner Circle:

New here? Start with the free choose-your-tool overview to pick a client, then follow its setup guide.

Put it together — one real loop

A bug fix that never opens a maker portal, a DevOps board, or a browser. This is one continuous conversation inside your AI client — the agent calls the Azure DevOps MCP tools and the Power Platform skills for you. Real tool names, real skills:

your AI client · one session
YouList the bugs assigned to me in Azure DevOps.
→ azure-devops · wit_my_work_items { types: ["Bug"], state: "Active" }
↳ 2 bugs. #4821 — “High-priority work orders save as Medium” · Sev 2 · Active
YouOpen #4821 and tell me what's going on — don't change anything yet.
→ azure-devops · wit_get_work_item { id: 4821 }
↳ Repro: set Work Order Priority = Critical, save → it saves as Medium. Environment: dev.
→ dv-query · read fs_workorder + the “WO – Set Defaults” flow (Dataverse MCP, dev)
↳ The fs_priority global choice has no “Critical” value, and the default flow forces Priority = Medium on create.
Here's my plan — approve before I touch anything:
  1. Add “Critical” (value 4) to the fs_priority global choice — /dv-metadata
  2. Guard “WO – Set Defaults” to set Priority only when it's empty — /build-flow
  3. Bundle into the FieldService solution, deploy to QA, resolve the bug.
YouLooks right. Go.
→ /dv-metadata — add “Critical” option to fs_priority
→ /build-flow — edit trigger condition: run only when Priority is blank
↳ Applied and validated on dev — 1 choice option, 1 flow updated.
YouShip it to QA and close the bug.
→ /dv-connect — switch to the QA environment
↳ Connected: FieldService-QA (…/fs-qa.crm.dynamics.com).
→ /dv-solution — export FieldService from dev, import (managed) to QA
↳ FieldService 1.4.2 imported to QA · publish complete.
→ azure-devops · wit_update_work_item { id: 4821, State: "Resolved" }
→ azure-devops · wit_add_work_item_comment { id: 4821, text: "Added Critical option + guarded default flow. Deployed FieldService 1.4.2 to QA." }
↳ Bug #4821 → Resolved.

That's the loop — intake → plan → build → ship → close — and every step ran in the client. You never left the conversation.

Run the whole loop 🔁

Go from work item to shipped — we'll set it all up with you.

The catalog shows what exists. Inside the Inner Circle you get the how: the install-and-connect guide for each AI client (including Azure DevOps + Copilot Studio), the plugin tours, copy-paste config and templates, all 13 book chapters, and the monthly live build calls where we run loops like the one above together.

Join The Inner Circle →

Already a member? Sign in →