add-data-source

Guide the user to add a data source, connection, or API connector to a Canvas App via Power Apps Studio, then verify and continue. USE WHEN the user asks to add a data source, add a connection, add an API, add a connector, connect to SharePoint / Dataverse / SQL / Excel / OneDrive / Teams / Office 365, or any similar request to make new data available to the app. DO NOT USE WHEN the user is asking to list or describe existing data sources — call list_data_sources or list_apis directly instead.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable workflow with explicit verification and a retry feedback loop, appropriate for an instruction-only skill. Minor conciseness padding in the intro and a slight overshoot of the simple-skill line count keep it just short of top marks.

Suggestions

Trim the opening paragraph — its restatement of the phased flow (inform → guide → verify → continue) duplicates the phase headers that follow.

Consolidate the repeated 'wait for confirmation' phrasing (Phase 2 and the Not-found branch both restate the AskUserQuestion pause) to tighten conciseness.

If the skill is meant to stay single-file, consider compressing Phase 1's numbered UI steps so the body stays near the under-50-line simple-skill threshold.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete tool calls and UI steps, but the opening paragraph and some repeated confirmation phrasing (e.g. 'Do not proceed until the user confirms') lightly restate what the phased workflow already encodes.	4 / 5
Actionability	Concrete guidance throughout — specific MCP tools (list_data_sources, list_apis, get_data_source_schema, describe_api), explicit UI steps, and branched Found/Not-found handling — with only minor gaps in copy-paste-ready specificity.	4 / 5
Workflow Clarity	Phases 0–4 are clearly sequenced with an explicit verification checkpoint (Phase 3) and a feedback loop (Not found → AskUserQuestion → re-run Phase 3) for error recovery.	5 / 5
Progressive Disclosure	Well-organized into clearly labeled phases and self-contained with no external references; at ~60 lines it slightly exceeds the under-50-line threshold that would let a self-contained skill score 5 on structure alone.	4 / 5
	Total	17 / 20 Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-structured description that clearly states what the skill does, when to use it, and when not to use it, with rich natural trigger terms and product synonyms. The only minor gap is action breadth, where the core action ('add') dominates despite several variants.

Dimension	Reasoning	Score
Specificity	Names the domain (Canvas App via Power Apps Studio) and several concrete actions — 'add a data source, connection, or API connector', 'verify and continue' — with minor gaps; not quite the breadth of distinct actions that defines a 5.	4 / 5
Completeness	Explicitly answers both 'what' (guide user to add via Studio, verify, continue) and 'when' (USE WHEN clause with concrete triggers), plus a DO NOT USE WHEN boundary directing to other tools.	5 / 5
Trigger Term Quality	Comprehensive natural trigger terms including synonyms ('add a data source, add a connection, add an API, add a connector') and concrete product names (SharePoint / Dataverse / SQL / Excel / OneDrive / Teams / Office 365).	5 / 5
Distinctiveness Conflict Risk	Clear niche (adding data sources to Canvas Apps via Power Apps Studio) with explicit negative boundary guidance pointing list/describe requests to list_data_sources/list_apis, minimizing conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: microsoft/power-platform-skills
Path: plugins/canvas-apps/skills/add-data-source/SKILL.md
Commit: 4c284ab

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.