agentsclimarketplace

Power automate workflow patterns

Skill Wals-pro/claude-power-automate/skills/power-automate-workflow-patterns

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.

Install
npx -y skills add Wals-pro/claude-power-automate --skill power-automate-workflow-patterns

Assembled 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

Design or modify Microsoft Power Automate cloud-flow architectures using proven workflow patterns. Use when building flows, choosing triggers/actions, structuring branches/scopes, adding SharePoint/Outlook/Dataverse automation, handling retries and errors, or translating n8n-style workflow routines into Power Automate without reinventing the process.

SKILL.md

1.6 KB, as published. Nobody here has run it

Power Automate Workflow Patterns

Use this before designing or restructuring a Power Automate cloud flow. It adapts n8n-style workflow discipline to Power Automate concepts.

Pattern Workflow

  1. Pick the pattern from references/cloud-flow-patterns.md.
  2. Identify trigger, data source, transformation, action, and observability points.
  3. Keep solution-aware flows versioned through local artifacts.
  4. Use power-automate-action-configuration for connector payloads.
  5. Use power-automate-expression-syntax for conditions and dynamic content.
  6. Use power-automate-api-client for pull/diff/deploy/verify.
  7. Use power-automate-reference to confirm trigger/action type values and keep expressions inside the real WDL function namespace.

Design Rules

  • Prefer small, explicit branches over dense nested expressions.
  • Use scopes to group transactional steps and error handling.
  • Make connector boundaries visible: SharePoint lookup, Outlook send/draft, Dataverse write, HTTP call, etc.
  • Add observable evidence for critical paths, such as log rows or status updates, when the business process needs auditability.
  • Keep customer-facing send paths testable without sending directly from Claude.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.