Skip to main content
skill CX Codex

add-datasource · microsoft, code-apps — Claude Code skill: what it does, how to install

add-datasource — a router skill that asks what your Power Apps code app should do, then hands the job to the right connector skill. Useful when you need data but aren't sure which connector fits.

MIT ★ 1,167 updated 2026-10-29

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add microsoft/power-platform-skills
/plugin install code-apps-preview@power-platform-skills
Open on GitHub

What add-datasource does

A router skill for Power Apps code apps. It wires nothing up on its own. First it asks what the app should do, then hands the job to a focused skill: /add-dataverse, /add-teams, /add-sharepoint, /add-office365, /add-excel, /add-onedrive, /add-azuredevops, /add-mcscopilot, or the catch-all /add-connector.

The routing table sits in the skill file. Actions beat vague nouns: want to send mail or create a file, and you get the connector for that action. It reads memory-bank.md before starting. Pass the goal as an argument and the question step is skipped. Several capabilities in one request get handled one skill at a time.

Nothing gets connected by this skill alone, so it only pays off together with the /add-* family. Already know you need Excel? Call /add-excel and skip the router.

What it helps with

  • turn a plain-language goal into the right connector
  • connect Dataverse without Power Platform jargon
  • chain several data sources in one session
  • explain in plain words why one connector suits the task
  • pass the goal up front and skip the questions

Example prompts for the agent

  • Run /add-datasource: the app needs to send mail from a shared mailbox.
  • /add-datasource I want to keep support tickets in custom tables.
  • We need file uploads and a task list — pick the data sources for me.

How to install add-datasource

1Plugin marketplace

/plugin marketplace add microsoft/power-platform-skills
/plugin install code-apps-preview@power-platform-skills

This installs the whole code-apps-preview plugin with all its skills

2Skills CLI (Vercel)

npx skills add microsoft/power-platform-skills --skill add-datasource -a claude-code

3Manually: put the files in place

~/.claude/skills/add-datasource/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/add-datasource/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about add-datasource

How to install add-datasource in Claude Code?

Add the marketplace first with /plugin marketplace add microsoft/power-platform-skills, then run /plugin install code-apps-preview@power-platform-skills.

What does add-datasource do?

It asks what your app should be able to do, then routes to a specialized skill such as /add-dataverse, /add-teams or /add-office365.

How is add-datasource different from /add-connector?

The router picks a specific connector from your goal. /add-connector covers everything else, including goals that are still vague.

Source text

SKILL.md · MIT
---
name: add-datasource
description: 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.
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 Data Source

Router skill that understands the user's goal and connects them to the right data source -- without requiring them to know Power Platform terminology.

## Workflow

### Check Memory Bank

Check for `memory-bank.md` per [shared-instructions.md](${PLUGIN_ROOT}/shared/shared-instructions.md).

### Understand the Goal

1. **If `$ARGUMENTS` is provided or the caller already specified what's needed**, use it directly and skip the question below.
2. Otherwise, ask the user **what they want their app to do** -- not which connector to use. Focus on the end goal. Example questions:
   - "What kind of data does your app need to work with?"
   - "What should your app be able to do? (e.g., search company info, manage tasks, send messages)"
3. Based on their answer, **recommend the best approach** and explain *why* it's the right fit. The user shouldn't need to know the difference between Dataverse, SharePoint, or other connectors -- that's our job.

### Route to the Right Skill

Map the user's goal to the appropriate skill:

| User's goal | Best approach | Invoke |
|-------------|---------------|--------|
| Store and manage structured business data (custom tables, forms, CRUD) | Dataverse is the platform's native database | `/add-dataverse` |
| Track work items, bugs, builds, or pipelines | Azure DevOps connector | `/add-azuredevops` |
| Send or read Teams messages, post to channels | Teams connector | `/add-teams` |
| Read/write Excel spreadsheet data | Excel Online (Business) connector | `/add-excel` |
| Upload, download, or manage files | OneDrive for Business connector | `/add-onedrive` |
| Work with SharePoint lists or document libraries | SharePoint Online connector | `/add-sharepoint` |
| Send emails, read inbox, manage calendar events | Office 365 Outlook connector | `/add-office365` |
| Invoke an AI agent or copilot built in Copilot Studio | Copilot Studio connector | `/add-mcscopilot` |
| Something else or not sure | Generic connector (we'll figure it out) | `/add-connector` |

**Important routing rules:**
- When the user wants to **perform actions** (send an email, post a message, create a file), use the specific connector for that action (e.g., `/add-office365` for sending email, `/add-teams` for posting messages).

4. If the user wants multiple capabilities, invoke each skill in sequence.

### When the User Isn't Sure

If the user describes a vague goal (e.g., "I need data for my app"), guide them:

1. Ask what their app does and who uses it
2. Ask what data they need to display or interact with
3. Recommend the simplest approach that meets their needs
4. Explain the recommendation in plain language (avoid jargon like "connector", "Dataverse", "tabular data source" unless the user uses those terms first)

© Microsoft · MIT · microsoft/power-platform-skills

Similar skills

All skills for Agent setup: memory, context, orchestration →

add-datasource by other authors comes first.

add-datasource Microsoft The add-datasource skill identifies the data an Expo/React Native app needs and directs the request to the matching Power Platform skill. CX Codex +1 ★ 1,167repo stars Power Platform Expert official github Power Platform Expert — a GitHub Copilot subagent for Power Platform work: Power Apps, Dataverse, connectors, Power Automate. It answers questions on architecture, security and deployment for Microsoft solutions. CX Codex +1 ★ 41,430repo stars pcf-tooling official github pcf-tooling — a GitHub Copilot rule that brings Microsoft Power Platform CLI context into Power Apps Component Framework projects. Triggers on TypeScript, JavaScript, JSON, XML and PCF project files. CX Codex +1 ★ 41,430repo stars MCP Dataverse codeurali Connects AI coding assistants directly to Microsoft Dataverse for live schema inspection, FetchXML queries, and batch record updates. CX Codex +1 ★ 18repo stars earth2studio-create-datasource NVIDIA Earth-2 Team earth2studio-create-datasource is a Claude Code skill that builds and validates Earth2Studio wrappers for connecting remote data sources to its async infrastructure. CX Codex +1 587installs mfs-ingest zilliztech mfs-ingest is a Claude Code skill that registers MFS data sources, edits connector settings, and starts a fresh sync. It can also list configured connectors or help investigate a sync that misses data. CX Codex +1 ★ 159repo stars docyrus-api-dev Docyrus The docyrus-api-dev skill guides Docyrus API integration with OAuth2, data-source requests, query payloads, and external connectors. Use it while building a Docyrus-backed app. CX Codex +1 900installs

From the same set157

The whole set →
canvas-create-functionality The canvas-create-functionality subagent records app users, tasks, requirements, and observable outcomes before Canvas screens are designed. Use it to shape the requested functionality first. CX Codex ★ 1,167repo stars route-environments route-environments is a Claude Code skill that checks Power Platform environment routing and shows where new makers land when they open the platform. CX Codex +1 ★ 1,167repo stars add-excel add-excel attaches the Excel Online (Business) connector to Power Apps code apps to read and write workbook tables in OneDrive or SharePoint. CX Codex +1 ★ 1,167repo stars canvas-create-builder canvas-create-builder is a Claude Code subagent that writes a single Power Apps screen YAML file from approved designs. The coordinator agent runs it after layout and data bindings are verified. CX Codex ★ 1,167repo stars manage-desktop-flows manage-desktop-flows manages Power Automate Desktop RPA flows and machine groups in Claude Code. Triggers attended or unattended tasks directly from chat. CX Codex +1 ★ 1,167repo stars investigate-process investigate-process investigates broad Process Mining questions through hypotheses, comparisons, and specialist analysis. Use it when one metric cannot explain the finding. CX Codex +1 ★ 1,167repo stars analyze-variants analyze-variants — a skill for investigating business process execution variants: common and slow paths, rework cases, specific instances. CX Codex +1 ★ 1,167repo stars analyze-performance analyze-performance guides analysis of slow process activities, handoff delays, waiting times, and total workload without distorting statistical metrics. CX Codex +1 ★ 1,167repo stars

Project sponsors

Companies that keep this analytics open