Menu
Use when the user asks to find, create, or look up a Power Platform connection ID or connection reference for the current environment.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
| name | list-connections |
| description | Use when the user asks to find, create, or look up a Power Platform connection ID or connection reference for the current environment. |
| user-invocable | true |
| allowed-tools | Bash |
| model | haiku |
๐ Shared instructions: shared-instructions.md โ cross-cutting concerns (Windows CLI compatibility, memory bank, etc.).
Finds or creates a Power Platform connection with the Power Apps CLI. Returns the Connection ID or Connection Reference that callers feed into npx power-apps add-data-source.
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.
If the caller provided a connector API ID and needs a new connection, create it from the app root:
npx power-apps create-connection --api-id <api-id> --json
Use the returned connectionId for --connection-id <connectionId>. Optional display names are supported:
npx power-apps create-connection --api-id <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.
If the caller provided a solution ID and needs a connection reference name, list connection references from the app root:
npx power-apps list-connection-references --solution-id <solution-id> --json
If a matching connection reference exists, return its reference name for --connection-ref <connection-ref>.
If npx power-apps create-connection or list-connection-references fails because of auth, wrong user, multiple accounts, no output, or timeout, follow shared-instructions command-failure handling and retry once.
Other failures:
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:
power.config.json environmentId):
https://make.powerapps.com/environments/<environment-id>/connections โ + New connection/list-connections <api-id> or provide the portal connection ID so the data-source skill can continueUse when the user wants to add a Power Platform connector to a mobile app and there is no dedicated /add-* skill for that connector (Dataverse and SharePoint have their own skills).
Use when the user wants to add a data source to a mobile app but hasn't said which kind (Dataverse table, SharePoint list, or other connector).
Use when the user wants to add Dataverse tables (existing or new) to a Power Apps mobile app, extend an existing Dataverse table with new columns, or apply an approved data model plan.
Internal implementation skill invoked by /add-native for camera, image picker, barcode scanner, QR scanner, and camera/gallery Dataverse artifact workflows.
Internal implementation skill invoked by /add-native for native background GPS tracking with durable storage and Dataverse sync using @microsoft/power-apps-native-bglocation.
Internal implementation skill invoked by /add-native for app-generated PDF report workflows using expo-print and, when present, expo-sharing.