feat: add FlowStudio monitoring + governance skills, update debug + build by ninihen1 · Pull Request #1304 · github/awesome-copilot

ninihen1 · 2026-04-05T12:28:18Z

Summary

New skill: flowstudio-power-automate-monitoring — flow health, failure rates, maker inventory, Power Apps, environment/connection counts via FlowStudio MCP cached store tools
New skill: flowstudio-power-automate-governance — 10 CoE-aligned governance workflows: compliance review, orphan detection, archive scoring, connector audit, notification management, classification/tagging, maker offboarding, security review, environment governance, governance dashboard
Updated: flowstudio-power-automate-debug — mandatory action output inspection step (error codes alone are insufficient), resubmit clarified as working for ALL trigger types (not just HTTP)
Updated: flowstudio-power-automate-build — resubmit promoted as first testing option for any trigger type
Updated: flowstudio-power-automate-mcp — trigger_live_flow content-type behavior documented, branch URLs updated to main

Validation

All response shapes verified against real FlowStudio MCP API calls
All 10 governance workflows validated by agent simulation (10/10 PASS)
All 5 monitoring workflows validated end-to-end with real data (5/5 PASS)
Skills written for agent consumption — step lists, not code blocks

Test plan

Verify 5 skill SKILL.md files are well-formed (frontmatter, description, metadata)
Verify skill names follow flowstudio-power-automate-* convention
Verify no internal implementation details leaked (no Azure Function names, server URLs, table names)
Spot-check response shape examples against tools/list output

🤖 Generated with Claude Code

New skills: - flowstudio-power-automate-monitoring: flow health, failure rates, maker inventory, Power Apps, cached store tools - flowstudio-power-automate-governance: 10 CoE-aligned workflows — compliance review, orphan detection, archive scoring, connector audit, notification management, tagging, offboarding, security review, environment governance, dashboard Updated skills: - flowstudio-power-automate-debug: mandatory action output inspection (not just error codes), resubmit works for ALL trigger types - flowstudio-power-automate-build: resubmit promoted as first testing option, trigger_live_flow demoted to custom-payload only - flowstudio-power-automate-mcp: trigger_live_flow content-type note, branch URLs updated to main All response shapes verified against real API calls. All 10 governance workflows validated by agent simulation (10/10 PASS).

github-actions

⚠️ This PR targets main, but PRs should target staged.

The main branch is auto-published from staged and should not receive direct PRs.
Please close this PR and re-open it against the staged branch.

You can change the base branch using the Edit button at the top of this PR,
or run: gh pr edit 1304 --base staged

Copilot

Pull request overview

Adds two new FlowStudio Power Automate skills focused on tenant monitoring and governance, and updates existing FlowStudio Power Automate skills to emphasize action-output inspection during debugging and to promote resubmit_live_flow_run as the primary verification path across trigger types.

Changes:

Introduce new skills for monitoring (flowstudio-power-automate-monitoring) and governance (flowstudio-power-automate-governance) using FlowStudio MCP cached store tools.
Enhance debug guidance to require action inputs/outputs inspection (not just top-level error codes) and clarify resubmit behavior for all trigger types.
Update build guidance to promote resubmit-first testing and align HTTP schema fields (requestSchema, responseStatus, etc.).

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 11 comments.

Show a summary per file

File	Description
skills/flowstudio-power-automate-monitoring/SKILL.md	New monitoring skill documenting store tools, response shapes, and common health/inventory workflows.
skills/flowstudio-power-automate-governance/SKILL.md	New governance skill describing CoE-aligned workflows built around `update_store_flow` and cached reads.
skills/flowstudio-power-automate-mcp/SKILL.md	Expands MCP skill description and adds external debugging example links + metadata.
skills/flowstudio-power-automate-debug/SKILL.md	Adds mandatory “inspect action outputs” step and clarifies resubmit applicability across triggers; updates cross-references.
skills/flowstudio-power-automate-build/SKILL.md	Promotes resubmit-first testing, clarifies HTTP custom payload usage, and updates cross-references.

Copilot · 2026-04-05T12:33:20Z

skills/flowstudio-power-automate-monitoring/SKILL.md

+---
+name: flowstudio-power-automate-monitoring
+description: >-
+  Monitor Power Automate flow health, track failure rates, and inventory tenant
+  assets using the FlowStudio MCP cached store. The live API only returns
+  top-level run status. Store tools surface aggregated stats, per-run failure
+  details with remediation hints, maker activity, and Power Apps inventory —
+  all from a fast cache with no rate-limit pressure on the PA API.


This new skill folder doesn’t appear to be added to the skills index in docs/README.skills.md (the index currently lists flowstudio-power-automate-build/debug/mcp but not monitoring). Please add an entry so the skill is discoverable via the repo docs.

Copilot · 2026-04-05T12:33:20Z

skills/flowstudio-power-automate-monitoring/SKILL.md

+```
+
+> `id` format: `envId.flowId`. Split on first `.` to get the flow UUID.
+>
+> `triggerUrl` and `tags` are optional. Some entries are sparse (just `id` +
+> `monitor`) — skip entries without `displayName`.
+>


The id format guidance says envId.flowId split on the first . (which is important), but the example id shown doesn’t clearly include a . (it’s obscured by ....). Consider using an explicit placeholder like Default-<envGuid>.<flowGuid> so readers don’t mistakenly split on - or assume no delimiter.

Copilot · 2026-04-05T12:33:21Z

skills/flowstudio-power-automate-governance/SKILL.md

+This skill uses `update_store_flow` to write governance metadata and the
+monitoring tools (`list_store_flows`, `get_store_flow`, `list_store_makers`,
+etc.) to read tenant state. For monitoring and health-check workflows, see
+the `power-automate-monitoring` skill.


This skill references power-automate-monitoring / power-automate-* as related skills, but the actual skill names in this repo are flowstudio-power-automate-*. Please update these references so agents can load the correct skills (e.g., flowstudio-power-automate-monitoring).

Suggested change

the `power-automate-monitoring` skill.

the `flowstudio-power-automate-monitoring` skill.

Copilot · 2026-04-05T12:33:21Z

skills/flowstudio-power-automate-governance/SKILL.md

+id = "Default-26e65220-....0f368466-b6b1-44ed-999c-94791124e402"
+environmentName = "Default-26e65220-..."   (everything before first ".")
+flowName = "0f368466-b6b1-44ed-999c-94791124e402"  (everything after first ".")


The Flow ID extraction example explains splitting envId.flowId on the first ., but the sample id string shown doesn’t visibly include a . (it’s masked by ....). Please change the example to an unambiguous placeholder (e.g., Default-<envGuid>.<flowGuid>) so the parsing instruction is clear.

Suggested change

id = "Default-26e65220-....0f368466-b6b1-44ed-999c-94791124e402"

environmentName = "Default-26e65220-..." (everything before first ".")

flowName = "0f368466-b6b1-44ed-999c-94791124e402" (everything after first ".")

id = "Default-<envGuid>.<flowGuid>"

environmentName = "Default-<envGuid>" (everything before first ".")

flowName = "<flowGuid>" (everything after first ".")

Copilot · 2026-04-05T12:33:21Z

skills/flowstudio-power-automate-governance/SKILL.md

+---
+name: flowstudio-power-automate-governance
+description: >-
+  Govern Power Automate flows and Power Apps at scale using the FlowStudio MCP
+  cached store. Classify flows by business impact, detect orphaned resources,
+  audit connector usage, enforce compliance standards, manage notification rules,
+  and compute governance scores — all without Dataverse or the CoE Starter Kit.
+  Load this skill when asked to: tag or classify flows, set business impact,


This new skill folder doesn’t appear to be added to the skills index in docs/README.skills.md (which currently lists the other FlowStudio Power Automate skills). Please add an entry so the governance skill is discoverable via the repo docs.

Copilot · 2026-04-05T12:33:22Z

skills/flowstudio-power-automate-debug/SKILL.md

+
 **Prerequisite**: A FlowStudio MCP server must be reachable with a valid JWT.
-See the `flowstudio-power-automate-mcp` skill for connection setup.  
+See the `power-automate-mcp` skill for connection setup.  


The skill name referenced in the prerequisite (power-automate-mcp) doesn’t exist in this repo; the actual skill is flowstudio-power-automate-mcp. Please update the reference so readers can find the correct connection setup instructions.

Suggested change

See the `power-automate-mcp` skill for connection setup.

See the `flowstudio-power-automate-mcp` skill for connection setup.

Copilot · 2026-04-05T12:33:22Z

skills/flowstudio-power-automate-debug/SKILL.md

+- `power-automate-mcp` — Core connection setup and operation reference
+- `power-automate-build` — Build and deploy new flows


The Related Skills section refers to power-automate-mcp / power-automate-build, but the skill files in this repo are named flowstudio-power-automate-*. Please update these names to avoid broken cross-skill references.

Suggested change

- `power-automate-mcp` — Core connection setup and operation reference

- `power-automate-build` — Build and deploy new flows

- `flowstudio-power-automate-mcp` — Core connection setup and operation reference

- `flowstudio-power-automate-build` — Build and deploy new flows

Copilot · 2026-04-05T12:33:22Z

skills/flowstudio-power-automate-build/SKILL.md


 **Prerequisite**: A FlowStudio MCP server must be reachable with a valid JWT.
-See the `flowstudio-power-automate-mcp` skill for connection setup.  
+See the `power-automate-mcp` skill for connection setup.  


The prerequisite section references power-automate-mcp, but the actual skill in this repo is flowstudio-power-automate-mcp. Please correct the name so readers can locate the connection setup documentation.

Suggested change

See the `power-automate-mcp` skill for connection setup.

See the `flowstudio-power-automate-mcp` skill for connection setup.

Copilot · 2026-04-05T12:33:22Z

skills/flowstudio-power-automate-build/SKILL.md

+- `power-automate-mcp` — Core connection setup and tool reference
+- `power-automate-debug` — Debug failing flows after deployment


The Related Skills section refers to power-automate-mcp / power-automate-debug, but the skill files in this repo are flowstudio-power-automate-*. Please update these names to avoid broken cross-skill references.

Suggested change

- `power-automate-mcp` — Core connection setup and tool reference

- `power-automate-debug` — Debug failing flows after deployment

- `flowstudio-power-automate-mcp` — Core connection setup and tool reference

- `flowstudio-power-automate-debug` — Debug failing flows after deployment

Copilot · 2026-04-05T12:33:23Z

skills/flowstudio-power-automate-governance/SKILL.md

+- `power-automate-monitoring` — Health checks, failure rates, inventory (read-only)
+- `power-automate-mcp` — Core connection setup, live tool reference
+- `power-automate-debug` — Deep diagnosis with action-level inputs/outputs
+- `power-automate-build` — Build and deploy flow definitions


The Related Skills section lists power-automate-* skill names, but this repo’s FlowStudio skills are named flowstudio-power-automate-* (including the monitoring skill introduced in this PR). Please update these names so the cross-references resolve correctly.

Suggested change

- `power-automate-monitoring` — Health checks, failure rates, inventory (read-only)

- `power-automate-mcp` — Core connection setup, live tool reference

- `power-automate-debug` — Deep diagnosis with action-level inputs/outputs

- `power-automate-build` — Build and deploy flow definitions

- `flowstudio-power-automate-monitoring` — Health checks, failure rates, inventory (read-only)

- `flowstudio-power-automate-mcp` — Core connection setup, live tool reference

- `flowstudio-power-automate-debug` — Deep diagnosis with action-level inputs/outputs

- `flowstudio-power-automate-build` — Build and deploy flow definitions

- All SKILL.md cross-references: power-automate-* → flowstudio-power-automate-* - Plugin README: rewritten with problem statement, 5-skill table, getting started - plugin.json: added monitoring + governance, v2.0.0 - Governance: clearer ID format placeholder - action-types.md: cross-reference fixed Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

The plugin.json referenced these paths but the folders were missing. Also synced cross-reference fixes to the plugin copies of mcp/debug/build. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

- Fixed skills paths in plugin.json to end with "/" (validation requirement) - Ran npm run build — updated docs/README.skills.md, docs/README.plugins.md, and .github/plugin/marketplace.json with new skills Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Governance: cache-only write docs, skip Deleted flows, two tag systems, DataverseSystemUser note, connector audit scoping, security review rewrite, environment governance sparse entry handling. Monitoring: critical flow designation, tag system clarification. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Top-level source skills were stale — plugin copies had all the fixes (store tool removal from debug, list_live_flows in build, governance and monitoring updates) but the source skills were not updated. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

ninihen1 · 2026-04-05T23:22:04Z

Updated: base changed to `staged`, all review comments addressed

Rebased PR target from main to staged per contributing guidelines.

All 11 Copilot review comments from the initial submission have been addressed in subsequent commits:

Cross-references fixed — all 8 skill name references now use the flowstudio-power-automate-* prefix (was power-automate-*)
Skills index updated — both flowstudio-power-automate-monitoring and flowstudio-power-automate-governance are in docs/README.skills.md
ID format clarified — examples use explicit Default-<envGuid>.<flowGuid> placeholders showing the . delimiter
Tier split enforced — debug and build skills now use only live API tools; store tools are confined to monitoring and governance skills
Top-level source skills synced — both skills/ and plugins/.../skills/ copies are identical

Ready for re-review.

github-actions bot and others added 2 commits April 1, 2026 23:04

chore: publish from staged

0c3c5bb

Copilot AI review requested due to automatic review settings April 5, 2026 12:28

ninihen1 requested a review from aaronpowell as a code owner April 5, 2026 12:28

github-actions bot requested changes Apr 5, 2026

View reviewed changes

Copilot started reviewing on behalf of ninihen1 April 5, 2026 12:29 View session

Copilot AI reviewed Apr 5, 2026

View reviewed changes

ninihen1 force-pushed the flowstudio-store-skills branch from 5f30eab to d3900df Compare April 5, 2026 12:39

ninihen1 and others added 11 commits April 5, 2026 23:05

fix: add monitoring + governance skills to plugin skills folder

7a83e38

The plugin.json referenced these paths but the folders were missing. Also synced cross-reference fixes to the plugin copies of mcp/debug/build. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

fix: monitoring SKILL.md — clearer ID format placeholder per review

d29a680

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

fix: sync ID format placeholders and cross-references across all copies

8d6b4eb

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

fix: replace all envId placeholders with <environmentId> for clarity

6fc9d95

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

fix: build skill Step 1 uses list_live_flows instead of list_store_flows

93a1ab1

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

fix: debug skill store tools marked optional, build cross-ref prefix

5e4e2c7

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

fix: remove store tool references from debug skill entirely

3479f68

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

ninihen1 changed the base branch from main to staged April 5, 2026 23:19

ninihen1 requested a review from dvelton as a code owner April 5, 2026 23:19

	the `power-automate-monitoring` skill.
	the `flowstudio-power-automate-monitoring` skill.

	See the `power-automate-mcp` skill for connection setup.
	See the `flowstudio-power-automate-mcp` skill for connection setup.

		- `power-automate-mcp` — Core connection setup and operation reference
		- `power-automate-build` — Build and deploy new flows

		- `power-automate-mcp` — Core connection setup and tool reference
		- `power-automate-debug` — Debug failing flows after deployment

Conversation

ninihen1 commented Apr 5, 2026

Summary

Validation

Test plan

Uh oh!

github-actions bot left a comment

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI Apr 5, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 5, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 5, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 5, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 5, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 5, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 5, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 5, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 5, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 5, 2026

Choose a reason for hiding this comment

Uh oh!

ninihen1 commented Apr 5, 2026

Updated: base changed to staged, all review comments addressed

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Updated: base changed to `staged`, all review comments addressed