Skip to content

ericrisco/rsc-harness / skills/power-automate

power-automate

Verified

Use when operating Microsoft Power Automate cloud flows from code — create, enable, update, list or delete via the Dataverse Web API (`workflow` table, category 5) with Entra ID OAuth2, plus run-history debugging. NOT designing the flow definition (that is `automation-flows`), NOT picking a platform by billing model (that is `automation-strategy`).

FileKindSize
SKILL.mdskill md12.3 KB
evals/README.mdmarkdown1.3 KB
evals/cases.yamlconfig4.1 KB
references/dataverse-web-api.mdmarkdown7.3 KB
references/entra-auth-setup.mdmarkdown3.8 KB
references/flowstudio-mcp-and-limits.mdmarkdown3.6 KB

evals/cases.yaml

View on GitHub
skill: power-automate

should_trigger:
  - prompt: "Create a Power Automate cloud flow via the Dataverse Web API and turn it on from my deploy script."
    why: Canonical programmatic operate — POST /workflows (category 5) then enable via statecode; the core deliverable.
  - prompt: "Why can't I edit my flow under 'My Flows' with the API? Every call I make fails."
    why: The load-bearing honesty limit — My Flows are not code-manageable; must route to the solution-aware answer.
  - prompt: "Enable my Power Automate flow by code — set statecode to 1 after I create it."
    why: Enable-via-statecode is the explicit lifecycle step new flows come up Off (0) and need PATCH to 1.
  - prompt: "Automatizar el despliegue de un flujo de Power Automate dentro de una solución de Dataverse desde CI."
    why: Spanish; solution-aware programmatic deployment with a service principal — squarely this skill.
  - prompt: "Use FlowStudio MCP to pull the action-level inputs and outputs of my flow's last failed run."
    why: MCP run-history debugging that the Dataverse API doesn't expose per action — the MCP path this skill owns.
  - prompt: "PATCH the clientdata of an existing workflow row to update the flow's definition."
    why: Update lifecycle against the workflow table, including the clientdata string-encoding concern.

should_not_trigger:
  - prompt: "Design a 'new Stripe payment → post to Teams' automation and give me the importable definition."
    route_to: automation-flows
    why: Designing what the flow does and authoring its definition is the design skill; this one operates a definition, it doesn't invent it.
  - prompt: "Should I use Power Automate or n8n for about 50k runs a month?"
    route_to: automation-strategy
    why: Platform selection by billing/constraints, not operating a live Power Automate flow.
  - prompt: "Write a typed TypeScript client for the Dataverse Web API with token refresh, pagination, and exponential backoff."
    route_to: api-connector-builder
    why: Generic client engineering (auth/pagination/retry) even though the API is Dataverse; this skill uses endpoints surgically, it doesn't build the client.
  - prompt: "Build the Express endpoint that receives my flow's HTTP-trigger POST and verifies it."
    route_to: webhooks
    why: Building the inbound receiver in your own app; this skill operates/triggers flows, it does not build the receiver.
  - prompt: "Send an email and read a calendar via Microsoft Graph from my Node backend."
    route_to: api-connector-builder
    why: Scripting Microsoft 365 via Graph directly is not a Power Automate flow; no first-party MS-Graph skill, so build a typed Graph client.

capability:
  - scenario: "User has an Entra app registration and wants to create an automated cloud flow inside a Dataverse solution, enable it, later update its definition, and finally remove it safely. Walk the full programmatic lifecycle."
    must_include:
      - "Acquire an Entra OAuth2 token from https://login.microsoftonline.com/{tenant}/oauth2/v2.0/token (client_credentials) with scope {PA_DATAVERSE_URL}/.default."
      - "POST /api/data/v9.2/workflows with category=5, type=1, primaryentity=\"none\", name, and clientdata as a STRING-encoded JSON (definition + connectionReferences), not a nested object."
      - "State the honesty limit: only flows inside a Dataverse solution are code-manageable; classic My Flows cannot be created or edited by code."
      - "New flow comes up statecode=0 (Off); enable with PATCH workflows({workflowid}) statecode=1 using If-Match: *; validate connection references resolve before enabling."
      - "Update via PATCH (send only changed fields), and note api.flow.microsoft.com is unsupported — use the Dataverse Web API or the Power Automate Management connector; flag api.powerplatform.com as an evolving alternative."
      - "Irreversibility rule: ExportSolution to a saved base64 zip BEFORE DELETE workflows({workflowid}) — deletion has no undo."
      - "For action-level run debugging use the third-party FlowStudio MCP (get_live_flow_run_action_outputs), flagged as NOT Microsoft-affiliated."
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall