Update FlowStudio Power Automate skills for Button, PowerApps, and Skills triggers

[ninihen1]

What changed

FlowStudio MCP server 1.2.42 changed trigger_live_flow: Button, PowerApps, and Skills triggers now receive the body you pass (previously only HTTP request triggers did). Four files in the three live skills catch up:

• flowstudio-power-automate-debug/SKILL.md — resubmit-vs-trigger table and the custom-payload section cover Button and PowerApps; documents the new warning for missing required inputs, runName, and the browser-extension limitation.
• flowstudio-power-automate-build/SKILL.md and references/trigger-types.md — drop the "build an HTTP twin" workaround for Button/Skills flows; pass inputs in body instead.
• flowstudio-power-automate-mcp/references/tool-reference.md — full trigger_live_flow entry: new response keys (triggerKind, invocation, runName, warning), routing, corrected content-type note.

Frontmatter unchanged, so README output is unaffected. Verified live against the production server (1.2.43) on Button, PowerAppV2, and Skills flows.

[github-actions]

🔒 PR Risk Scan Results

Scanned 4 changed file(s).

Severity	Count
🔴 High	0
🟠 Medium	0
ℹ️ Info	0

✅ No matching risk patterns were detected in changed files.

This is an automated soft-gate report. Findings indicate review targets and do not block merge by themselves.

[github-actions]

🔍 Vally Lint Results

⛔ Findings need attention

Scope	Checked
Skills	3
Agents	0
Total	3

Severity	Count
❌ Errors	1
⚠️ Warnings	0
ℹ️ Advisories	0

Summary

Level	Finding
❌	flowstudio-power-automate-build (1/2 checks passed, 1 failed)

Full linter output

### Linting skills/flowstudio-power-automate-build
❌ flowstudio-power-automate-build (1/2 checks passed, 1 failed)
    ✗ [spec-compliance] 1 of 1 skill(s) have spec violations.
        ✗ spec-compliance: Spec checks failed.
            ✗ File length (506 lines) exceeds limit (500).
    ✓ [valid-refs] All file references across 1 skill(s) are valid.
        ✓ valid-refs: All file references resolve to existing files within the skill directory.

1 skill(s) linted, 1 failed

### Linting skills/flowstudio-power-automate-debug
✅ flowstudio-power-automate-debug (2/2 checks passed)
    ✓ [spec-compliance] All 1 skill(s) are spec-compliant.
        ✓ spec-compliance: All spec checks passed.
    ✓ [valid-refs] All file references across 1 skill(s) are valid.
        ✓ valid-refs: All file references resolve to existing files within the skill directory.

1 skill(s) linted, 1 passed

### Linting skills/flowstudio-power-automate-mcp
✅ flowstudio-power-automate-mcp (2/2 checks passed)
    ✓ [spec-compliance] All 1 skill(s) are spec-compliant.
        ✓ spec-compliance: All spec checks passed.
    ✓ [valid-refs] All file references across 1 skill(s) are valid.
        ✓ valid-refs: All file references resolve to existing files within the skill directory.

1 skill(s) linted, 1 passed

Note: Vally lint returned a non-zero exit code. Please review the findings above before merge.

[Copilot]

Pull request overview

Updates FlowStudio Power Automate skills for expanded trigger_live_flow support.

Changes:

• Documents connector-runtime invocation and response fields.
• Replaces temporary HTTP workarounds with direct payload triggering.
• Adds required-input warnings and browser-key limitations.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 3 comments.

File	Description
skills/flowstudio-power-automate-mcp/references/tool-reference.md	Updates tool behavior and responses.
skills/flowstudio-power-automate-debug/SKILL.md	Expands custom-payload debugging guidance.
skills/flowstudio-power-automate-build/SKILL.md	Updates flow testing guidance.
skills/flowstudio-power-automate-build/references/trigger-types.md	Documents direct Skills-trigger testing.

Suppressed comments (6)

skills/flowstudio-power-automate-mcp/references/tool-reference.md:453

• The supported-trigger list and routing explanation omit Skills triggers, despite this PR documenting that they are invokable with body through the same connector runtime. This can cause callers to treat a supported Skills flow as an unsupported “other” trigger.

> **Works for `Request` triggers: HTTP request, Button, and PowerApps.** Returns an
> error for Recurrence and connector triggers:
> `"only HTTP Request triggers can be invoked via this tool"`.

skills/flowstudio-power-automate-mcp/references/tool-reference.md:471

• Skills triggers are documented above as using the connector runtime too, so the browser-extension restriction also applies to them. Naming only Button and PowerApps incorrectly implies that a Skills payload can be delivered with this key type.

> Browser-extension keys cannot reach the connector runtime, so Button and
> PowerApps triggers run only with an empty body over that key type. The error
> lists the alternatives (resubmit a past run, default the inputs inside the flow
> with `coalesce()`, or use a standard key).

skills/flowstudio-power-automate-mcp/references/tool-reference.md:600

• This behavioral summary omits Skills triggers and then classifies unlisted kinds as unsupported, contradicting the new Skills-trigger guidance in this PR.

- **Works for HTTP, Button, and PowerApps triggers.** Returns error for Recurrence,
  connector, and other trigger types.
- Pass trigger inputs as `body`. A `warning` in the result means a required input
  was missing and the run started with it null.

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

• Skills is also a supported Request trigger kind (kind: "Skills" in trigger-types.md), so this exclusivity statement is inaccurate.

> Works for `Request` triggers only: HTTP request, Button, and PowerApps.
> Scheduled and connector triggers cannot be run this way.

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

• Because Skills triggers use connector-runtime invocation too, they also return runName and share the browser-extension-key limitation. Omitting Skills makes these operational instructions incorrect for one of the trigger kinds this PR adds.

> `runName` is only returned for Button and PowerApps runs. For HTTP triggers
> find the run with `get_live_flow_runs`.
>
> Over a browser-extension key, Button and PowerApps triggers run only with an
> empty body. The tool says so and lists the ways round it: resubmit a past run,

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

• PowerApps triggers have the same missing-required-input behavior documented by this PR, so limiting this gotcha to Button/Skills leaves one supported trigger kind uncovered.

| Button/Skills trigger used for MCP testing | Runs even when a required input is missing (null) | Pass inputs in `trigger_live_flow` `body`; on `warning`, cancel and retry with the full body |

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.