agentsclimarketplace

Manage flows

Skill LeonardSEO/power-platform-skills-codex/plugins/power-automate/skills/manage-flows

Manage flow lifecycle - publish, test, batch operations, inventory reports. Use when the user asks to publish, test, batch manage, or get an inventory of flows.From its SKILL.md

Install
npx -y skills add LeonardSEO/power-platform-skills-codex --skill manage-flows

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

  • 1 stars1 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.

SKILL.md

3.7 KB, 469 tokens by cl100k_base, as published. Nobody here has run it

Flow Lifecycle Manager

Autonomous agent for flow lifecycle operations: publish-and-test, batch operations, inventory reports.

Tools

This skill uses the FlowAgent MCP tools, referred to by bare name (clients surface them as mcp__flowagent__<tool> in Claude Code or flowagent-<tool> in Copilot CLI). If MCP tools aren't available, run /setup to wire the FlowAgent MCP server.

Capabilities

1. Publish-and-Test Cycle

  1. Call publish_flow to enable
  2. Call run_flow with wait: true and timeout: 30 to trigger and wait for completion
  3. Report: pass/fail, duration, action statuses

2. Batch Operations

For multiple flows (IDs from $ARGUMENTS or from list_flows):

  • Batch disable: Call disable_flow per flow
  • Batch delete: Call delete_flow per flow (confirm first)
  • Batch publish: Call publish_flow per flow Report per-item success/failure.

3. Inventory Report

  1. Call list_environments to get environments
  2. Call list_flows on each (or specified) environment
  3. Produce summary: flow counts by state, trigger types, recent modifications

4. Health Check

For each flow in an environment:

  1. Call get_run_history with top: 5
  2. Count Succeeded vs Failed runs
  3. Flag flows with >50% failure rate Report: flow name, success rate, last run status, last failure error.

5. Incident Response (runaway runs)

When a flow is misfiring with many queued runs:

  1. Call cancel_all_runs to bulk-cancel every Running/Waiting run (uses the Dataverse bulk action for solution & modern non-solution flows, per-run fallback otherwise). Pass turnOff: true to also disable the flow while the root cause is fixed.
  2. After fixing, resubmit_run the affected runs (note: only self-invoked runs are resubmittable per PA policy).

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most operations skills give in 469 tokens

Counted across 483 of the 484 authors here whose files we hold, read 2026-08-07

  • Collect monitoring data throughout the simulationin 14 of 483, across 6 files
  • Set the random seed for reproducibilityin 14 of 483, across 6 files
  • Validate simulations against analytical solutionsin 12 of 483, across 4 files
  • Clarify goals, constraints, and inputsin 11 of 483, across 2 files
  • Implement contract tests for integration pointsin 11 of 483, across 2 files
  • Implement strangler fig infrastructure with API gatewayin 11 of 483, across 2 files
  • Audit modernized components for security vulnerabilitiesin 11 of 483, across 2 files
  • Avoid Python blocking calls in processesin 10 of 483, across 3 files
  • Use resource context managers for automatic cleanupin 9 of 483, across 2 files
  • Maintain consistent time unitsin 9 of 483, across 2 files
  • Validate outcomes against success criteriain 8 of 483, across 1 file
  • Analyze the legacy codebase for technical debtin 8 of 483, across 1 file

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. 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.