SKILLEMALL.ai

BF app-builder

Builds and edits a model-driven Power Apps app from a natural-language intent — tables, columns, relationships, adaptive forms with sub-grids, views, Choice-column charts, business rules, business process flows, generative page intents for overview/dashboard surfaces (page `.tsx` generated in generate-pages after plan approval), and an app module + sitemap — via the headless cds-maker-sdk. Runs an interactive, multi-turn authoring flow (env selection, jobs-to-be-done first, then design-only App Spec authoring across confirmed levels, guardrail lint, plan-mode approval, generate-pages, full build) and a narrated build, and can download a deployed app back into an editable spec to change it. Use when the user says "build an app for X", "create a model-driven app", "make me an app to manage Y", "add a business process flow", or "edit/add to my app". This skill stands alone and does not require /genpage — but for a standalone generative page added to an app that already exists, use /genpage instead.

microsoft/power-platform-skills Claude Code author: microsoft 1 file body ≈ 11 758 tokens Open the sourcegithub.com analyzed 2 h ago

Builds and edits a model-driven Power Apps app from a natural-language intent — tables, columns, relationships, adaptive forms with sub-grids, views…

As a process F 61/100 · Will not run — References files that are not bundled: ../../references/authoring-flow.md, ../../references/app-spec-schema.md, ../../samples/app-spec.support-desk.json

GeneratorInfrastructureData and analyticsWriting and documentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
83/100
safety, quality, tests
Safety 60%
95
Quality 40%
64
Run on models
none yet
Process rating
F
61/100
Will not run
References files that are not bundled: ../../references/authoring-flow.md, ../../references/app-spec-schema.md, ../../samples/app-spec.support-desk.json
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 Task AskUserQuestion EnterPlanMode ExitPlanMode TaskCreate TaskUpdate TaskList read edit execute search agent todo

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

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 11758 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: ../../references/authoring-flow.md
  • warning missing-ref reference to a missing file: ../../references/app-spec-schema.md
  • warning missing-ref reference to a missing file: ../../samples/app-spec.support-desk.json
  • warning missing-ref reference to a missing file: ../../references/app-spec-schema-advanced.md
  • warning missing-ref reference to a missing file: ../../docs/app-builder-capabilities.md
  • warning missing-ref reference to a missing file: references/authoring-flow.md
  • warning missing-ref reference to a missing file: references/app-spec-schema-advanced.md
  • warning missing-ref reference to a missing file: references/app-spec-schema.md
  • warning missing-ref reference to a missing file: scripts/build-model-app.js
  • warning missing-ref reference to a missing file: scripts/vendor/
  • note edit-residue the text marks something as outdated (lines 262, 362): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 61/100

Will not run. References files that are not bundled: ../../references/authoring-flow.md, ../../references/app-spec-schema.md, ../../samples/app-spec.support-desk.json
  • 0Tools and files. 10 referenced file(s) missing: ../../references/authoring-flow.md, ../../references/app-spec-schema.md, ../../samples/app-spec.support-desk.json
  • 0Result and completion. Does not say what the result is
  • 40Execution cost. Instruction body is 11758 tokens: crowds the task out of the window
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 36 steps
  • 100When it triggers. States when to use and when not to
  • 100Failures and branches. 1 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 (11 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)
  • +3Description length 1010: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 5 example trigger phrases
  • +4Structure: 10 headings
  • +3Step-by-step instructions: 36 items
  • +4Has examples (13 code blocks)

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