BF edit-app
Use when the user wants to iterate on an existing generated Power Apps mobile app after /create-mobile-app: update Application Insights configuration, the plan, data model, native capabilities, design, screens, generated app code, and preview without restarting the full project flow.
Use when the user wants to iterate on an existing generated Power Apps mobile app after /create-mobile-app: update Application Insights configuration, the…
As a process F 56/100 · Will not run — References files that are not bundled: ../../shared/shared-instructions.md, ${PLUGIN_ROOT}/shared/references/javascript-dependency-planning.md, ${PLUGIN_ROOT}/shared/references/offline-profile-reconciliation.md
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
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.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
- 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-toolsSKILL.md:1Broad tool permissions pre-approved: Bashallowed-tools: Read Write Edit Glob Grep Bash AskUserQuestion Task Skill
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 11746 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: ../../shared/shared-instructions.md - warning
missing-refreference to a missing file: ${PLUGIN_ROOT}/shared/references/javascript-dependency-planning.md - warning
missing-refreference to a missing file: ${PLUGIN_ROOT}/shared/references/offline-profile-reconciliation.md - warning
missing-refreference to a missing file: scripts/check-routes.js
Process rating: all ten parameters 56/100
- 0Tools and files. 4 referenced file(s) missing: ../../shared/shared-instructions.md, ${PLUGIN_ROOT}/shared/references/javascript-dependency-planning.md, ${PLUGIN_ROOT}/shared/references/offline-profile-reconciliation.md
- 0Result and completion. Does not say what the result is
- 30Running it twice. 59 mutating operations with no state check
- 40Execution cost. Instruction body is 11746 tokens: crowds the task out of the window
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 112 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 16 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- high The skill tells the model to perform an irreversible action with no human approval
- low The response is described with custom markup (6 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
- +1No license
- +2Single-language instructions
- +3Description length 284: enough signal without eating the budget
- +4Structure: 21 headings
- +3Step-by-step instructions: 112 items
- +4Has examples (16 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.