SKILLEMALL.ai

BF assemble-ppmplugin

Assemble the final `.ppmplugin` binary bundle for a PAM native extension and verify its contents. First **reconciles** the manifest's declared `entrypoints` against the binaries actually staged — if the manifest declares a platform with no built binary it gates (build it / ship without it / stop) rather than shipping a broken bundle. Then re-runs the plugin's upload-compatibility checks on the reconciled manifest, zips the manifest plus whichever of `android/<PascalName>Plugin.dex` and `ios/<PascalName>Plugin.framework/` are present into `ppmplugin/<name>.ppmplugin`, and verifies the archive layout with `jar tf` (exactly the manifest + the shipped binaries — nothing missing, nothing extra). Output: a statically verified `.ppmplugin` file on disk. Prereqs: `jar` (JDK). Run after /generate-ppmplugin-manifest and the build skill(s).

microsoft/power-platform-skills Agent Skills author: microsoft 1 file body ≈ 2 185 tokens Open the sourcegithub.com analyzed 2 h ago

Assemble the final .ppmplugin binary bundle for a PAM native extension and verify its contents. First reconciles the manifest's declared entrypoints against…

As a process F 41/100 · Will not run — References files that are not bundled: ../generate-ppmplugin-manifest/SKILL.md, ../../shared/ppmplugin-format.md, ../../shared/shared-instructions.md

AnalyzerFinancetype and topics are labelled automatically from the skill text
JSON
Technical rating
B
80/100
safety, quality, tests
Safety 60%
95
Quality 40%
57
Run on models
none yet
Process rating
F
41/100
Will not run
References files that are not bundled: ../generate-ppmplugin-manifest/SKILL.md, ../../shared/ppmplugin-format.md, ../../shared/shared-instructions.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
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. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  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 · 1

✓ No critical or high findings

Medium and low: 1
  • 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

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

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: ../generate-ppmplugin-manifest/SKILL.md
  • warning missing-ref reference to a missing file: ../../shared/ppmplugin-format.md
  • warning missing-ref reference to a missing file: ../../shared/shared-instructions.md

Process rating: all ten parameters 41/100

Will not run. References files that are not bundled: ../generate-ppmplugin-manifest/SKILL.md, ../../shared/ppmplugin-format.md, ../../shared/shared-instructions.md
  • 0Tools and files. 3 referenced file(s) missing: ../generate-ppmplugin-manifest/SKILL.md, ../../shared/ppmplugin-format.md, ../../shared/shared-instructions.md
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 55Failures and branches. 1 branches
  • 100Steps. 19 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2185 tokens
  • 100Running it twice. Mutating operations check current state
  • low The response is described with custom markup (12 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)
  • +3Description length 841: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 7 headings
  • +3Step-by-step instructions: 19 items
  • +4Has examples (6 code blocks)

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