Skip to main content
ClaudeWave
Skill358 estrellas del repoactualizado today

add-data-source

The add-data-source skill guides users through adding data sources, connections, and API connectors to Canvas Apps in Power Apps Studio, since these cannot be added programmatically. Use this skill when users request to connect to SharePoint, Dataverse, SQL, Excel, OneDrive, Teams, Office 365, or similar data sources. The skill informs users of the manual Studio steps required, waits for confirmation, then verifies the connection is available through the MCP server before proceeding with development work.

Instalar en Claude Code
Copiar
git clone --depth 1 https://github.com/microsoft/power-platform-skills /tmp/add-data-source && cp -r /tmp/add-data-source/plugins/canvas-apps/skills/add-data-source ~/.claude/skills/add-data-source
Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

SKILL.md

Data sources, connections, and API connectors cannot be added by the coding agent — they must be added through the Power Apps Studio interface. This skill informs the user, guides them to add the connection in their Studio session, verifies it is available via the MCP server, and then continues with any pending work.

## Phase 0 — Identify the Connection Type

From the user's request, determine what they want to add and how to verify it:

| Request type | Verify with |
|---|---|
| Data source (SharePoint list, Dataverse table, SQL table, Excel file, OneDrive, etc.) | `list_data_sources` |
| API / connector (Office 365 Users, Teams, custom connector, etc.) | `list_apis` |
| Unclear | Both `list_data_sources` and `list_apis` |

Note what the user is trying to add so you can look for it by name in Phase 3.

## Phase 1 — Inform the User

Explain that this step requires action in their Studio session. Tell the user:

- The coding agent cannot add data sources or connections programmatically — this must be done directly in Power Apps Studio.
- To add the connection, follow these steps in their open Studio session:
  1. Open the **Data** panel in the left sidebar
  2. Click **Add data**
  3. Search for the data source or connector they want (e.g., "SharePoint", "Dataverse", "SQL Server", "Office 365 Users")
  4. Follow the authentication prompts and select the specific table, list, file, or dataset
- Once added, the connection will be available to the MCP server and you can continue.

## Phase 2 — Wait for Confirmation

Use `AskUserQuestion` to pause until the user has completed the steps in Studio:

> "Please add the data source or connection in your Power Apps Studio session. Reply here when it's ready and I'll verify the connection before continuing."

Do not proceed until the user confirms they have added it.

## Phase 3 — Verify the Connection

Once the user confirms, call the appropriate MCP tools to check that the connection is now available:

- If the request was for a **data source**: call `list_data_sources`
- If the request was for an **API / connector**: call `list_apis`
- If the type was unclear: call both in parallel

Scan the results for the connection the user added:

**Found** — Confirm to the user that the data source or connection is now visible to the agent. Include the exact name as returned by the MCP tool (this is how it must be referenced in Power Fx formulas). If it is a data source, call `get_data_source_schema` to retrieve its column names and types, and include the schema summary in your response so it is ready for use in edits. Similarly, for APIs/connectors, call `describe_api` to retrieve the available endpoints and their parameters, and include the schema summary in your response.

**Not found** — Inform the user that the connection is not yet visible. Ask them to:
1. Confirm they completed the Studio steps and the connection appears in the Data panel there.
2. Check that their Studio session is still active (the MCP server must be connected to a live coauthoring session).
3. Let you know when ready to try again.

Use `AskUserQuestion` to wait for their follow-up, then re-run Phase 3.

## Phase 4 — Continue

After the connection is confirmed:

- If the user had a pending task (e.g., "add SharePoint as a data source, then build a gallery"), continue with that work now using the verified connection name and schema.
- If adding the connection was the only request, summarize what was confirmed (connection name, type, and schema if applicable) and suggest a natural next step (e.g., building a screen or gallery that uses the new data).
canvas-appSkill

Creates or edits a Power Apps Canvas App through the Canvas Authoring MCP coauthoring session. Handles new app generation from requirements, simple inline edits, and complex multi-screen changes with parallel screen builders. Triggers on requests to create, build, generate, modify, update, change, or edit a Canvas App or .pa.yaml files.

configure-canvas-mcpSkill

Configure the Canvas Authoring MCP server for the current coauthoring session. USE WHEN "configure MCP", "set up MCP server", "MCP not working", "connect Canvas Apps MCP", "canvas-authoring not available", "MCP not configured", "set up canvas apps". DO NOT USE WHEN prerequisites are missing — direct the user to install .NET 10 SDK first.

generate-canvas-appSkill

[DEPRECATED — use canvas-app instead] Generate a complete Power Apps canvas app.

report-issueSkill

>

add-azuredevopsSkill

Adds Azure DevOps connector to a Power Apps code app. Use when querying work items, creating bugs, managing pipelines, or making ADO API calls.

add-connectorSkill

Adds any Power Platform connector to a Power Apps code app. Generic fallback for connectors not covered by a specific skill.

add-datasourceSkill

Adds a data source or connector to a Power Apps code app. Asks what the user wants to accomplish and routes to the appropriate specialized skill.

add-dataverseSkill

Adds Dataverse tables to a Power Apps code app with generated TypeScript models and services. Can also create new Dataverse tables. Use when connecting to Dataverse, adding tables, creating schema, or querying Dataverse data.