add-connector · microsoft, code-apps — Claude Code skill: what it does, how to install
add-connector adds any generic Power Platform connector to a Power Apps code app when a dedicated skill does not exist.
MIT ★ 1,167 updated 2026-10-29
/plugin marketplace add microsoft/power-platform-skills
/plugin install code-apps-preview@power-platform-skillsWhat add-connector does
This skill acts as a generic fallback for integrating Power Platform connectors into code apps. Upon receiving a connector name, it checks whether a specialized tool is already available. If a connector like Dataverse, SharePoint, Teams, Excel, or Azure DevOps is detected, it delegates immediately and stops.
For general connectors, it runs pa app add data-source. A valid connection ID is required, which it retrieves using /list-connections or asks you to create in the Power Apps portal. Tabular data sources like SQL also require dataset and table arguments.
Once added, it inspects generated TypeScript interfaces in src/generated/services/ with Grep, assists with method signatures, and verifies everything with npm run build without deploying.
What it helps with
- add arbitrary Power Platform connectors to a code app
- inspect generated TypeScript service files without loading full files
- delegate integration tasks to dedicated connector skills automatically
- verify generated client code with npm run build
Example prompts for the agent
- /add-connector sql
- Add the azureblob connector to my Power Apps code app
- /add-connector office365users
How to install add-connector
1Plugin marketplace
/plugin marketplace add microsoft/power-platform-skills/plugin install code-apps-preview@power-platform-skillsThis installs the whole code-apps-preview plugin with all its skills
2Skills CLI (Vercel)
npx skills add microsoft/power-platform-skills --skill add-connector -a claude-code3Manually: put the files in place
~/.claude/skills/add-connector/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/add-connector/
1Skills CLI (Vercel)
npx skills add microsoft/power-platform-skills --skill add-connector -a codex2Manually: put the files in place
.agents/skills/add-connector/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add microsoft/power-platform-skills --skill add-connector -a cursor2Manually: put the files in place
.cursor/skills/add-connector/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install microsoft/power-platform-skills plugins/code-apps/skills/add-connector2Manually: put the files in place
.github/skills/add-connector/SKILL.md1Skills CLI (Vercel)
npx skills add microsoft/power-platform-skills --skill add-connector -a gemini-cli2Platform CLI
gemini skills install https://github.com/microsoft/power-platform-skills --path plugins/code-apps/skills/add-connectorManually: put the files in place
.devin/skills/add-connector/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 add-connector
How to install add-connector in Claude Code?
Run two commands in sequence: first /plugin marketplace add microsoft/power-platform-skills, then /plugin install code-apps-preview@power-platform-skills.
What does add-connector do?
It identifies the connector API name, finds the connection ID, configures the data source with the pa CLI, and checks build integrity.
How does it handle common connectors like Teams or SharePoint?
It checks incoming arguments against known dedicated tools and routes execution straight to specialized skills such as /add-teams or /add-sharepoint.
Source text
SKILL.md · MIT
---
name: add-connector
description: Adds any Power Platform connector to a Power Apps code app. Generic fallback for connectors not covered by a specific skill.
user-invocable: true
allowed-tools: Read, Edit, Write, Grep, Glob, Bash, LSP, TaskCreate, TaskUpdate, TaskList, TaskGet, AskUserQuestion, Skill
model: sonnet
---
**📋 Shared Instructions: [shared-instructions.md](${PLUGIN_ROOT}/shared/shared-instructions.md)** - Cross-cutting concerns.
# Add Connector (Generic)
Fallback skill for any connector not covered by a specific `/add-*` skill. For common connectors, prefer the dedicated skills:
- `/add-dataverse` -- Dataverse tables
- `/add-azuredevops` -- Azure DevOps
- `/add-teams` -- Microsoft Teams
- `/add-excel` -- Excel Online (Business)
- `/add-onedrive` -- OneDrive for Business
- `/add-sharepoint` -- SharePoint Online
- `/add-office365` -- Office 365 Outlook (calendar, email, contacts)
- `/add-workiq` -- Work IQ (M365 Copilot Search)
## Workflow
1. Check Memory Bank → 2. Identify Connector → 3. Add Connector → 4. Inspect & Configure → 5. Build → 6. Update Memory Bank
---
### Step 1: Check Memory Bank
Check for `memory-bank.md` per [shared-instructions.md](${PLUGIN_ROOT}/shared/shared-instructions.md).
### Step 2: Identify Connector
**If `$ARGUMENTS` is provided or the caller already specified the connector**, use it directly and skip the question below.
Otherwise, ask the user which connector they want to add. Browse available connectors: [Connector Reference](https://learn.microsoft.com/en-us/connectors/connector-reference/)
**Before proceeding, check if the connector has a dedicated skill. If it does, delegate immediately and STOP:**
| Connector API name | Delegate to |
| --------------------------- | ------------------ |
| `shared_a365copilotchatmcp` | `/add-workiq` |
| `sharepointonline` | `/add-sharepoint` |
| `teams` | `/add-teams` |
| `excelonlinebusiness` | `/add-excel` |
| `onedriveforbusiness` | `/add-onedrive` |
| `azuredevops` | `/add-azuredevops` |
| `office365` | `/add-office365` |
| `commondataservice` | `/add-dataverse` |
Invoke the appropriate skill with the same `$ARGUMENTS` and **do not continue this skill's workflow**.
Common connector API names:
- `sharepointonline`, `teams`, `excelonlinebusiness`, `onedriveforbusiness`
- `azuredevops`, `azureblob`, `azurequeues`
- `office365`, `office365users`, `office365groups`
- `sql`, `commondataservice`
### Step 3: Add Connector
**First, find the connection ID** (see [connector-reference.md](${PLUGIN_ROOT}/shared/connector-reference.md)):
Run the `/list-connections` skill. Find the connector in the output. If none exists, direct the user to create one using the environment-specific Connections URL — construct it from the active environment ID in context (from `power.config.json` or a prior step): `https://make.powerapps.com/environments/<environment-id>/connections` → **+ New connection** → search for the connector → Create.
```bash
# Non-tabular connectors (Teams, Azure DevOps, etc.)
pa app add data-source --connector <connector-api-name> -c <connection-id>
# Tabular connectors (SharePoint, Excel, SQL, etc.) -- also need dataset and table
pa app add data-source --connector <connector-api-name> -c <connection-id> -d '<dataset>' --table '<table>'
```
**Parameter reference:**
- `--connector` (apiId) -- connector name (e.g., `sharepointonline`, `teams`). On the flat `power-apps` binary this is `--api-id`/`-a`.
- `-c` (connectionId) -- **required** for all non-Dataverse connectors. Get from `/list-connections`.
- `-d` (dataset) -- required for tabular datasources (e.g., SharePoint site URL, SQL database). Not needed for Dataverse.
- `--table` (table) -- table/list name for tabular datasources (e.g., SharePoint list, Dataverse table logical name). On the flat `power-apps` binary this is `--resource-name`/`-t`.
### Step 4: Inspect & Configure
After adding, inspect the generated files. **Generated service files can be very large** -- use `Grep` to find specific methods instead of reading the entire file:
```
Grep pattern="async \w+" path="src/generated/services/<Connector>Service.ts"
```
Files to check:
- `src/generated/services/<Connector>Service.ts` -- available operations and their parameters
- `src/generated/models/<Connector>Model.ts` -- TypeScript interfaces (if generated)
- `.power/schemas/<connector>/` -- connector schema and configuration
For each method the user needs:
1. Grep for the method name to find its signature
2. Read just that method's section (use `offset` and `limit` parameters on Read)
3. Identify required vs optional parameters and response type
Help the user write code using the generated service methods.
### Step 5: Build
```bash
npm run build
```
Fix TypeScript errors before proceeding. Do NOT deploy yet.
### Step 6: Update Memory Bank
Update `memory-bank.md` with: connector added, configured operations, build status.
© Microsoft · MIT · microsoft/power-platform-skills
Similar skills
All skills for Cloud: AWS, Azure, GCP →add-connector by other authors comes first.