ericrisco/rsc-harness / skills/power-automate
power-automate
VerifiedUse 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`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.3 KB |
| evals/README.md | markdown | 1.3 KB |
| evals/cases.yaml | config | 4.1 KB |
| references/dataverse-web-api.md | markdown | 7.3 KB |
| references/entra-auth-setup.md | markdown | 3.8 KB |
| references/flowstudio-mcp-and-limits.md | markdown | 3.6 KB |
evals/README.md
View on GitHub# Evals — power-automate
`cases.yaml` has three groups. `should_trigger` covers the programmatic operate cases: create+enable
via the Dataverse Web API, the My-Flows honesty question, enable-via-statecode, a Spanish
solution-aware CI deploy, FlowStudio-MCP run debugging, and a clientdata update. `should_not_trigger`
lists adjacent prompts owned by a named sibling — flow *design*/definition (automation-flows),
platform selection by billing (automation-strategy), generic typed-client engineering
(api-connector-builder), the inbound webhook receiver (webhooks), and direct Microsoft Graph
scripting (api-connector-builder, no first-party MS-Graph skill). `capability` is one end-to-end
lifecycle scenario whose `must_include` rubric checks the concrete API calls (token, POST, PATCH
statecode, DELETE), the string-encoded `clientdata`, the My-Flows/`api.flow.microsoft.com` honesty
limits, the ExportSolution-before-DELETE irreversibility rule, and the third-party FlowStudio-MCP
flag.
No automated runner. Score by judgement: feed each `should_trigger` / `should_not_trigger` prompt to
the routing layer and confirm it activates (or routes to the listed sibling); for `capability`, have
the skill produce the lifecycle walkthrough and check every `must_include` bullet by hand.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |