genpage
Creates, updates, and deploys Power Apps generative pages for model-driven apps using React v17, TypeScript, and Fluent UI V9. Orchestrates specialist agents for planning, entity creation, and code generation. 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".
73
92%
Does it follow best practices?
Impact
—
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 a narrow, specific domain (Power Apps generative pages) with concrete actions, explicit trigger guidance, and distinctive terminology. It covers the tech stack, the orchestration approach, and provides multiple natural trigger terms including the shorthand 'genux'. The description is well-structured and concise without unnecessary padding.
| 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), and mentions orchestrating specialist agents for planning, entity creation, and code generation. | 3 / 3 |
Completeness | Clearly answers both 'what' (creates, updates, deploys generative pages using specific tech stack, orchestrates specialist agents) and 'when' (explicit 'Use it when...' clauses with specific trigger phrases like 'generative page', 'genux', 'page in a model-driven'). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would 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 niche targeting specifically Power Apps model-driven app generative pages with unique trigger terms like 'genux' and 'generative page'. Very unlikely to conflict with other skills due to the specificity of the domain. | 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 for a complex multi-agent orchestration workflow. Its greatest strengths are the precise, executable commands with exact flag names, clear conditional branching, and thoughtful progressive disclosure that defers detailed sub-workflows to separate files. The main weakness is moderate verbosity in explanatory sections (particularly the Phase 1 critical block) that could be condensed without losing clarity.
Suggestions
Condense the Phase 1 CRITICAL block — the five bullet points explaining why not to ask 'new or edit?' yourself could be reduced to 2-3 sentences since the instruction itself ('MUST invoke genpage-planner via Task tool') is already clear.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly long (~300+ lines) and includes some redundant explanations (e.g., the lengthy CRITICAL block in Phase 1 explaining why not to ask 'new or edit?' yourself with multiple bullet points). However, most content is genuinely instructive and specific to a complex multi-phase workflow that Claude wouldn't inherently know. The verbosity is partially justified by the complexity but could be tightened in several places. | 2 / 3 |
Actionability | The skill provides fully executable commands (pac CLI, node scripts), exact flag names, specific JSON response schemas, concrete prompt templates for subagent invocation, and precise conditional logic. Every phase has copy-paste-ready commands with explicit parameter placeholders and clear decision trees. | 3 / 3 |
Workflow Clarity | The 8-phase workflow is clearly sequenced with explicit validation checkpoints (Phase 2a pre-flight auth check with JSON response handling, Phase 5a plan validation before dispatch, Phase 6.5 placeholder resolution with error-on-mismatch). Conditional branching is well-defined (skip entity creation, single vs multi-page fast path, edit flow redirect). Feedback loops exist for auth failures and placeholder mismatches. | 3 / 3 |
Progressive Disclosure | The skill serves as a clear orchestration overview, with well-signaled one-level-deep references to rules.md, troubleshooting.md, samples/, edit-flow.md, verify-flow.md, plan-schema.md, data-caching.md, and localization.md. The verify flow is explicitly loaded on-demand to keep context lean. Content is appropriately split between the main skill and referenced files. | 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
3b2009f
- 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.