Agent skill
list-connections
Lists Power Platform connections in the current environment. Use when you need a connection ID before adding a connector to a code app.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/list-connections-microsoft-power-platform-skill
SKILL.md
📋 Shared Instructions: shared-instructions.md - Cross-cutting concerns (Windows CLI compatibility, memory bank, etc.).
List Connections
Lists all Power Platform connections in the default environment using the Power Platform CLI (pac).
Workflow
- Fetch Connections → 2. Present Results
Step 1: Fetch Connections
pwsh -NoProfile -Command "pac connection list"
If pac is not authenticated, tell the user to run pwsh -NoProfile -Command "pac auth create" and try again.
Other failures:
- Non-zero exit for any reason other than auth: Report the exact output. STOP.
- No output or timeout: Run
pwsh -NoProfile -Command "pac env list"to verify pac can reach the environment, then retry once.
Step 2: Present Results
Show the connection list to the user. The Connection ID is what goes into -c <connection-id> when adding a data source.
If the needed connector is missing:
- Share the direct Connections URL using the active environment ID from context (from
power.config.jsonor a prior step):https://make.powerapps.com/environments/<environment-id>/connections→ + New connection - Search for and create the connector, then complete the sign-in/consent flow
- Re-run
/list-connectionsto get the new connection ID
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?