DC debug-app
Diagnose Power Apps mobile install/startup failures, npm run dev errors, missing package entry points, or QR/device-opening problems even before an app is loaded. Inspect locally first; restore locked dependencies or restart Metro only with explicit approval, never upgrade packages or patch host/MSAL source. For a running native app, monitor sanitized project-local Metro logs and diagnose runtime errors or silent failures such as empty lists and blank screens. Supports startup-only diagnosis, symptoms, port/platform filters, bounded monitoring, and non-mutating --no-fix mode. Verify the original symptom, not merely installation or quiet logs.
Diagnose Power Apps mobile install/startup failures, npm run dev errors, missing package entry points, or QR/device-opening problems even before an app is…
As a process C 51/100 · Has gaps — References files that are not bundled: ${PLUGIN_ROOT}/shared/shared-instructions.md, ${PLUGIN_ROOT}/skills/add-dataverse/references/dataverse-reference.md, ../add-dataverse/references/dataverse-reference.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
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 Edit Write Grep Glob Bash AskUserQuestion WebFetch mcp__plugin_mobile-app_microsoft-learn__microsoft_docs_search
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 23414 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: ${PLUGIN_ROOT}/shared/shared-instructions.md - warning
missing-refreference to a missing file: ${PLUGIN_ROOT}/skills/add-dataverse/references/dataverse-reference.md - warning
missing-refreference to a missing file: ../add-dataverse/references/dataverse-reference.md - warning
missing-refreference to a missing file: ${PLUGIN_ROOT}/shared/references/javascript-dependency-planning.md - note
edit-residuethe text marks something as outdated (lines 226, 239, 457, 628, 629): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 51/100
- 0Tools and files. 4 referenced file(s) missing: ${PLUGIN_ROOT}/shared/shared-instructions.md, ${PLUGIN_ROOT}/skills/add-dataverse/references/dataverse-reference.md, ../add-dataverse/references/dataverse-reference.md
- 0Result and completion. Does not say what the result is
- 10Execution cost. Instruction body is 23414 tokens: crowds the task out of the window
- 50When it triggers. No condition that starts the skill
- 60Steps. 206 steps, 4 vague phrases
- 100Inputs and preconditions. Inputs and preconditions are listed
- 100Failures and branches. 11 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 10 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (49 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
- -4Absolute local paths (C:\Users, /home/…): not portable
- +1No license
- +2Single-language instructions
- +3Description length 650: enough signal without eating the budget
- +4Structure: 39 headings
- +3Step-by-step instructions: 206 items
- +4Has examples (37 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 45.