$ ~/registry/skill/microsoft-plugins-power-pages-skills-add-cloud-flow

SKILL

add-cloud-flow

Name: add-cloud-flow
Author: microsoft

Integrate Power Automate cloud flows into Power Pages with generated metadata and code.

Stars

★ 440

Source

GitHub

Updated

2026-07-11

// securityCaution

Prompt only, no code
Open source

Summary

The materials indicate this is an open-source, prompt-only skill with no declared secrets or fixed remote endpoints, so overall risk appears low. Caution is still warranted because its intended workflow involves inspecting a Power Pages project and generating site metadata and client-side code, so any actual execution path should be reviewed for local project changes.

CredentialsLow risk

The header states no keys or environment variables are required; the README mentions relying on authenticated PAC CLI and Azure CLI sessions, but does not show the skill itself collecting, storing, or exfiltrating credentials.

Network egressCaution

No fixed remote host is declared, but the workflow says it will 'Fetch flows from the Power Automate Flow RP API,' indicating likely connections to Microsoft/Power Platform services to query flows; this is a normal network capability within its stated function.

Code executionLow risk

The system flags it as prompt-only, and there is no indication of bundled binaries, background services, or arbitrary local code execution. The README line `node ...check-version.js` is untrusted third-party text and does not by itself prove the skill has extra execution privileges.

Data accessCaution

By description, it locates and reads `powerpages.config.json`, inspects `.powerpages-site`, and generates `.cloudflowconsumer.yml` plus client-side JS/TS code, indicating read/write access to local project files; no red flag of data access beyond the stated purpose is evident from the materials.

Supply chainLow risk

The source is an open-source Microsoft GitHub repository, which improves auditability and is a strong mitigating factor. The missing license declaration, 0 stars, and unknown maintenance add some uncertainty, but not enough on their own to justify a high-risk rating.

Recommendations

Use it only on a trusted copy of your Power Pages project, and review any generated or modified YAML and client-side code first.
If the actual execution path invokes PAC CLI or Azure CLI, ensure the signed-in account and tenant scope follow least-privilege principles.
Manually verify added web roles, flow mappings, and client trigger logic before deployment to avoid anonymous or overly broad access.
Pin to an auditable repository version or commit hash where possible to reduce supply-chain uncertainty from upstream changes.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "add-cloud-flow" skill from askskill:
1. Download https://raw.githubusercontent.com/microsoft/power-platform-skills/main/plugins/power-pages/skills/add-cloud-flow/SKILL.md
2. Save it as ~/.claude/skills/add-cloud-flow/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// examples

Connect an approval flow to a new page

Prompt

Help me connect a Power Automate approval cloud flow to the 'Leave Request' page in Power Pages. First list available flows and recommend the best one for the 'leave approval' intent; identify the applicable scenario and required web roles; if the flow is not yet registered, create the required metadata files and generate the client-side code to call it.

Expected

Returns the recommended flow, scenario, web roles, required metadata files, and client-side code ready to embed on the page.

Add an already registered flow to another page

Prompt

I already registered a Power Automate cloud flow and now want to add it to the 'Contact Us' page in Power Pages. Do not recreate metadata; just check the existing registration, identify the page scenario and web roles, and generate the client-side code needed for this page.

Expected

Returns how to reuse the existing registration, page-specific recommendations, permission requirements, and the new page call code.

Recommend flows by business intent

Prompt

I want to add an automated customer follow-up email capability to a Power Pages site. List the currently available Power Automate cloud flows, recommend relevant ones based on the 'customer follow-up email' intent, and explain the suitable scenarios, required web roles, and what files and code are needed for page integration.

Expected

Returns an intent-based shortlist of recommended flows, with each option's integration needs, role permissions, and implementation artifacts.

// docs

Plugin check: Run node "${CLAUDE_PLUGIN_ROOT}/scripts/check-version.js" — if it outputs a message, show it to the user before proceeding.

Add Cloud Flow

Connect one or more Power Automate cloud flows to a Power Pages code site, or wire already-registered flows into additional pages/components. For new flows this skill:

Creates the adx_cloudflowconsumer metadata YAML in .powerpages-site/cloud-flow-consumer/
Assigns web roles based on the flow's scenario and target audience
Generates client-side TypeScript/JavaScript service code to trigger the flow with CSRF authentication

For already-registered flows, the skill skips metadata and role creation and goes straight to client-side integration — wiring the existing flow into new UI locations.

Core Principles

Multiple flows in one run: The user can add several flows at once. All flows are planned together and implemented together before asking for deployment.
Ask before acting: Present a full HTML plan (all flows, roles, reasoning) before creating any files.
Web roles drive access: Every flow must have at least one web role. Anonymous Users role is valid but must be confirmed.
Scenario determines roles: Understand what each flow does and who triggers it before picking roles.
Use TaskCreate/TaskUpdate: Track all phases upfront before starting any work.

Prerequisites:

An existing Power Pages code site with .powerpages-site deployed

PAC CLI authenticated (pac auth who must succeed)

Azure CLI authenticated (az login --allow-no-subscriptions works whether or not your account has an Azure subscription — Dataverse and Power Platform tokens are AAD-scoped)

Initial request: $ARGUMENTS

Workflow

Verify Prerequisites — Locate the project, confirm .powerpages-site exists, inventory web roles and existing flows
List Available Flows — Fetch flows from the Power Automate Flow RP API
Select Flows & Understand Scenarios — User picks one or more flows; determine scenario and audience for each
Determine Web Roles — Propose minimum roles per flow with reasoning
Review Plan — Render HTML plan for all flows; get user approval
Create Metadata — Write .cloudflowconsumer.yml for each flow; create missing web roles first
Client-Side Integration — Generate typed service code to call each flow from the frontend
Verify & Summarize — Validate all YAMLs, record skill usage, offer deployment

Phase 1: Verify Prerequisites

Goal: Locate the Power Pages project and confirm all prerequisites are met

Actions:

Create todo list with all 8 phases (see Progress Tracking table)

1.1 Locate Project

Look for powerpages.config.json in the current directory or immediate subdirectories.

If not found: Tell the user to create a site first with /create-site.

1.2 Read Config

Read powerpages.config.json to get the siteName (used for display and plan rendering).

1.3 Check `.powerpages-site` Exists

Look for the .powerpages-site folder in the project root.

If not found:

Use AskUserQuestion:

Question	Options
`.powerpages-site` is required to add cloud flows. Would you like to deploy the site now?	Yes, deploy now (Required), Cancel

If "Yes, deploy now": Invoke /deploy-site first, then continue to Phase 2. If "Cancel": Stop.

1.4 Read Existing Web Roles

Read all .webrole.yml files from .powerpages-site/web-roles/ to inventory available roles. Note each role's id, name, adx_anonymoususersrole, and adx_authenticatedusersrole.