SKILLEMALL.ai

BF 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". This skill stands alone and does not require /app-builder — but if the user wants a whole app built (tables, forms, views, sitemap) rather than pages for an app that already exists, use /app-builder instead.

microsoft/power-platform-skills Claude Code author: microsoft 3 files body ≈ 12 107 tokens Open the sourcegithub.com analyzed 2 h ago

Creates, updates, and deploys Power Apps generative pages for model-driven apps using React v17, TypeScript, and Fluent UI V9.

As a process F 55/100 · Will not run — References files that are not bundled: ../../references/rules.md, ../../references/troubleshooting.md, ../../samples/

GeneratorInfrastructureSoftware developmentWriting and documentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
84/100
safety, quality, tests
Safety 60%
95
Quality 40%
67
Run on models
none yet
Process rating
F
55/100
Will not run
References files that are not bundled: ../../references/rules.md, ../../references/troubleshooting.md, ../../samples/
Tools and files w 18
0
Result and completion w 14
0
Execution cost w 6
40
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Broad scope medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

How to improve

  1. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
  2. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 1

✓ No critical or high findings

Medium and low: 1
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash
    allowed-tools: Read Write Edit Bash Glob Grep WebFetch Task AskUserQuestion EnterPlanMode ExitPlanMode TaskCreate TaskUpdate TaskList read edit execute search web agent todo

Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 12107 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: ../../references/rules.md
  • warning missing-ref reference to a missing file: ../../references/troubleshooting.md
  • warning missing-ref reference to a missing file: ../../samples/
  • warning missing-ref reference to a missing file: references/supported-dependencies.md
  • warning missing-ref reference to a missing file: scripts/lib/supported-dependencies.js

Process rating: all ten parameters 55/100

Will not run. References files that are not bundled: ../../references/rules.md, ../../references/troubleshooting.md, ../../samples/
  • 0Tools and files. 5 referenced file(s) missing: ../../references/rules.md, ../../references/troubleshooting.md, ../../samples/
  • 0Result and completion. Does not say what the result is
  • 40Execution cost. Instruction body is 12107 tokens: crowds the task out of the window
  • 60Steps. 94 steps, 4 vague phrases
  • 70When it triggers. States when to use, but not when not to
  • 100Inputs and preconditions. Inputs and preconditions are listed
  • 100Failures and branches. 9 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low The response is described with custom markup (40 tags): a typed call is more reliable

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 2 example trigger phrases
  • +3Description length 613: enough signal without eating the budget
  • +4Structure: 35 headings
  • +3Step-by-step instructions: 94 items
  • +4Has examples (18 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.