$ ~/registry/skill/microsoft-plugins-code-apps-skills-add-datasource

SKILL

add-datasource

Name: add-datasource
Author: microsoft

Add a data source or connector to a Power Apps code app.

Stars

★ 440

Source

GitHub

Updated

2026-07-11

// securityCaution

Prompt only, no code
Open source

Summary

The material indicates this is an open-source, prompt-only routing skill with no required secrets, no declared remote endpoints, and no described local code execution. Overall risk is low; the main caveat is that it may route users to other skills, so practical risk depends more on the downstream skills it invokes.

CredentialsLow risk

The material explicitly states that no keys or environment variables are required. The skill itself does not request API keys, tokens, or other sensitive credentials, so direct credential exposure or misuse risk appears low.

Network egressLow risk

The material lists no remote endpoint hosts, and the README does not describe sending data to external services. For this skill itself, there is no evident data egress. It may route users to other connector skills, but that is not itself a data-egress red flag for this skill.

Code executionLow risk

The system has classified it as prompt-only. The README only describes asking about user intent and routing to other skills, with no indication of spawning local processes, running scripts, or invoking system commands.

Data accessCaution

The README mentions checking `memory-bank.md`, indicating the skill may read skill context or a local memory file. While this is a common form of contextual access for prompt-based skills and there is no sign of broad filesystem access or over-privileged behavior, it is still worth ensuring the memory bank does not contain unnecessary sensitive information.

Supply chainCaution

The source is a Microsoft GitHub open-source repository, which is a clear risk-reducing factor because the code is auditable. However, the license is not declared, community adoption is 0 stars, and maintenance status is unknown, so there is still some supply-chain uncertainty.

Recommendations

Review the downstream skills it may invoke, especially those involving connectors, external services, or data writes.
Ensure that `memory-bank.md` or related shared context does not contain unnecessary sensitive information.
Prefer pinning to a specific version or commit from the official repository, and monitor future maintenance and license details.
If used in production, validate its routing behavior first under least-privilege settings and with test data.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "add-datasource" skill from askskill:
1. Download https://raw.githubusercontent.com/microsoft/power-platform-skills/main/plugins/code-apps/skills/add-datasource/SKILL.md
2. Save it as ~/.claude/skills/add-datasource/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// examples

Connect SharePoint data

Prompt

I want to add SharePoint as a data source in a Power Apps code app to read a project task list. First ask for the site, list name, and authentication method, then guide me through the connection.

Expected

It identifies the right connector flow and provides the required details and steps to add a SharePoint data source.

Add a SQL database connection

Prompt

Help me connect a SQL Server database to my Power Apps code app. I want to query a customer table, so tell me what connection details I need and guide me to the correct connector.

Expected

It recommends the proper connector for the target source and lists the database connection settings and integration steps.

Decide which connector to use

Prompt

I want my Power Apps code app to access data from an external business system, but I’m not sure whether to use a standard connector, a custom connector, or another approach. Ask about my goal first, then help me choose.

Expected

It asks about the use case and system type, then routes you to the most suitable data access approach.

// docs

📋 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)

Add a Copilot Studio connector to Power Apps code apps for agent integration.

microsoftGet→

$ loading_