feat: align FlowStudio Power Automate skills with MCP server v1.1.6#1564
Merged
aaronpowell merged 1 commit intogithub:stagedfrom Apr 30, 2026
Merged
Conversation
Foundation skill (flowstudio-power-automate-mcp) rewritten to use the server's new tool_search and list_skills meta-tools (v1.1.5+) for discovery instead of cataloging every tool by hand. Cut from 519 to 295 lines. New "Which Skill to Use When" intent-keyed decision tree points at the four specialized skills. Build/debug/governance/monitoring updated for use-case framing. Tools that genuinely cross tiers (e.g. debug skill borrowing get_store_flow_summary) are correct when the workflow needs them — the split between skills is by use-case intent, not by tool partition. Build skill: new Step 3a Resolving Dynamic Connector Values covers get_live_dynamic_options outer-parameter auto-bridge (v1.1.6+) and the AadGraph user-picker fallback via shared_office365users.SearchUserV2 (replaces broken builtInOperation:AadGraph.GetUsers). Debug skill: Outlook user-picker failure note pointing at the fallback. Monitoring skill description disambiguates from the server's monitor-flow tool bundle (runtime control of a single flow) — this skill is tenant-wide health analytics over the cached store. All 5 skills validate via npm run skill:validate; line endings LF only; codespell clean; auto-regenerated docs/README.skills.md included.
Contributor
🔍 Skill Validator Results
Summary
Full validator output```text Found 5 skill(s) [flowstudio-power-automate-build] 📊 flowstudio-power-automate-build: 5,040 BPE tokens [chars/4: 5,168] (comprehensive ✗), 46 sections, 17 code blocks [flowstudio-power-automate-build] ⚠ Skill is 5,040 BPE tokens (chars/4 estimate: 5,168) — "comprehensive" skills hurt performance by 2.9pp on average. Consider splitting into 2–3 focused skills. [flowstudio-power-automate-build] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [flowstudio-power-automate-debug] 📊 flowstudio-power-automate-debug: 4,320 BPE tokens [chars/4: 4,264] (standard ~), 65 sections, 15 code blocks [flowstudio-power-automate-debug] ⚠ Skill is 4,320 BPE tokens (chars/4 estimate: 4,264) — approaching "comprehensive" range where gains diminish. [flowstudio-power-automate-governance] 📊 flowstudio-power-automate-governance: 5,414 BPE tokens [chars/4: 5,786] (comprehensive ✗), 17 sections, 11 code blocks [flowstudio-power-automate-governance] ⚠ Skill is 5,414 BPE tokens (chars/4 estimate: 5,786) — "comprehensive" skills hurt performance by 2.9pp on average. Consider splitting into 2–3 focused skills. [flowstudio-power-automate-mcp] 📊 flowstudio-power-automate-mcp: 3,243 BPE tokens [chars/4: 3,176] (standard ~), 19 sections, 9 code blocks [flowstudio-power-automate-mcp] ⚠ Skill is 3,243 BPE tokens (chars/4 estimate: 3,176) — approaching "comprehensive" range where gains diminish. [flowstudio-power-automate-monitoring] 📊 flowstudio-power-automate-monitoring: 3,809 BPE tokens [chars/4: 3,609] (standard ~), 25 sections, 14 code blocks [flowstudio-power-automate-monitoring] ⚠ Skill is 3,809 BPE tokens (chars/4 estimate: 3,609) — approaching "comprehensive" range where gains diminish. ✅ All checks passed (5 skill(s)) ``` |
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the FlowStudio Power Automate skill documentation set to match FlowStudio MCP server v1.1.6, shifting tool discovery guidance to the new list_skills / tool_search meta-tools and updating workflow guidance for Pro+ Store-tier capabilities.
Changes:
- Reworked the foundation skill to focus on intent-based skill selection, meta-tool discovery (
list_skills/tool_search), and oversized-response handling. - Added/updated guidance across build/debug/monitoring/governance skills for v1.1.6 behavior (dynamic options “auto-bridge”,
describe_live_connectorfallback patterns, Pro+ access notes). - Updated plugin/docs descriptions to reflect the new foundation-skill positioning and discovery approach.
Reviewed changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated 14 comments.
Show a summary per file
| File | Description |
|---|---|
| skills/flowstudio-power-automate-monitoring/SKILL.md | Updates monitoring positioning, Pro+ gating guidance, and shifts discovery to tool_search. |
| skills/flowstudio-power-automate-mcp/SKILL.md | Major rewrite into a foundation/plumbing skill with meta-tool discovery and oversized-response handling guidance. |
| skills/flowstudio-power-automate-governance/SKILL.md | Reframes governance intent vs monitoring, adds Pro+ gating + meta-tool discovery guidance. |
| skills/flowstudio-power-automate-debug/SKILL.md | Adds Outlook dynamic-options failure guidance and updates cross-skill references. |
| skills/flowstudio-power-automate-build/SKILL.md | Adds “Step 3a” dynamic-options guidance including v1.1.6 auto-bridge + fallback. |
| plugins/flowstudio-power-automate/README.md | Updates skill descriptions/formatting to match the new foundation-skill focus. |
| docs/README.skills.md | Updates the skills index descriptions for the FlowStudio Power Automate skill set. |
Comment on lines
+48
to
+52
| | Make or change a flow (build new, modify existing, fix a bug, deploy) | **`power-automate-build`** | | ||
| | Diagnose why a flow failed (root cause analysis on a failing run) | **`power-automate-debug`** | | ||
| | See tenant-wide flow health, failure rates, asset inventory | **`power-automate-monitoring`** *(Pro+)* | | ||
| | Tag, audit, classify, score, or offboard flows | **`power-automate-governance`** *(Pro+)* | | ||
| | Just connect, set up auth, write the helper, parse responses | this skill (foundation) | |
|
|
||
| **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. |
| > ``` | ||
|
|
||
| See the `flowstudio-power-automate-mcp` skill's **connection-references.md** reference | ||
| See the `power-automate-mcp` skill's **connection-references.md** reference |
Comment on lines
+531
to
+532
| - `power-automate-mcp` — Foundation skill: connection setup, MCP helper, tool discovery | ||
| - `power-automate-debug` — Debug failing flows after deployment |
|
|
||
| **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. |
Comment on lines
+514
to
+517
| - `power-automate-monitoring` — Health checks, failure rates, inventory (read-only) | ||
| - `power-automate-mcp` — Foundation skill: connection setup, MCP helper, tool discovery | ||
| - `power-automate-debug` — Deep diagnosis with action-level inputs/outputs | ||
| - `power-automate-build` — Build and deploy flow definitions |
| > 2. Tell the user this feature requires a Pro+ subscription | ||
| > 3. Link them to https://mcp.flowstudio.app/pricing | ||
| > 4. If their question can be answered with live tools (e.g. "list flows in | ||
| > one environment"), offer to use the `power-automate-mcp` skill instead |
Comment on lines
+411
to
414
| - `power-automate-mcp` — Foundation skill: connection setup, MCP helper, tool discovery | ||
| - `power-automate-debug` — Deep diagnosis with action-level inputs/outputs (live API) | ||
| - `power-automate-build` — Build and deploy flow definitions | ||
| - `power-automate-governance` — Governance metadata, tagging, notification rules, CoE patterns |
Comment on lines
+156
to
+157
| | [flowstudio-power-automate-mcp](../skills/flowstudio-power-automate-mcp/SKILL.md)<br />`gh skills install github/awesome-copilot flowstudio-power-automate-mcp` | Foundation skill for Power Automate via FlowStudio MCP — auth setup, the reusable MCP helper (Python + Node.js), tool discovery via `list_skills` / `tool_search`, and oversized-response handling. Load this skill first when connecting an agent to Power Automate. For specialized workflows, load `power-automate-build`, `power-automate-debug`, `power-automate-monitoring` (Pro+), or `power-automate-governance` (Pro+) — each contains the workflow narrative, this skill provides the plumbing they all rely on. Requires a FlowStudio MCP subscription or compatible server — see https://mcp.flowstudio.app | `references/MCP-BOOTSTRAP.md`<br />`references/action-types.md`<br />`references/connection-references.md`<br />`references/tool-reference.md` | | ||
| | [flowstudio-power-automate-monitoring](../skills/flowstudio-power-automate-monitoring/SKILL.md)<br />`gh skills install github/awesome-copilot flowstudio-power-automate-monitoring` | **Pro+ subscription required.** Tenant-wide Power Automate flow health monitoring, failure rate analytics, and asset inventory using the FlowStudio MCP cached store. Load this skill ONLY for tenant-wide aggregated views — not for listing flows in a single environment or debugging a specific run (use power-automate-mcp or power-automate-debug for those). Not the same as the server's `monitor-flow` tool bundle (`tool_search query: "skill:monitor-flow"`) — that bundle is for runtime control of a single flow (start/stop/trigger/ cancel/resubmit); this skill is for tenant-wide health analytics over the cached store. Load when asked to: monitor tenant health, get aggregated failure rates over a time window, review tenant-wide error trends, find inactive makers across the tenant, inventory all Power Apps in the tenant, compute governance scores, generate a compliance report, or run a tenant-wide health overview. Requires a FlowStudio for Teams or MCP Pro+ subscription — see https://mcp.flowstudio.app | None | |
| 1. Install the plugin | ||
| 2. Get your API key at [mcp.flowstudio.app](https://mcp.flowstudio.app) | ||
| 3. Configure the MCP connection in VS Code (`.vscode/mcp.json`): | ||
|
|
aaronpowell
approved these changes
Apr 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Aligns the five
flowstudio-power-automate-*skills with the FlowStudio MCP server v1.1.6 release (addedtool_search/list_skillsmeta-tools, hidget_live_connectorbehinddescribe_live_connector).What changed
Foundation skill (
flowstudio-power-automate-mcp) rewritten — 519 → 295 lines (-43%):tool_searchandlist_skillsmeta-tools (v1.1.5+) own this now, so re-listing every tool inline only goes stale.tool_searchquery forms.Build skill — new Step 3a Resolving Dynamic Connector Values:
get_live_dynamic_optionsouter-parameter auto-bridge (v1.1.6) — agents can passparameters: {searchTerm: "joh", top: 10}directly without manually declaringparameterReferencemappings.builtInOperation:AadGraph.GetUsers(used by OutlookGetEmailsV3) is broken at the listEnum layer;describe_live_connector(v1.1.6) returns a structuredfallbackfield pointing agents atshared_office365users.SearchUserV2instead.Debug skill — new "Outlook user-picker failures (
DynamicListValuesUndefinedOrInvalid)" subsection in Step 7, pointing at the build skill's Step 3a for the working pattern.Governance skill — reframed intro: the skill shares the same Store-tier tool family with
flowstudio-power-automate-monitoringbut with a different intent (audit/classification vs operational health). Replacedtools/listreference withtool_search query: "skill:governance".Monitoring skill — description disambiguates from the server's
monitor-flowtool bundle (the bundle is runtime control of a single flow; this skill is tenant-wide health analytics over the cached store). Body intro replacedtools/listwithtool_searchguidance.Plugin README — updated foundation skill description.
Pre-flight (all green)
npm run skill:validate— All 273 skills validnpm run plugin:validate— All 64 plugins validnpm run build—marketplace.jsonregenerated cleanly.mdfilesWhy this matters
Every skill catalog table eventually drifts from the server. Letting agents pull schemas via
tool_searchkeeps the SKILL.md small, relevant, and focused on workflow narrative — the part the server can't tell them.