Use for Dataverse table METADATA - tables, columns, lookups/relationships, choices/option sets, alternate keys, main forms, public/lookup views, the form-level ribbon (RibbonDiffXml), form event handlers and script libraries, and table icons - plus up-front schema and query-shape design before metadata exists. Trigger on "create a table", "add a column/field", "add a lookup", "add a choice", "set an alternate key", "update the main form", "add a view / change view columns", "add a button to the form ribbon", "set the table icon", or "design a Dataverse schema", even when no helper is named. Prefer this over hand-edited customizations.xml. Not for row/record DATA, seeding config rows, or query authoring - use data-operations.
Use for solution-aware Power Automate cloud flows in Dataverse - create, update, inspect, lint, connector governance review, hardening review (retry/concurrency/pagination/idempotency/ error handling), HTTP-trigger callback URL resolution, run-history inspection (recent runs, status, errors, duration), and the environment variables flows read. Fires whenever the user mentions a cloud flow, Power Automate, a workflow record, flow connection references, a flow trigger URL or webhook callback, "lint my flow", "harden this flow", "review the connectors", "why did my flow change behavior", "show me the run history", "did the flow run", "why did my flow fail", or "check the recent runs", even if no helper is named. Patches only the changed `workflow` properties and blocks semantic drift (emptied branches, dropped switch cases, removed required actions) by default. Not for C# plug-ins or custom APIs - use plugins-server-extensions. Run the live-mutation preflight from the `powerplatform-core` orchestrator before any
Entry point and router for Microsoft Power Platform and Dataverse development. Use to discover repo context, choose the right development surface, and run the mandatory live-mutation preflight before any deploy/publish/import/registration/data-write. Start here when the request spans multiple areas, is ambiguous, or the repo shape is unknown, then DEFER to the matching domain skill for focused single-domain work (schema, data, flows, plug-ins, PCF/web resources, code apps, solution ALM, security roles, document generation, custom connectors, platform administration). Trigger when the user mentions Power Platform, Dataverse, Dynamics 365, Power Apps, Power Automate, model-driven apps, solutions, or the pac CLI without naming a specific asset - but let the domain skills lead on their specifics.
Use for Dataverse row/record DATA and queries - create, read, update, upsert, or delete rows, seed or sync reference/config data, and design and run queries. Trigger on "create a record/row", "read/retrieve this record", "get the value of a field on a row", "list/query the rows where", "how many rows match", "update this record", "upsert by alternate key", "delete this row", "seed config data", "import/sync these rows", "design an OData / FetchXML query", or "build the List rows filter for a flow", even when no helper is named. Covers keyed create/read/update/upsert/delete via the Dataverse SDK and query execution with bounded paging and total-count reporting, plus query design across OData, FetchXML, and Power Automate "List rows". Not for table/column/form/view/ribbon METADATA - use dataverse-schema.
Use for Power Platform TENANT and ENVIRONMENT administration - the tasks normally done in the Power Platform Admin Center, driven headlessly via the `pac admin` CLI and the Power Platform API. Covers listing environments, creating / resetting / backing-up / restoring / deleting environments, reading and writing tenant settings, data loss prevention (DLP) policies, managed environments, environment groups, application users / admin service principals, and capacity reporting. Trigger on "list the environments", "create / reset / delete / backup / restore an environment", "tenant settings", "DLP" / "data policy", "managed environment", "environment group", "Power Platform admin", "admin center", or "what environments are in this tenant", even when no helper is named. Admin-tier: it needs a Power Platform Administrator profile, distinct from the maker/developer Dataverse auth the other skills use. NOT for Dataverse data or solution ALM inside a single environment - use data-operations or solution-alm-delivery. Ru
Use for Dataverse server-side logic in C# - plug-ins and custom APIs. Covers headless first registration of a plug-in assembly or package, repeatable build-and-push, SDK message-processing step and image inspection, reconciling step enable/disable state to source intent, and creating a custom API with its request parameters and response properties. Fires whenever the user mentions a plug-in, plugin step, SDKMessage, pre/post image, plug-in assembly or package, "register my plug-in", "push the plug-in", "why is my step disabled", step-state drift, or a custom API / unbound action backed by a plug-in, even if no helper is named. Treats step enablement as explicit deployment state and registration as a separate approval gate. Not for Power Automate cloud flows - use power-automate-flows. Run the live-mutation preflight from the `powerplatform-core` orchestrator before any registration, push, or step-state write.
Use for Power Apps Code Apps - the pro-code model where a standalone Vite-built React/Vue/TS single-page app uses the `@microsoft/power-apps` client library and is pushed into a Power Platform environment with no server to manage. Covers scaffolding from the official Vite template, initializing with `power.config.json`, adding Dataverse data sources that generate typed model/service files, local dev, building, and pushing via `npx power-apps push` (npm CLI) or legacy `pac code push`. Trigger whenever the user mentions a code app, `power.config.json`, `@microsoft/power-apps`, `pac code` / `power-apps` CLI, a `CodeApp/` folder, or wants to build, run, or push a custom SPA into Power Platform, even if no helper is named. Not for PCF controls embedded in model-driven forms (use pcf-and-web-resources) or Canvas/maker apps.
Use to DESIGN Power Platform custom connectors and integration wrappers - review an OpenAPI/Swagger description, choose the auth shape (API key, OAuth2, basic, none), inventory operations, and decide whether to expose an API as a direct custom connector or behind an Azure Function / API facade. Produces a connector name, auth approach, operation summaries, a recommended pattern, suggested environment variables, and solution-aware connection-reference guidance. Trigger whenever the user mentions a custom connector, OpenAPI/Swagger for Power Platform, connecting a flow or app to an external/REST API, an integration wrapper or facade, or whether an Azure Function should front an integration, even if no helper is named. Design-first - it does not publish the connector. Not for authoring the flow that calls it (use power-automate-flows) or server-side Dataverse logic (use plugins-server-extensions).