# Add Datasource

Use when adding an unspecified data source to an Expo/React Native Power Apps mobile...

- Repository: https://github.com/microsoft/power-platform-skills (1098 stars)
- Category: Mobile
- License: MIT
- Last updated: 2026-10-31
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add microsoft/power-platform-skills --skill add-datasource -g -a claude-code -y`
Codex: `npx skills add microsoft/power-platform-skills --skill add-datasource -g -a codex -y`
Cursor: `npx skills add microsoft/power-platform-skills --skill add-datasource -g -a cursor -y`
Gemini CLI: `npx skills add microsoft/power-platform-skills --skill add-datasource -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add microsoft/power-platform-skills`

## Description

Use when adding an unspecified data source to an Expo/React Native Power Apps mobile app; routes to Dataverse, SharePoint, or another connector.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

> **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](${PLUGIN_ROOT}/shared/shared-instructions.md)**, read first.

# Add Data Source

**Entry routing:** use the shared [App feature entry points](../../shared/shared-instructions.md#app-feature-entry-points)
preflight before the workflow below.

**Invocation scope:** follow [Data-source invocation scope](../../shared/shared-instructions.md#data-source-invocation-scope)
before any project read or the workflow below. Resolve the absolute app root
before reading memory-bank. Routing selects a data workflow, not implementation
approval or a full-app integration workflow.

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

**Telemetry checkpoint: `route_data_source_request`**

The rest: https://github.com/microsoft/power-platform-skills/blob/HEAD/plugins/mobile-apps/skills/add-datasource/SKILL.md