From code-apps-preview
Adds any Power Platform connector to Power Apps code apps as generic fallback for connectors without dedicated skills. Delegates common ones like SharePoint, Teams, Excel to specific skills.
npx claudepluginhub microsoft/power-platform-skills --plugin code-apps-previewThis skill is limited to using the following tools:
**๐ Shared Instructions: [shared-instructions.md](${CLAUDE_PLUGIN_ROOT}/shared/shared-instructions.md)** - Cross-cutting concerns.
Routes to specialized skills for adding Power Apps data sources like Dataverse (business data), SharePoint lists, Teams messages, Excel, OneDrive, and Office 365 based on user goals.
Generates Power Platform custom connectors with MCP integration for Copilot Studio, including schema generation, C# scripts, validation, troubleshooting, and certification prep.
Scaffolds Vite + React + TypeScript project for Power Apps Code Apps with PAC CLI, SDK integration, connectors, configs, scripts, and sample authenticated UI.
Share bugs, ideas, or general feedback.
๐ Shared Instructions: shared-instructions.md - Cross-cutting concerns.
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)Check for memory-bank.md per shared-instructions.md.
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
Before proceeding, check if the connector has a dedicated skill. If it does, delegate immediately and STOP:
| Connector API name | Delegate to |
|---|---|
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, onedriveforbusinessazuredevops, azureblob, azurequeuesoffice365, office365users, office365groupssql, commondataserviceFirst, find the connection ID (see 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.
# Non-tabular connectors (Teams, Azure DevOps, etc.)
pwsh -NoProfile -Command "pac code add-data-source -a <connector-api-name> -c <connection-id>"
# Tabular connectors (SharePoint, Excel, SQL, etc.) -- also need dataset and table
pwsh -NoProfile -Command "pac code add-data-source -a <connector-api-name> -c <connection-id> -d '<dataset>' -t '<table>'"
Parameter reference:
-a (apiId) -- connector name (e.g., sharepointonline, teams)-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.-t (table) -- table/list name for tabular datasources (e.g., SharePoint list, Dataverse table logical name)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 parameterssrc/generated/models/<Connector>Model.ts -- TypeScript interfaces (if generated).power/schemas/<connector>/ -- connector schema and configurationFor each method the user needs:
offset and limit parameters on Read)Help the user write code using the generated service methods.
npm run build
Fix TypeScript errors before proceeding. Do NOT deploy yet.
Update memory-bank.md with: connector added, configured operations, build status.