CD edit-site
Plans, coordinates and customizes PAC CLI-downloaded Standard or Enhanced data model non-SPA Power Pages sites created from Microsoft templates or manually in Design Studio. Use for requests involving pages, localized content, navigation, assets, snippets, site markers, Liquid/web templates, page layouts, or styling. Coordinated work produces an approved browser-viewable plan, executes changes in dependency order, verifies the local result, and optionally hands off to deployment. Not for React, Angular, Vue, or Astro SPA sites.
Promises to manage Power Pages sites via PAC CLI: planning, coordinating changes to pages, content, navigation, templates, and styling. The archive contains 22 files, but has a catch—broken references and missing files. Checks show: quality 71%, process 45%, safety 94%. No critical errors, but 2 medium-low findings flagged. Model never ran, sandbox untested.
For Power Pages work, this could work if you already know PAC CLI and accept that the instructions need patching. Install only if you're definitely working with non-SPA sites from Microsoft templates and willing to debug missing links yourself.
Plans, coordinates and customizes PAC CLI-downloaded Standard or Enhanced data model non-SPA Power Pages sites created from Microsoft templates or manually in…
As a process D 45/100 · Unfinished process — References files that are not bundled: scripts/prepare-non-spa-asset.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 · 2
✓ No critical or high findings
Medium and low: 2
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bashallowed-tools: Read Write Edit Grep Glob Bash WebSearch AskUserQuestion Skill TaskCreate TaskUpdate TaskList mcp__plugin_power-pages_microsoft-learn__microsoft_docs_search mcp__plugin_power-pages_micr
-
low Obfuscation
obf-base64-blobreferences/styling/sources.md:59Long base64-looking blob (detector / deny-list definition)- [Microsoft Nonprofits, enhanced-model portal source](https://github.com/microsoft/Nonprofits/tree/b3da…e80/VolunteerEngagement/Portal-EDM/.powerpages-site): examples
detector
Files scanned: 22. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 8714 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: scripts/prepare-non-spa-asset.js
Process rating: all ten parameters 45/100
- 0Tools and files. 1 referenced file(s) missing: scripts/prepare-non-spa-asset.js
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 47 mutating operations with no state check
- 40Execution cost. Instruction body is 8714 tokens: crowds the task out of the window
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 68 steps
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 11 top-level sections: this looks like several domains in one skill
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
- +3Output format is not stated: the model decides each time
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 533: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 68 items
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (5 of 11)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.