feat: add FlowStudio monitoring + governance skills, update debug + build#1304
feat: add FlowStudio monitoring + governance skills, update debug + build#1304ninihen1 wants to merge 1 commit intogithub:stagedfrom
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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. |
| --- | ||
| 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. |
There was a problem hiding this comment.
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.
| ``` | ||
|
|
||
| > `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`. | ||
| > |
There was a problem hiding this comment.
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.
| 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. |
There was a problem hiding this comment.
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).
| the `power-automate-monitoring` skill. | |
| the `flowstudio-power-automate-monitoring` skill. |
| id = "Default-26e65220-....0f368466-b6b1-44ed-999c-94791124e402" | ||
| environmentName = "Default-26e65220-..." (everything before first ".") | ||
| flowName = "0f368466-b6b1-44ed-999c-94791124e402" (everything after first ".") |
There was a problem hiding this comment.
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.
| 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 ".") |
| --- | ||
| 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, |
There was a problem hiding this comment.
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.
|
|
||
| **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. |
There was a problem hiding this comment.
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.
| 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 |
There was a problem hiding this comment.
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.
| - `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 |
|
|
||
| **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. |
There was a problem hiding this comment.
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.
| 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 tool reference | ||
| - `power-automate-debug` — Debug failing flows after deployment |
There was a problem hiding this comment.
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.
| - `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 |
| - `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 |
There was a problem hiding this comment.
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.
| - `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 |
ninihen1
force-pushed
the
flowstudio-store-skills
branch
from
5f30eab to
d3900df
Compare
Updated: base changed to
|
🔍 Skill Validator Results6 resource(s) checked | ✅ All checks passed Full output |
…uild + mcp - **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** — purely live API tools (no store dependencies), mandatory action output inspection step, resubmit clarified as working for ALL trigger types. - **Updated flowstudio-power-automate-build** — Step 1 uses list_live_flows (not list_store_flows) for the duplicate check, resubmit-first testing. - **Updated flowstudio-power-automate-mcp** — store tool catalog, response shapes verified against real API calls, set_store_flow_state shape fix. - Plugin version bumped to 2.0.0, all 5 skills listed in plugin.json. - Generated docs regenerated via npm start. All response shapes verified against real FlowStudio MCP API calls. All 10 governance workflows validated with real tenant data. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
ninihen1
force-pushed
the
flowstudio-store-skills
branch
from
a6e9a76 to
41b39c4
Compare
|
Rebased onto latest Ran
The branch is ready for review. |
Summary
flowstudio-power-automate-monitoring— flow health, failure rates, maker inventory, Power Apps, environment/connection counts via FlowStudio MCP cached store toolsflowstudio-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 dashboardflowstudio-power-automate-debug— mandatory action output inspection step (error codes alone are insufficient), resubmit clarified as working for ALL trigger types (not just HTTP)flowstudio-power-automate-build— resubmit promoted as first testing option for any trigger typeflowstudio-power-automate-mcp— trigger_live_flow content-type behavior documented, branch URLs updated to mainValidation
Test plan
flowstudio-power-automate-*conventiontools/listoutput🤖 Generated with Claude Code