一键导入
add-datasource
Use when the user wants to add a data source to a mobile app but hasn't said which kind (Dataverse table, SharePoint list, or other connector).
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Use when the user wants to add a data source to a mobile app but hasn't said which kind (Dataverse table, SharePoint list, or other connector).
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
Use when the user wants to add a Power Platform connector to a mobile app and there is no dedicated /add-* skill for that connector (Dataverse and SharePoint have their own skills).
Use when the user wants to add Dataverse tables (existing or new) to a Power Apps mobile app, extend an existing Dataverse table with new columns, or apply an approved data model plan.
Internal implementation skill invoked by /add-native for camera, image picker, barcode scanner, QR scanner, and camera/gallery Dataverse artifact workflows.
Internal implementation skill invoked by /add-native for native background GPS tracking with durable storage and Dataverse sync using @microsoft/power-apps-native-bglocation.
Internal implementation skill invoked by /add-native for app-generated PDF report workflows using expo-print and, when present, expo-sharing.
Internal implementation skill invoked by /add-native for native PDF control workflows. Handles HTTPS-only PDF viewing with @microsoft/power-apps-native-pdf-viewer.
| name | add-datasource |
| description | Use when the user wants to add a data source to a mobile app but hasn't said which kind (Dataverse table, SharePoint list, or other connector). |
| user-invocable | true |
| allowed-tools | Read, Grep, Glob, AskUserQuestion, Skill |
| model | sonnet |
📋 Shared instructions: shared-instructions.md — read first.
Router skill that understands the user's goal and connects them to the right data source — without requiring them to know Power Platform terminology.
Check for memory-bank.md per shared-instructions.md.
$ARGUMENTS is provided or the caller already specified what's needed, use it directly and skip the question below.| 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 |
| Invoke an existing Dataverse action/function/API | Discover with Power Apps CLI find-dataverse-api; this plugin only adds Dataverse table CRUD | /add-connector |
| Read lists, manage documents, integrate with SharePoint sites | SharePoint Online — dedicated skill with list creation support | /add-sharepoint |
| Invoke an existing Power Automate cloud flow | Use Power Apps CLI list-flows / add-flow support through the generic connector workflow | /add-connector |
| Anything else — Teams messages, Excel data, OneDrive files, Office 365 email/calendar, Azure DevOps, Copilot Studio, custom connectors | Generic connector (we'll figure out the right one) | /add-connector |
Note: Dedicated skills for Teams, Excel, OneDrive, Office 365, and Azure DevOps are planned for v1. Until then, /add-connector handles all of them — it covers every connector the platform supports and generates the same src/generated/ service layer.
Important routing rules:
/add-connector with the connector name as the argument (e.g., /add-connector office365, /add-connector teams)./add-connector and tell it to use npx power-apps list-flows --json followed by npx power-apps add-flow --flow-id <flow-guid> --non-interactive from the app root./add-connector and tell it to use npx power-apps find-dataverse-api --search '<operation-name>' --json; then stop and explain that this plugin only adds Dataverse table CRUD./add-dataverse.If the user describes a vague goal (e.g., "I need data for my app"), guide them: