BF export-solution
Exports a Dataverse solution containing Power Pages site components as a zip file, ready for deployment to another environment. Use when asked to: "export solution", "download solution", "export managed", "export unmanaged", "package for deployment", "create solution zip", "export site package", or "build deployment artifact".
Exports a Dataverse solution containing Power Pages site components as a zip file, ready for deployment to another environment.
As a process F 52/100 · Will not run — References files that are not bundled: scripts/lib/export-solution-async.js, scripts/lib/download-export-data.js, scripts/lib/alm-paths.js
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 Bash Glob Grep TaskCreate TaskUpdate TaskList AskUserQuestion mcp__plugin_power-pages_microsoft-learn__microsoft_docs_search mcp__plugin_power-pages_microsoft-learn__mic
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 6721 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: scripts/lib/export-solution-async.js - warning
missing-refreference to a missing file: scripts/lib/download-export-data.js - warning
missing-refreference to a missing file: scripts/lib/alm-paths.js
Process rating: all ten parameters 52/100
- 0Tools and files. 3 referenced file(s) missing: scripts/lib/export-solution-async.js, scripts/lib/download-export-data.js, scripts/lib/alm-paths.js
- 0Result and completion. Does not say what the result is
- 50Failures and branches. 0 branches, has a failure section
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 6721 tokens
- 85Steps. 56 steps, 2 vague phrases
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
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
- -31 of 1 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +5Description quotes 8 example trigger phrases
- +3Description length 328: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 56 items
- +4Has examples (12 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.