list-connections · microsoft, mobile-apps — Claude Code skill: what it does, how to install
list-connections finds or provisions Power Platform connections and references for Expo and React Native apps. Handy when linking data sources via CLI.
MIT ★ 1,167 updated 2026-10-29
/plugin marketplace add microsoft/power-platform-skills
/plugin install mobile-app@power-platform-skillsWhat list-connections does
The skill resolves connection identifiers (Connection ID) and reference names (Connection Reference) required by pa app add data-source. It verifies project context, checks current parameters, and executes the local Power Apps CLI using $PA connection create or $PA connection list-references.
A pre-installed project CLI is mandatory; running without --no-install is blocked. Browser-driven connection auth is disabled out of the box. If a connector lacks SSO support, you need to set POWERAPPS_CLI_ENABLE_BROWSER_CONNECTION=true or set up the link manually inside the Power Apps maker portal.
What it helps with
- retrieve a Connection ID for adding mobile data sources
- provision a Power Platform connector link through the local CLI
- list matching connection references for a specific solution ID
- get direct maker portal URLs when manual connector setup is required
Example prompts for the agent
- /list-connections shared_sharepointonline
- List connection references for solution-456 in this app
- Create a connection for connector shared_slack with display name TeamChat
How to install list-connections
1Plugin marketplace
/plugin marketplace add microsoft/power-platform-skills/plugin install mobile-app@power-platform-skillsThis installs the whole mobile-app plugin with all its skills
2Skills CLI (Vercel)
npx skills add microsoft/power-platform-skills --skill list-connections -a claude-code3Manually: put the files in place
~/.claude/skills/list-connections/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/list-connections/
1Skills CLI (Vercel)
npx skills add microsoft/power-platform-skills --skill list-connections -a codex2Manually: put the files in place
.agents/skills/list-connections/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add microsoft/power-platform-skills --skill list-connections -a cursor2Manually: put the files in place
.cursor/skills/list-connections/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install microsoft/power-platform-skills plugins/mobile-apps/skills/list-connections2Manually: put the files in place
.github/skills/list-connections/SKILL.md1Skills CLI (Vercel)
npx skills add microsoft/power-platform-skills --skill list-connections -a gemini-cli2Platform CLI
gemini skills install https://github.com/microsoft/power-platform-skills --path plugins/mobile-apps/skills/list-connectionsManually: put the files in place
.devin/skills/list-connections/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about list-connections
How to install list-connections in Claude Code?
Register the marketplace and install the package using these commands in order: /plugin marketplace add microsoft/power-platform-skills followed by /plugin install mobile-app@power-platform-skills.
What does list-connections do?
It discovers or initializes Power Platform connections through the Power Apps CLI so Expo or React Native mobile projects can connect to data sources.
Why does connection creation report browser sign-in disabled?
Browser-based flows are off by default. Export POWERAPPS_CLI_ENABLE_BROWSER_CONNECTION=true in your shell or authenticate the connector via the maker portal.
Source text
SKILL.md · MIT
---
name: list-connections
description: Use to find or create a Power Platform connection ID or reference for an Expo/React Native Power Apps mobile app.
user-invocable: true
allowed-tools: Read, Bash
model: haiku
---
> **Plugin check**: Run `node "${PLUGIN_ROOT}/scripts/check-version.js"` - if it outputs a message, show it to the user before proceeding.
**📋 Shared instructions: [shared-instructions.md](${PLUGIN_ROOT}/shared/shared-instructions.md)** — read first for cross-cutting concerns (Windows CLI compatibility, memory bank, etc.).
# List Connections
**App root:** before any project read or command, execute
[app-working-directory.md](${PLUGIN_ROOT}/shared/references/app-working-directory.md).
Reuse the resolved absolute `working_dir` for every shell call and
file tool, including auth retries and the environment read used for portal URLs.
Forwarded owner context is required for child calls; do not fall back to the
launch directory. Reapply the guard and arguments in each fresh call.
Finds or creates a Power Platform connection with the Power Apps CLI. Returns the **Connection ID** or **Connection Reference** that callers feed into `pa app add data-source`.
## Workflow
1. Get Connection → 2. Present Results
---
### Step 1 — Get Connection
**Telemetry checkpoint: `resolve_power_platform_connection`**
Use one of the supported paths below.
If the caller already provided a connection ID, validate the connector/API ID from context and return it as-is for `--connection-id`.
Preserve any supplied connection reference as well; do not create a replacement.
Creation requires current approval for the selected environment and connector.
For `--plan-only` or a planning-phase handoff, perform only permitted read-only
lookup and return missing access/identity to the owner; never create a connection
to unblock discovery. The invocation marker does not grant creation consent.
If the caller provided a connector API ID and needs a new connection, create it from the app root:
> Resolve the CLI first (see [cli-binary.md](${PLUGIN_ROOT}/shared/cli-binary.md)): run as `$PA connection create …` (`npx --no-install pa …`), never a bare `pa`. On `power-apps`-only projects, translate to `power-apps create-connection --api-id …`.
```bash
cd -- '<working_dir>' || { echo "BLOCKED: cannot enter working_dir" >&2; exit 1; }
$PA connection create --connector <api-id> --json
```
Use the returned `connectionId` for `--connection-id <connectionId>`. Optional display names are supported:
```bash
cd -- '<working_dir>' || { echo "BLOCKED: cannot enter working_dir" >&2; exit 1; }
$PA connection create --connector <api-id> --display-name '<display-name>' --json
```
Browser-based connection creation is disabled by default. If the connector is not SSO-eligible and the command reports that browser creation is disabled, tell the user to either set `POWERAPPS_CLI_ENABLE_BROWSER_CONNECTION=true` and rerun the command, or create the connection in the maker portal.
### Step 1b — Fetch Connection References When Solution-Aware
If the caller provided a solution ID and needs a connection reference name, list connection references from the app root:
```bash
cd -- '<working_dir>' || { echo "BLOCKED: cannot enter working_dir" >&2; exit 1; }
$PA connection list-references --solution-id <solution-id> --json
```
If a matching connection reference exists, return its reference name for `--connection-ref <connection-ref>`.
If `pa connection create` or `pa connection list-references` fails because of auth, wrong user, multiple accounts, no output, or timeout, follow shared-instructions command-failure handling and retry once from the same guarded root. A missing app-local CLI is a blocker, not permission to retry without `--no-install` or install another version.
**Other failures:**
- Non-zero exit for any reason other than auth: report the exact output. STOP.
### Step 2 — Present Results
Show the supported add path. A **Connection ID** goes into `--connection-id <connection-id>` when adding a data source. When Step 1b was requested, also show matching connection references; a **Connection Reference** goes into `--connection-ref <connection-ref>`.
**If the needed connector is missing:**
1. Share the direct Connections URL using the active environment ID from context (read from `<working_dir>/power.config.json` `environmentId`):
`https://make.powerapps.com/environments/<environment-id>/connections` → **+ New connection**
2. Search for and create the connector, then complete the sign-in / consent flow
3. Rerun `/list-connections <api-id>` or provide the portal connection ID so the data-source skill can continue
© Microsoft · MIT · microsoft/power-platform-skills
Similar skills
All skills for Mobile →list-connections by other authors comes first.