SKILLEMALL.ai

CF generate-pcf-companion

Generate the dispatcher PCF for a third-party `.ppmplugin` (wrap-runtime) control. Runs `pac pcf init` in the pcf/ subfolder, rewrites ControlManifest.Input.xml from ARCHITECTURE §6, and writes index.ts derived from ARCHITECTURE §4 (message contract), §8 (PCF surface), §9 (error UX) — no placeholders. The bridge dispatches the composite key `<name>/<receiver>` to `NativeModules.<nativeModule>.<method>` via the host-injected `window.PowerApps.NativeExtension.sendAsync` global (never `cordova.exec` — not in the PCF sandbox); also emits a `PowerAppsNativeExtension.d.ts` ambient declaration. Responses are peeled with `extractResponse`. Emits structured JSON debug/error logs. Validated by `npm run build`. **Local only** — does not deploy. Needs only `pac` CLI. Run after the native module exists. Uses npm (not pnpm).

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

Generate the dispatcher PCF for a third-party .ppmplugin (wrap-runtime) control. Runs pac pcf init in the pcf/ subfolder, rewrites ControlManifest.Input.xml…

As a process F 47/100 · Will not run — References files that are not bundled: ../../shared/ppmplugin-format.md, ../../shared/shared-instructions.md, ../../shared/naming-conventions.md

GeneratorSoftware developmentInfrastructureWriting and documentstype and topics are labelled automatically from the skill text
JSON
Technical rating
C
74/100
safety, quality, tests
Safety 60%
95
Quality 40%
42
Run on models
none yet
Process rating
F
47/100
Will not run
References files that are not bundled: ../../shared/ppmplugin-format.md, ../../shared/shared-instructions.md, ../../shared/naming-conventions.md
Tools and files w 18
0
Result and completion w 14
0
Execution cost w 6
10
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 SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
  3. 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 body-long SKILL.md body ≈ 23362 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: ../../shared/ppmplugin-format.md
  • warning missing-ref reference to a missing file: ../../shared/shared-instructions.md
  • warning missing-ref reference to a missing file: ../../shared/naming-conventions.md
  • warning missing-ref reference to a missing file: ../../shared/repo-layout.md
  • warning missing-ref reference to a missing file: ../../shared/prereq-check.md
  • warning missing-ref reference to a missing file: ../../shared/self-critique-protocol.md

Process rating: all ten parameters 47/100

Will not run. References files that are not bundled: ../../shared/ppmplugin-format.md, ../../shared/shared-instructions.md, ../../shared/naming-conventions.md
  • 0Tools and files. 6 referenced file(s) missing: ../../shared/ppmplugin-format.md, ../../shared/shared-instructions.md, ../../shared/naming-conventions.md
  • 0Result and completion. Does not say what the result is
  • 10Execution cost. Instruction body is 23362 tokens: crowds the task out of the window
  • 30Inputs and preconditions. Does not say what the process needs to start
  • 50When it triggers. No condition that starts the skill
  • 85Steps. 102 steps, 2 vague phrases
  • 100Failures and branches. 6 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 20 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (50 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 822: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -5TODO / placeholder text left in the skill
  • +1No license
  • +2Single-language instructions
  • +4Structure: 40 headings
  • +3Step-by-step instructions: 102 items
  • +4Has examples (27 code blocks)

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