SKILLEMALL.ai

BF create-mobile-app

Use when the user wants to start a new Power Apps mobile app (Expo / React Native / TypeScript, targeting iOS and Android) from scratch.

microsoft/power-platform-skills Agent Skills author: microsoft 3 files body ≈ 39 209 tokens Open the sourcegithub.com analyzed 3 h ago

Top-level orchestrator.

As a process F 62/100 · Will not run — References files that are not bundled: ${PLUGIN_ROOT}/shared/shared-instructions.md, ${PLUGIN_ROOT}/shared/version-check.md, ../../shared/references/universal-patterns.md

GeneratorAzureSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
B
81/100
safety, quality, tests
Safety 60%
94
Quality 40%
61
Run on models
none yet
Process rating
F
62/100
Will not run
References files that are not bundled: ${PLUGIN_ROOT}/shared/shared-instructions.md, ${PLUGIN_ROOT}/shared/version-check.md, ../../shared/references/universal-patterns.md
Tools and files w 18
0
Execution cost w 6
10
Result and completion w 14
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 · 2

✓ No critical or high findings

Medium and low: 2
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash
    allowed-tools: Read Write Edit Bash Glob Grep AskUserQuestion Skill Task EnterPlanMode ExitPlanMode
  • low Concealment en-hide-from-user SKILL.md:97
    Instruction to hide actions from the user (negated — the text forbids it)
    **Do not silently copy a bundled template over the user's folder.** A fresh `plugins/mobile-apps/template` template may contain placeholder `power.config.json` with an empty `environmentId`; Step 5 re
    negated

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

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 39209 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: ${PLUGIN_ROOT}/shared/shared-instructions.md
  • warning missing-ref reference to a missing file: ${PLUGIN_ROOT}/shared/version-check.md
  • warning missing-ref reference to a missing file: ../../shared/references/universal-patterns.md
  • warning missing-ref reference to a missing file: ${PLUGIN_ROOT}/skills/create-mobile-app/references/requirements-discovery.md
  • warning missing-ref reference to a missing file: ${PLUGIN_ROOT}/shared/references/connectivity-intent-ownership.md
  • warning missing-ref reference to a missing file: ${PLUGIN_ROOT}/agents/native-app-planner.md
  • warning missing-ref reference to a missing file: ${PLUGIN_ROOT}/AGENTS.md
  • warning missing-ref reference to a missing file: ${PLUGIN_ROOT}/shared/references/javascript-dependency-planning.md
  • warning missing-ref reference to a missing file: ${PLUGIN_ROOT}/shared/references/design-planning.md
  • warning missing-ref reference to a missing file: ../design-system/references/tamagui-integration.md
  • warning missing-ref reference to a missing file: ${PLUGIN_ROOT}/shared/references/screen-templates.md
  • warning missing-ref reference to a missing file: scripts/resolve-environment.js
  • note edit-residue the text marks something as outdated (lines 714, 945, 950, 957, 1018, 1066): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 62/100

Will not run. References files that are not bundled: ${PLUGIN_ROOT}/shared/shared-instructions.md, ${PLUGIN_ROOT}/shared/version-check.md, ../../shared/references/universal-patterns.md
  • 0Tools and files. 12 referenced file(s) missing: ${PLUGIN_ROOT}/shared/shared-instructions.md, ${PLUGIN_ROOT}/shared/version-check.md, ../../shared/references/universal-patterns.md
  • 10Execution cost. Instruction body is 39209 tokens: crowds the task out of the window
  • 40Result and completion. Does not say what the result is
  • 60Steps. 175 steps, 4 vague phrases
  • 100When it triggers. States when to use and when not to
  • 100Inputs and preconditions. Inputs and preconditions are listed
  • 100Failures and branches. 38 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 (142 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

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • -5TODO / placeholder text left in the skill
  • +1No license
  • +2Single-language instructions
  • +3Description length 136: enough signal without eating the budget
  • +4Structure: 67 headings
  • +3Step-by-step instructions: 175 items
  • +4Has examples (67 code blocks)
  • +4Reference files are cited in the instructions (2 of 2)

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