integrate-webapi
This skill should be used when the user asks to "integrate web api", "add web api", "connect to dataverse", "add api integration", "set up web api calls", "integrate api for my tables", "add crud operations", "hook up web api", "add data fetching", "connect frontend to dataverse", or wants to integrate Power Pages Web API into their site's frontend code with proper permissions and deployment. This skill orchestrates the full integration lifecycle: code integration, permissions setup, and deployment.
Install with Tessl CLI
npx tessl i github:microsoft/power-platform-skills --skill integrate-webapi85
Quality
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Discovery
89%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 with excellent trigger term coverage and clear distinctiveness through its Power Pages/Dataverse focus. The main weakness is that the specific capabilities could be more concrete - it mentions 'code integration, permissions setup, and deployment' but doesn't detail what specific actions are performed (e.g., 'generate fetch XML queries', 'configure table permissions').
Suggestions
Add more specific concrete actions to the capability description, such as 'generates Web API fetch calls, configures table permissions in Portal Management, deploys site customizations'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Power Pages Web API integration) and mentions some actions ('code integration, permissions setup, and deployment', 'crud operations', 'data fetching'), but lacks specific concrete actions like 'create API endpoints' or 'configure authentication tokens'. | 2 / 3 |
Completeness | Clearly answers both what ('orchestrates the full integration lifecycle: code integration, permissions setup, and deployment') and when (explicit 'Use when...' equivalent with extensive trigger phrases and scenario description). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'integrate web api', 'add api integration', 'connect to dataverse', 'add crud operations', 'hook up web api', 'add data fetching', 'connect frontend to dataverse' - these are realistic phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific technology focus (Power Pages Web API, Dataverse) and clear niche. Terms like 'connect to dataverse' and 'Power Pages Web API' are unique identifiers unlikely to conflict with generic API skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured orchestration skill with excellent workflow clarity and actionability. The multi-phase approach with explicit checkpoints, user decision points, and sequential processing rationale demonstrates strong design. However, the skill is verbose in places with repeated explanations and could benefit from extracting some detailed reference content to separate files.
Suggestions
Extract the detailed YAML formatting rules (section 5.4) to a separate reference file like `yaml-formatting-reference.md` and link to it
Remove redundant explanations of sequential processing—state it once in Core Principles and reference that section instead of repeating
Consider extracting the permissions parsing logic (Path A in section 5.2) to a separate reference or sub-agent since it's substantial standalone functionality
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy (e.g., repeating 'process tables sequentially' multiple times, explaining prerequisites in multiple places). The workflow phases are well-structured but could be tightened—some explanatory text could be removed since Claude understands orchestration patterns. | 2 / 3 |
Actionability | Provides fully executable PowerShell commands, specific file paths, concrete prompt templates for sub-agents, exact YAML formatting rules, and copy-paste ready code snippets. The agent invocation prompts are detailed and actionable. | 3 / 3 |
Workflow Clarity | Excellent multi-phase workflow with explicit validation checkpoints (Phase 5 verification, build validation), clear sequencing rationale (why tables must be processed sequentially), decision points with user confirmation, and error recovery paths (e.g., deployment prerequisite handling). | 3 / 3 |
Progressive Disclosure | References external files appropriately (framework-conventions.md, skill-tracking-reference.md, sub-agents), but the main skill file is quite long (~400 lines). Some content like the detailed YAML formatting rules or the full permissions parsing logic could potentially be extracted to reference files. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- 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.