integrate-webapi

Integrates Power Pages Web API into a site's frontend code with proper permissions and deployment. Orchestrates the full integration lifecycle: code integration, table permissions setup, and deployment for Dataverse CRUD operations. Use when the user wants to add Web API calls, connect to Dataverse, or add data fetching to their frontend.

Quality

86%

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 thorough, highly actionable orchestration skill with excellent workflow structure and validation checkpoints. Its main weakness is verbosity from repeating the AI-only read mode contract and core principles across many phases instead of centralizing them.

Suggestions

Centralize the AI-only read mode rules in Phase 1.6 and have later phases reference it by flag rather than restating the contract at 10+ points; this would meaningfully cut token cost.

Move the full create-table-permission.js / create-site-setting.js flag signatures and the webapi-field-allowlist column rules into their referenced files, keeping SKILL.md to a concise overview plus a single canonical example per script.

Drop the 'Important Notes' section or reduce it to a pointer, since Core Principles, Key Decision Points, and Progress Tracking largely restate content already in the phase bodies.

Dimension	Reasoning	Score
Conciseness	The body is mostly operational and avoids explaining concepts Claude already knows, but the AI-only read mode contract is restated across ~10 phases (1.6, 4.1, 4.4, 6.1, 6.2, 6.3, 6.4.2, 6.4.3, 6.5, 7.3, 7.4) and the 'Important Notes' section repeats the Core Principles, so it could be tightened by centralizing those rules.	3 / 5
Actionability	Provides fully executable, copy-paste-ready guidance: concrete agent prompt templates, specific glob patterns, and complete CLI invocations for create-web-role.js, create-table-permission.js, and create-site-setting.js with every flag enumerated.	5 / 5
Workflow Clarity	A clear 7-phase sequence with explicit AskUserQuestion gates, a Phase 5 build-verify feedback loop ('if the build fails, fix the issues before proceeding'), and a full task-list checklist driving deterministic progress tracking.	5 / 5
Progressive Disclosure	References are clearly signaled one level deep (framework-conventions.md, webapi-field-allowlist.md, skill-tracking-reference.md, agents/.md, scripts/.js), but the body inlines substantial content that has a dedicated reference — the full create-table-permission.js flag reference and the webapi-field-allowlist rules — creating minor organization gaps.	4 / 5
	Total	17 / 20 Passed

Description

92%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, third-person description that clearly states what the skill does and when to use it with concrete trigger phrases. Minor gap: no synonyms or extension-style variants in the trigger terms.

Dimension	Reasoning	Score
Specificity	Names the domain and multiple concrete actions across the lifecycle — 'code integration, table permissions setup, and deployment for Dataverse CRUD operations' plus 'add Web API calls, connect to Dataverse, or add data fetching' — comprehensive coverage rather than just 1-2 actions.	5 / 5
Completeness	Explicitly answers both 'what' (orchestrates the full integration lifecycle) and 'when' with a concrete 'Use when the user wants to add Web API calls, connect to Dataverse, or add data fetching to their frontend' clause.	5 / 5
Trigger Term Quality	Trigger terms 'add Web API calls', 'connect to Dataverse', and 'add data fetching to their frontend' are natural user phrasings with good coverage, but lack common synonyms or file/extension variants, falling just short of comprehensive.	4 / 5
Distinctiveness Conflict Risk	The 'Power Pages Web API' and 'Dataverse CRUD operations' niche is specific with distinct triggers, making conflict with other skills minimal.	5 / 5
	Total	19 / 20 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (672 lines); consider splitting into references/ and linking	Warning
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	13 / 16 Passed

Repository: microsoft/power-platform-skills
Path: plugins/power-pages/skills/integrate-webapi/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.