genpage
Creates, updates, and deploys Power Apps generative pages for model-driven apps using React v17, TypeScript, and Fluent UI V9. Completes workflow from requirements to deployment. Uses PAC CLI to deploy the page code. Use it when user asks to build, retrieve, or update a page in an existing Microsoft Power Apps model-driven app. Use it when user mentions "generative page", "page in a model-driven", or "genux".
92
92%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
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 an excellent skill description that clearly defines its scope, lists concrete actions and technologies, and provides explicit trigger guidance with natural user terms. It covers a well-defined niche (Power Apps generative pages) with minimal risk of conflicting with other skills. The description is concise yet comprehensive, following best practices for skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: creates, updates, deploys Power Apps generative pages, specifies the tech stack (React v17, TypeScript, Fluent UI V9), mentions PAC CLI for deployment, and describes the full workflow from requirements to deployment. | 3 / 3 |
Completeness | Clearly answers both 'what' (creates, updates, deploys Power Apps generative pages using specific technologies) and 'when' (explicit 'Use it when...' clauses with specific trigger phrases like 'generative page', 'page in a model-driven', 'genux'). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would actually say: 'generative page', 'page in a model-driven', 'genux', 'Power Apps', 'model-driven app', 'build', 'retrieve', 'update'. Good coverage of both formal and shorthand terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Power Apps model-driven generative pages with specific technology stack. The trigger terms 'genux', 'generative page', and 'model-driven app' are very specific and unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%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, highly actionable skill that guides Claude through a complex multi-step workflow (from prerequisites to deployment and verification) with clear sequencing and validation checkpoints. Its main weakness is length — the inline DataAPI reference, component template, and extensive Playwright verification steps could potentially be offloaded to reference files to reduce token consumption. Overall, it's a strong skill that balances comprehensiveness with practical guidance.
Suggestions
Move the DataAPI Quick Reference and Component Template sections to the genpage-rules-reference.md file to reduce the main skill's token footprint, keeping only a brief pointer in Step 7.
Consider moving the detailed Playwright verification tables (Steps 9.2-9.5) to a separate verification-guide.md reference file, keeping only a summary in the main workflow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite long (~300+ lines) and includes some content that could be offloaded to references (e.g., the full DataAPI Quick Reference section, the component template, and the extensive Playwright verification steps). However, most content is genuinely instructional and specific to this workflow rather than explaining concepts Claude already knows. | 2 / 3 |
Actionability | Excellent actionability throughout — every step includes exact CLI commands with real flags, executable TypeScript code templates, specific PowerShell commands for deployment, and concrete examples of user prompts. The DataAPI quick reference provides copy-paste-ready code patterns. | 3 / 3 |
Workflow Clarity | The 10-step workflow is clearly sequenced with explicit validation checkpoints: prerequisite verification before proceeding, schema generation before code writing (marked CRITICAL), user confirmation before deployment, app selection confirmation before upload, and a fix-and-redeploy feedback loop in Step 9.5. Destructive operations (deployment) require explicit user consent. | 3 / 3 |
Progressive Disclosure | The skill has a clear References section at the top pointing to genpage-rules-reference.md, troubleshooting.md, and samples/ — all one level deep. The main SKILL.md serves as the workflow orchestrator while detailed code generation rules and troubleshooting are properly externalized. The samples table in Step 6 provides well-organized navigation to specific use cases. | 3 / 3 |
Total | 11 / 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 | |
- Repository
- microsoft/power-platform-skills
- Commit
1132a35
- 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.