manage-flows

manage-flows is a skill for Claude Code from microsoft/power-platform-skills. It costs 38 tokens per session (1,102 once invoked), scanned A, original, MIT.

A manager for the lifecycle of Power Automate flows, from publishing and testing to batch changes and inventory reports.

In plain words
What is it for?
Use it to publish and test flows, perform batch operations, report flow counts and states, and review trigger types and recent changes.
Why use it?
It reduces repetitive work when enabling, testing, disabling, deleting, or reviewing many flows across environments.

Skill for Claude Code ✓ vendor

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter; mentions Claude Code.

Part of the power-automate plugin — 9 skills shipped together

Good fit Use it to publish and test flows, perform batch operations, report flow counts and states, and review trigger types and recent changes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/microsoft/power-platform-skills/manage-flows
About the project

microsoft/power-platform-skills is a plugin marketplace containing reusable skills, agents, and commands for developing with Microsoft Power Platform. Developers use it to build and deploy Power Pages sites, model-driven Power Apps, and related solutions through Claude Code or GitHub Copilot. The catalogue entries are the marketplace's included skills, agents, plugins, and other agent components.

microsoft/power-platform-skills · 836 stars · on GitHub · aka.ms

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add microsoft/power-platform-skills --skill manage-flows
Clone the repo
git clone --depth 1 https://github.com/microsoft/power-platform-skills

Made for: Claude Code.

Or install power-automate, the plugin that ships this one along with the rest of its 9 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for manage-flows

README.md
[![agentmods](https://agentmods.dev/badge/skills/microsoft/power-platform-skills/manage-flows.svg)](https://agentmods.dev/skills/microsoft/power-platform-skills/manage-flows)
Your own site
<a href="https://agentmods.dev/skills/microsoft/power-platform-skills/manage-flows"><img src="https://agentmods.dev/badge/skills/microsoft/power-platform-skills/manage-flows.svg" alt="Measured on agentmods" height="20"></a>
Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,102 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Excessive Agency · line 8
    Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.
    Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00038 $0.01102
Opus 5 $0.00019 $0.00551
Sonnet 5 $0.00008 $0.00220
Haiku 4.5 $0.00004 $0.00110

Measured 4d ago against content hash 05fd555e07c3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

manage-flows scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/power-automate/skills/manage-flows/SKILL.md · 57 lines

What it actually says

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). Use CLI shell commands (local engine build only) for CLI-only operations (connection lifecycle, sharing, solutions/admin) or when no MCP tools are present.

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).
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 4d ago First seen · 57 lines · 38 tokens per session scan A 05fd555e07c3

Subscribe to this mod's changes

manage-flows is a skill published in the GitHub repository microsoft/power-platform-skills (836 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 1,102 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

canvas-apps-ui-gen

Generates paste-ready Power Apps Canvas App YAML. Invoke when the user wants to replicate a UI mockup, improve an existing Canvas app screen, or build a new screen from a text description. Also invoke when the user asks to "improve", "redesign", or "generate YAML" for a Canvas app screen.

ToluVictor/canvas-apps-tools · 71 tokens

catchup

Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.

oliver-kriska/claude-elixir-phoenix · 48 tokens

plan

Plan features spanning multiple domains: billing (Stripe), auth (RBAC), real-time (Presence), webhooks, jobs (Oban). Use when designing interconnected systems or converting review findings into tasks.

oliver-kriska/claude-elixir-phoenix · 42 tokens

work

Execute Elixir/Phoenix plan tasks with progress tracking. Use after /phx:plan to implement features with mix compile and mix test verification after each step, or --continue to resume interrupted work.

oliver-kriska/claude-elixir-phoenix · 43 tokens

phx-deps-update

Bump outdated Hex deps — inventory, snapshot changelogs, update, fix breaks, split reviewable PRs (patches bundled, majors solo). Use to upgrade/bump Elixir dependencies or when versions fall behind. NOT for deps.get failures (phx-investigate).

oliver-kriska/claude-elixir-phoenix · 62 tokens

link-ticket-to-session

Link the current Claude Code session to a ticket (Linear, Jira, GitHub Issues, or GitHub Pull Requests) and cache its title/status in karma. Use when the user explicitly asks to link, attach, associate, or connect this session to a ticket, issue, or PR — e.g. "/link-ticket-to-session ABC-123", "link this session to…

JayantDevkar/claude-code-karma · 91 tokens