SKILLEMALL.ai
GitHub ↗ RU Sign in

BF publish-pcf-companion

Deploy the dispatcher PCF for a third-party `.ppmplugin` control to a Power Platform environment via `pac pcf push`. The dispatcher PCF is the Studio-side control that dispatches the composite key `<name>/<receiver>` over the wrap shell's `SendMessagePlugin` bridge to the control's native module. Verifies deploy prereqs (Node.js 20+ with npm, .NET SDK, and active `pac auth`), then three confirmation gates — publisher prefix (2–8 chars; defaults to `pamext` or the last-used value from `.extension-state.md`), version bump (patch / minor / major / no-bump), target environment URL (from `pac org who`). Builds the PCF if needed, then pushes. Decoupled from /generate-pcf-companion so the engineer can scaffold and customize locally, then deploy when ready. Updates `.extension-state.md` with deployment history (timestamp, env URL, version, prefix used).

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

Deploy the dispatcher PCF for a third-party .ppmplugin control to a Power Platform environment via pac pcf push. The dispatcher PCF is the Studio-side control…

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

IntegrationInfrastructuretype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
B
81/100
safety, quality, tests
Safety 60%
95
Quality 40%
59
Run on models
none yet
Process rating
F
48/100
Will not run
References files that are not bundled: ../../shared/shared-instructions.md, ../../shared/naming-conventions.md, ../../shared/prereq-check.md
Tools and files w 18
0
Result and completion w 14
0
Progress reporting w 2
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. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
  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 body-long SKILL.md body ≈ 5338 tokens (recommended < 5000); move details to references/
  • 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/prereq-check.md

Process rating: all ten parameters 48/100

Will not run. References files that are not bundled: ../../shared/shared-instructions.md, ../../shared/naming-conventions.md, ../../shared/prereq-check.md
  • 0Tools and files. 3 referenced file(s) missing: ../../shared/shared-instructions.md, ../../shared/naming-conventions.md, ../../shared/prereq-check.md
  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 30Inputs and preconditions. Does not say what the process needs to start
  • 50When it triggers. No condition that starts the skill
  • 70Execution cost. Instruction body is 5338 tokens
  • 85Steps. 15 steps, 1 vague phrases
  • 100Failures and branches. 5 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low The response is described with custom markup (30 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 857: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 16 headings
  • +3Step-by-step instructions: 15 items
  • +4Has examples (10 code blocks)

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