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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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

The content is highly actionable with a clear, validated workflow, but it is verbose due to cross-phase restatement and lacks a clean one-level-deep reference structure — referenced reference files are missing from the bundle.

Suggestions

Extract the AI-only-read-mode contract (currently restated in Phases 1.6, 2.1, 3.2, 4.1, 6.1, 6.2, 6.3, 6.4, 6.5, 7.3, 7.4) into a single reference file and link to it once, reducing significant redundancy.

Add the missing referenced files (references/framework-conventions.md, references/skill-tracking-reference.md) to the bundle so the one-level-deep references are real, or remove the dangling references.

Move the detailed create-table-permission.js / create-site-setting.js CLI reference in 6.4 into a dedicated reference and keep SKILL.md as an overview pointing to it.

Dimension	Reasoning	Score
Conciseness	Sections individually assume Claude's competence and avoid teaching basics, but the ~660-line body restates the AI-only-read-mode contract across nearly every phase and repeats workflow content in Core Principles, Important Notes, and the progress-tracking table — material that could be tightened.	2 / 3
Actionability	Provides copy-paste-ready commands (create-table-permission.js with full flag sets, npm run build), exact file paths, and concrete agent prompt templates — fully executable guidance.	3 / 3
Workflow Clarity	A clear 7-phase sequence with explicit validation checkpoints (Phase 5 file inventory and build verification, 'fix issues before proceeding'), first-table-then-parallel gating, and approval gates for destructive/deploy steps.	3 / 3
Progressive Disclosure	Well-sectioned by phase, but it is a largely monolithic wall of text with detail that should be split (the repeated AI-only contract, the 6.4 CLI reference) inline, and referenced paths like references/framework-conventions.md and skill-tracking-reference.md are absent from the bundle.	2 / 3
	Total	10 / 12 Passed

Description

100%

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

The description is specific, uses natural trigger terms, answers both what and when explicitly, and occupies a clear niche. Third-person voice is used correctly throughout.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'code integration, table permissions setup, and deployment for Dataverse CRUD operations' — matching the score-3 anchor for specific concrete actions.	3 / 3
Completeness	Explicitly states both what it does ('Orchestrates the full integration lifecycle') and when to use it with a 'Use when...' clause, satisfying the score-3 anchor.	3 / 3
Trigger Term Quality	Natural trigger phrasing ('add Web API calls', 'connect to Dataverse', 'add data fetching to their frontend') covers terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	Narrowed to 'Power Pages Web API', 'Dataverse', and 'site frontend', a clear niche unlikely to trigger for unrelated skills.	3 / 3
	Total	12 / 12 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
Commit: 55fa377

Reviewed: 5 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.