Power automate docs
Skill Wals-pro/claude-power-automate/skills/power-automate-docs
A Claude Code suite for Microsoft Power Automate development — Agent Skills + a local CLI (Dataverse/Power Platform APIs, Azure CLI auth, no stored secrets). Beta.
npx -y skills add Wals-pro/claude-power-automate --skill power-automate-docsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 8 stars8 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Navigate official Microsoft Power Automate and Power Platform documentation. Use when researching Power Automate capabilities, deciding whether a topic belongs to cloud-flow expressions, Power Fx desktop flows, Dataverse workflow APIs, connector references, limits, errors, or monitoring. Prefer this skill before using generic web search for Power Automate tasks.
SKILL.md
1.6 KB, as published. Nobody here has run it
Power Automate Docs
Use this as the documentation router for Power Automate work. Prefer official Microsoft Learn sources and local runbooks over third-party examples.
Procedure
- Classify the task:
- Cloud-flow JSON/API work: use Workflow Definition Language and Dataverse workflow docs.
- Desktop-flow formulas: use Power Fx desktop-flow docs.
- Connector/action configuration: use connector reference docs.
- Failed run/debugging: use error, limits, and run-history docs.
- Read
references/doc-map.mdfor the right source links and caveats. - If changing local artifacts, pair this with:
power-automate-api-clientfor pull/diff/deploy/status/runs,power-automate-expression-syntaxfor expressions,power-automate-action-configurationfor action payloads,power-automate-run-forensicsfor execution analysis,power-automate-referencefor the exact function/trigger/action namespace and the workflow-definition schema.
Rules
- Do not treat Power Fx as the default expression language for cloud flows.
- Do not use closed hosted MCP services as the source of truth.
- When information may have changed, verify against Microsoft Learn before editing code or workflows.