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.
82
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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.
This is a strong skill description that clearly defines a specific niche (Power Pages Web API + Dataverse integration), lists concrete actions across the integration lifecycle, and includes an explicit 'Use when' clause with natural trigger terms. It uses proper third-person voice throughout and would be easily distinguishable from other skills in a large skill library.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'code integration, table permissions setup, and deployment for Dataverse CRUD operations.' It clearly names the domain (Power Pages Web API) and describes concrete lifecycle steps. | 3 / 3 |
Completeness | Clearly answers both 'what' (integrates Power Pages Web API with code integration, table permissions, and deployment for Dataverse CRUD) and 'when' (explicit 'Use when' clause with triggers like 'add Web API calls, connect to Dataverse, or add data fetching to their frontend'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'Web API calls', 'connect to Dataverse', 'data fetching', 'frontend', 'CRUD operations', 'Power Pages', 'permissions', 'deployment'. Good coverage of terms a developer working in this ecosystem would use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche targeting Power Pages Web API and Dataverse integration. The combination of Power Pages, Dataverse, table permissions, and Web API creates a very distinct trigger profile unlikely to conflict with generic frontend or API skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill excels at actionability and workflow clarity, providing a comprehensive, well-sequenced orchestration guide with concrete commands, agent prompts, and validation checkpoints at every phase. However, it suffers significantly from verbosity — key principles are repeated multiple times, inline details that could be referenced externally bloat the document, and the overall length (~400+ lines) far exceeds what's needed for an orchestration skill. The content would benefit greatly from extracting detailed subsections into referenced files and eliminating redundant restatements.
Suggestions
Eliminate repeated statements of the same principles (e.g., 'first table sequential, then parallel' and 'case-sensitive column names' each appear 3+ times) — state each once and reference it.
Extract the detailed script invocation syntax in section 6.4 (Create Permission & Settings Files) into a separate reference file, keeping only a brief summary and pointer in the main SKILL.md.
Remove or drastically condense the 'Important Notes' section at the end, as it almost entirely duplicates guidance already provided inline in the workflow phases.
Condense the Progress Tracking table — Claude doesn't need the full task descriptions spelled out when the phases above already describe them in detail.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~400+ lines with significant repetition. The same concepts are restated multiple times (e.g., 'first table sequential, then parallel' appears 3+ times, deployment prerequisite is repeated, column case-sensitivity is mentioned in multiple places). The 'Important Notes' section at the end largely duplicates guidance already given inline. Many sections explain orchestration logic that could be much more concise. | 1 / 3 |
Actionability | The skill provides fully executable bash commands with complete argument syntax for all scripts (create-web-role.js, create-table-permission.js, create-site-setting.js), concrete prompt templates for sub-agents, specific file paths to check, and exact glob patterns. The guidance is copy-paste ready throughout. | 3 / 3 |
Workflow Clarity | The 7-phase workflow is clearly sequenced with explicit validation checkpoints (Phase 5 build verification, file inventory checks after each agent), feedback loops (fix and re-validate on build failure), user confirmation gates at 6 decision points, and clear prerequisite dependencies (deployment before permissions, first table before parallel tables). Destructive/batch operations have appropriate verification steps. | 3 / 3 |
Progressive Disclosure | The skill references external files appropriately (framework-conventions.md, skill-tracking-reference.md, agent files), but the SKILL.md itself is monolithic — the detailed script invocation syntax for Path A (section 6.4) and the extensive permission/settings creation instructions could be split into separate reference files. The inline content is overwhelming for what should be an orchestration overview. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (544 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 | 8 / 11 Passed | |
- Repository
- microsoft/power-platform-skills
- Commit
48e49c4
- Reviewed
Table of Contents
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.