Add Connector
Use when adding a Power Platform connector to an Expo/React Native Power Apps mobile...
Install
npx skills add microsoft/power-platform-skills --skill add-connector -g -a claude-code -y- Repository
- microsoft/power-platform-skills1.1k
- Category
- Mobile
- Updated
- 4d ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Use when adding a Power Platform connector to an Expo/React Native Power Apps mobile app and no dedicated mobile connector skill exists.
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 | Connector reference: connector-reference.md, read both first.
Add Connector (Generic)
App root: before any project read or command, execute
app-working-directory.md.
Use its resolved absolute working_dir for every shell call and file tool,
including referenced commands and delegated skills; never inherit a prior cd.
Entry routing: use the shared App feature entry points preflight before the workflow below.
Invocation scope: follow Data-source invocation scope before the workflow below. This skill owns connector bindings and generated services, not a full-app plan or screen implementation.
For a standalone request, approve the current data-source delta before each
mutation: the exact connector, environment, binding, and dataset/table or
procedure as applicable. Connection creation needs explicit approval too.
An approved child reuses only its owner's current scope; a missing choice may
be resolved read-only, but a changed scope returns to that owner.
For --plan-only or a planning-phase handoff, return the proposed bindings and
unresolved choices before connection creation or pa app add data-source.
Do not update the app plan, memory-bank, configuration, or generated files on
that path; missing discovery access is not permission to create a connection.
Action connectors do not imply Dataverse Data Model changes.
