Install the "setup" agent skill from https://github.com/microsoft/power-platform-skills/tree/main/plugins/power-automate/skills/setup into .claude/skills/setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add microsoft/power-platform-skills --skill setup -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "setup" agent skill from https://github.com/microsoft/power-platform-skills/tree/main/plugins/power-automate/skills/setup into .agents/skills/setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add microsoft/power-platform-skills --skill setup -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "setup" agent skill from https://github.com/microsoft/power-platform-skills/tree/main/plugins/power-automate/skills/setup into .cursor/skills/setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add microsoft/power-platform-skills --skill setup -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "setup" agent skill from https://github.com/microsoft/power-platform-skills/tree/main/plugins/power-automate/skills/setup into .gemini/skills/setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add microsoft/power-platform-skills --skill setup -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "setup" agent skill from https://github.com/microsoft/power-platform-skills/tree/main/plugins/power-automate/skills/setup into .github/skills/setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add microsoft/power-platform-skills --skill setup -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "setup" agent skill from https://github.com/microsoft/power-platform-skills/tree/main/plugins/power-automate/skills/setup into .opencode/skills/setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
setup
GitHub stars
967
Token cost
~3.5k tokens
SKILL.md length
1,396 words
Files
1
Skills in repo
87
Repo updated
First seen
Licence
MIT
At a glance
Set up Power Automate CLI prerequisites. An agent skill from microsoft/power-platform-skills.
Works in 5 steps: Check Node.js → Check Azure CLI → Azure Login → …
The user is new
SKILL.md covers Step 1: Check Node.js, Step 2: Check Azure CLI, Step 3: Azure Login and Signing in to a specific account, plus 3 more sections
Calls az, node and brew; reaches service.flow.microsoft.com and gov.service.flow.microsoft.us
What it does
Setup is an agent skill from microsoft/power-platform-skills, published by the product's own GitHub organization. Set up Power Automate CLI prerequisites. Use when the user is new, something isn't working, or they need help getting started.
Its SKILL.md is about 3.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in AI & LLM Engineering. It works with Power Automate, Microsoft Azure and Node.js. The repository describes itself as: A plugin marketplace for GitHub Copilot and other AI agents that provides Power Platform development plugins, including reusable skills, agents, and commands for building and… The licence is MIT.
Read from SKILL.md and the folder at commit 5ef4e4f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
Bash
Read
Write
Glob
Grep
AskUserQuestion
mcp__flowagent__list_environments
mcp__flowagent__set_current_env
mcp__flowagent__get_current_env
mcp__flowagent__resolve_environment
…and 53 more on the same allowed-tools line.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
az
node
brew
winget
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
service.flow.microsoft.com
gov.service.flow.microsoft.us
high.service.flow.microsoft.us
Also links to:
aka.ms
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Setup loads about 3.5k tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 1,396 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~33
When it runs· the whole SKILL.md, loaded when a task matches
~3.5k
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
You are helping a non-technical user get the Power Automate plugin working for the first time. Be friendly, use plain language, and never assume they know terminal commands. Walk them through each step one at a time.
Step 1: Check Node.js
Run silently:
bash
node --version 2>&1
If it works (prints something like v18.x.x or higher): Tell them "Node.js is installed" and move on.
If it fails or version is below 18: Tell them they need Node.js 18 or newer. Ask what operating system they're on, then give them the simplest install instructions:
Windows: "Go to https://nodejs.org, download the LTS version, and run the installer. Click Next through everything."
Mac: "Open Terminal and run: brew install node" (or direct them to nodejs.org)
After they've installed it, re-check with node --version.
Step 2: Check Azure CLI
Run silently:
bash
az --version 2>&1
If it works: Tell them "Azure CLI is installed" and move on.
If it fails: Tell them they need the Azure CLI. Ask their OS:
If it works (shows account info): Tell them who they're logged in as (show the user.name field) and ask if that's the right account.
If it fails: Tell them "Let's sign you into Azure." Then run:bash
az login
This will open their browser. Tell them: "A browser window should open. Sign in with your work account — the one you use for Power Automate."
After login completes, confirm it worked by running az account show again.
Verify token access — this catches permission issues early.
First find out which Azure cloud they're on, because the Power Automate
resource URL differs per cloud and the commercial one cannot be assumed
(GCC High / DoD tenants will fail against it):
bash
az cloud show --query name -o tsv
az cloud show
Power Automate resource
AzureCloud (commercial)
https://service.flow.microsoft.com
AzureCloud + GCC tenant
https://gov.service.flow.microsoft.us
AzureUSGovernment (GCC High)
https://high.service.flow.microsoft.us
AzureUSGovernment (DoD)
Operator-verified PA_FLOW_RESOURCE value required; no built-in audience
az cloud show cannot distinguish commercial from GCC, or GCC High from DoD —
for those, set PA_CLOUD=gcc / PA_CLOUD=dod explicitly.
DoD endpoint hosts use appsplatform.us, but that does not establish the token
audience (App ID URI). With PA_CLOUD=dod, FlowAgent requires an explicit,
operator-verified PA_FLOW_RESOURCE and fails configuration otherwise. Do not
copy a guessed audience from a hostname; obtain the correct value for the tenant.
Then request a token for the matching resource, e.g. for commercial:
bash
az account get-access-token --resource https://service.flow.microsoft.com --output json 2>&1
FlowAgent itself auto-detects the cloud the same way; you can override the
detection with PA_CLOUD=commercial|gcc|gcchigh|dod.
If it works: Move on.
If it fails with "AADSTS": The user's account may not have Power Automate access. Tell them: "Your Azure account doesn't seem to have access to Power Automate. Check with your IT admin that you have a Power Automate license."
If it fails with other errors: Show the error and suggest they contact IT support.
If they're on a sovereign cloud and connection-management commands fail: keep
the original error and inspect its code. AADSTS650057 can indicate an invalid
resource or missing app authorization; AADSTS65001 can require admin consent.
An app-not-found or consent failure may require an appropriately authorized
public-client registration and PA_CLIENT_ID=<app-id>. Network, tenant-selection
and expired-session errors need different remediation. Do not infer missing
preauthorization from the cloud name or classify every other code as unrelated.
Signing in to a specific account
Connection management authenticates separately from az — it uses its own MSAL
session with its own on-disk token cache, so az login / az account set do
not switch the account it uses.
Three tools cover this:
Tool
Use it to
list_accounts
See the cached-account inventory, effectiveConnectivityIdentity, and nextSignIn settings. Inactive tenant caches do not count as identity mismatches. Acquires no token.
switch_account
Save a preferred username, or omit it to clear the preference. Check preferencePersisted and nextSignIn: environment overrides still apply.
whoami / doctor
Compare the effective Connectivity username and tenant with Azure CLI, including different users in the same tenant.
When a connection tool fails with ServiceToServiceEnvironmentNotFound,
check identity before assuming the environment is missing. list_accounts
distinguishes the effective account from historical cached accounts. A different
username or tenant on the effective account indicates a mismatch; an unused
tenant's cache alone does not. switch_account clears the cached sign-in and
records the preferred username for reauthentication. It does not prove that
the subsequent sign-in succeeded or that environment permissions are correct.
switch_account does not change the Azure CLI identity. az is yours to set;
where the two disagree, the tool says so rather than silently re-pointing one.
reconnect keeps a recorded preference — it drops credentials, and the
preference is a stated intent rather than a credential.
It waits for pending token acquisition and cache cleanup, then clears in-memory
tokens for all Azure CLI resources as well as Connectivity. A cleanup failure
is an error, not a completed switch: fix the cache access problem and retry.
Do not continue under the assumption that credentials changed when reset failed.
On interactive sign-in FlowAgent forces the account picker by default, so the
browser's currently-signed-in account is never used silently. Two overrides:
Variable
Effect
PA_LOGIN_HINT=<upn>
Pre-select that account. Suppresses the picker, since the account is already targeted.
PA_NO_ACCOUNT_PICKER=1
Restore plain browser SSO. For single-account users who don't want the extra click.
Precedence, most specific first: PA_LOGIN_HINT, then a switch_account
preference, then PA_NO_ACCOUNT_PICKER, then the picker.
For example, switch_account with username B still targets A if
PA_LOGIN_HINT=A is set. Omitting the username clears only the stored preference;
it does not override PA_LOGIN_HINT or PA_NO_ACCOUNT_PICKER. The response
reports the effective settings instead of promising a picker in those cases.
Show full SKILL.md (465 more words)Show less
Step 4: Check the FlowAgent tools are wired
The plugin talks to Power Automate through the FlowAgent MCP server, which is
registered as flowagent in the plugin's .mcp.json and started automatically.
.mcp.json loads the bundled server/mcp.mjs through a small Node bootstrap
that resolves the plugin's installation directory (PLUGIN_ROOT, else
CLAUDE_PLUGIN_ROOT, else the current directory) and prints an actionable error
if the bundle can't be found.
If flowagent-* / mcp__flowagent__* tools appear in your tool list: tell
them "The Power Automate tools are connected" and move on.
If they're missing: the MCP server isn't registered. Fix it automatically:
Locate the installed plugin's MCP bundle. This only matches a bundle
inside a power-automate plugin directory, so it can't pick up another
plugin's MCP server:
bash
node -e "const fs=require('fs'),p=require('path'),d=p.join(process.env.HOME||process.env.USERPROFILE,'.copilot','installed-plugins');const find=(dir)=>{let out=[];for(const e of fs.readdirSync(dir,{withFileTypes:true})){const f=p.join(dir,e.name);if(e.isDirectory()){try{out=out.concat(find(f))}catch{}}else if(e.name==='mcp.mjs'&&p.basename(p.dirname(dir))==='power-automate'){out.push(dir)}}return out};try{const hits=find(d);if(hits.length===1)console.log(JSON.stringify({found:true,serverDir:hits[0],mcpMjs:p.join(hits[0],'mcp.mjs')}));else if(hits.length>1)console.log(JSON.stringify({found:false,reason:'multiple power-automate bundles',candidates:hits}));else console.log(JSON.stringify({found:false}))}catch(e){console.log(JSON.stringify({found:false,error:e.message}))}"
If it reports multiple power-automate bundles, show the candidates and ask
the user which one to register rather than guessing.
If exactly one was found, read ~/.copilot/mcp-config.json, add the
flowagent MCP entry, and write it back:
bash
node -e "const fs=require('fs'),p=require('path');const home=process.env.HOME||process.env.USERPROFILE;const cfgPath=p.join(home,'.copilot','mcp-config.json');let cfg;try{cfg=JSON.parse(fs.readFileSync(cfgPath,'utf8'))}catch{cfg={mcpServers:{}}};if(!cfg.mcpServers)cfg.mcpServers={};if(cfg.mcpServers.flowagent){console.log('already registered');process.exit(0)}const d=p.join(home,'.copilot','installed-plugins');const find=(dir)=>{let out=[];for(const e of fs.readdirSync(dir,{withFileTypes:true})){const f=p.join(dir,e.name);if(e.isDirectory()){try{out=out.concat(find(f))}catch{}}else if(e.name==='mcp.mjs'&&p.basename(p.dirname(dir))==='power-automate'){out.push(dir)}}return out};const hits=find(d);if(hits.length!==1){console.log(hits.length?'ambiguous: '+JSON.stringify(hits):'mcp.mjs not found');process.exit(1)}const mcpPath=p.join(hits[0],'mcp.mjs');cfg.mcpServers.flowagent={command:'node',args:[mcpPath]};fs.writeFileSync(cfgPath,JSON.stringify(cfg,null,2)+'\n');console.log('registered flowagent MCP at '+mcpPath)"
Tell the user to restart the agent (Copilot CLI: /restart, Claude Code:
restart the process). After restart, flowagent-* tools should appear.
If not found (plugin not installed at all): tell them to install the
plugin first:
Verify everything works end-to-end by listing the user's environments:
Preferred: call the list_environments tool.
If MCP tools aren't available: run node <path-to-plugin>/server/mcp.mjs
to confirm the bundled MCP server starts cleanly, then fix the plugin install
or .mcp.json wiring before retrying.
If it returns environments: Success! Tell them:
"Everything is working! Here are your Power Automate environments:"
Show the environments in a simple table (name, location).
If there are multiple, ask which one they mainly use and suggest setting it
as the default (the set_current_env tool, or ask "set my default
environment to <name>").
Tell them about the available skills:
/browse-flows — Browse your flows
/create-flow — Create a new flow
/debug-flow — Fix a broken flow
If it fails: Check the error. Common issues:
Auth error → go back to Step 3
Tools not found → go back to Step 4
Network error → ask if they're behind a corporate proxy/VPN
Tone Guidelines
Use "we" language: "Let's check if Node.js is installed"
Celebrate small wins: "Great, Node.js is ready!"
Don't dump all steps at once — do one at a time and confirm before moving on
If something fails, don't panic — explain what went wrong in plain English and what to do
Never show raw JSON errors to the user without explaining what they mean
Setup next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
Query official Microsoft documentation to find concepts, tutorials, and code examples across Azure, .NET, Agent Framework, Aspire, VS Code, GitHub, and more.
Kysy virallista Microsoftin dokumentaatiota löytääksesi käsitteitä, opetusohjelmia ja koodiesimerkkejä Azureen, .NET:iin, Agent Frameworkiin, Aspireen, VS Codeen, GitHubiin ja muihin liittyen.
Interroger la documentation officielle de Microsoft pour trouver des concepts, des tutoriels et des exemples de code couvrant Azure, .NET, Agent Framework, Aspire, VS Code, GitHub, et plus encore.
आधिकारिक Microsoft दस्तावेज़ों में क्वेरी करें ताकि Azure, .NET, Agent Framework, Aspire, VS Code, GitHub, और अन्य के बारे में अवधारणाएँ, ट्यूटोरियल और कोड उदाहरण मिल सकें। डिफ़ॉल्ट रूप से Microsoft…
Pretražuje službenu Microsoftovu dokumentaciju kako bi pronašao koncepte, vodiče i primjere koda za Azure, .NET, Agent Framework, Aspire, VS Code, GitHub i još mnogo toga.
Inspects and configures the security headers a Power Pages site sends to browsers — Content Security Policy, frame and clickjacking protection, cross-origin sharing, cookie behavior, and related…
Set up Power Automate CLI prerequisites. An agent skill from microsoft/power-platform-skills. Setup is an agent skill from microsoft/power-platform-skills, published by the product's own GitHub organization. Set up Power Automate CLI prerequisites.
When should I use Setup?
Setup fits situations like: the user is new; something isnt working; they need help getting started.
How do I install Setup in Claude Code?
Run `npx skills add microsoft/power-platform-skills --skill setup -a claude-code`. Or copy the skill folder (plugins/power-automate/skills/setup in microsoft/power-platform-skills) into .claude/skills/setup in your project. Claude Code loads it when a task matches its description.
How do I install Setup in Codex?
Run `npx skills add microsoft/power-platform-skills --skill setup -a codex`. Or copy the skill folder (plugins/power-automate/skills/setup in microsoft/power-platform-skills) into .agents/skills/setup in your project. Codex loads it when a task matches its description.
Can I use Setup in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add microsoft/power-platform-skills --skill setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/setup, .gemini/skills/setup, .github/skills/setup and .opencode/skills/setup in your project.
SKILL.md names 4 domains. In commands or code: service.flow.microsoft.com, gov.service.flow.microsoft.us and high.service.flow.microsoft.us; the agent is likely to contact these when it follows the instructions. As links in the text: aka.ms. This is read from the text; nothing was executed.
Is Setup safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Setup use?
Setup is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Setup use?
About 3.5k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Setup?
Skills that share tags, products or a category with Setup: Microsoft Docs (microsoft/ai-agents-for-beginners, 77k stars), Microsoft Docs (microsoft/ai-agents-for-beginners, 77k stars), Microsoft Docs (microsoft/ai-agents-for-beginners, 77k stars) and Microsoft Docs (microsoft/ai-agents-for-beginners, 77k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Setup?
microsoft (a GitHub organization, an official publisher) maintains it in microsoft/power-platform-skills, which has 967 GitHub stars. The repository holds 87 skills in this directory. The repository was last updated on October 6, 2026.
