📋 Shared Instructions: 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.
Understand the Goal
- If
$ARGUMENTS is provided or the caller already specified what's needed, use it directly and skip the question below.
- 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)"
- 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).
- 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:
- Ask what their app does and who uses it
- Ask what data they need to display or interact with
- Recommend the simplest approach that meets their needs
- Explain the recommendation in plain language (avoid jargon like "connector", "Dataverse", "tabular data source" unless the user uses those terms first)
1---2name: add-datasource3description: 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.4---5
6**📋 Shared Instructions: [shared-instructions.md](${CLAUDE_PLUGIN_ROOT}/shared/shared-instructions.md)** - Cross-cutting concerns.
7
8# Add Data Source
9
10Router skill that understands the user's goal and connects them to the right data source -- without requiring them to know Power Platform terminology.
11
12## Workflow
13
14### Check Memory Bank
15
16Check for `memory-bank.md` per [shared-instructions.md](${CLAUDE_PLUGIN_ROOT}/shared/shared-instructions.md).
17
18### Understand the Goal
19
201. **If `$ARGUMENTS` is provided or the caller already specified what's needed**, use it directly and skip the question below.
212. Otherwise, ask the user **what they want their app to do** -- not which connector to use. Focus on the end goal. Example questions:
22 - "What kind of data does your app need to work with?"
23 - "What should your app be able to do? (e.g., search company info, manage tasks, send messages)"
243. 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.
25
26### Route to the Right Skill
27
28Map the user's goal to the appropriate skill:
29
30| User's goal | Best approach | Invoke |
31|-------------|---------------|--------|
32| Store and manage structured business data (custom tables, forms, CRUD) | Dataverse is the platform's native database | `/add-dataverse` |
33| Track work items, bugs, builds, or pipelines | Azure DevOps connector | `/add-azuredevops` |
34| Send or read Teams messages, post to channels | Teams connector | `/add-teams` |
35| Read/write Excel spreadsheet data | Excel Online (Business) connector | `/add-excel` |
36| Upload, download, or manage files | OneDrive for Business connector | `/add-onedrive` |
37| Work with SharePoint lists or document libraries | SharePoint Online connector | `/add-sharepoint` |
38| Send emails, read inbox, manage calendar events | Office 365 Outlook connector | `/add-office365` |
39| Invoke an AI agent or copilot built in Copilot Studio | Copilot Studio connector | `/add-mcscopilot` |
40| Something else or not sure | Generic connector (we'll figure it out) | `/add-connector` |
41
42**Important routing rules:**
43- 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).
44
454. If the user wants multiple capabilities, invoke each skill in sequence.
46
47### When the User Isn't Sure
48
49If the user describes a vague goal (e.g., "I need data for my app"), guide them:
50
511. Ask what their app does and who uses it
522. Ask what data they need to display or interact with
533. Recommend the simplest approach that meets their needs
544. Explain the recommendation in plain language (avoid jargon like "connector", "Dataverse", "tabular data source" unless the user uses those terms first)
majiayu000