SKILLEMALL.ai
GitHub ↗ RU Sign in

BF deploy-pipeline

Triggers a Power Platform Pipeline deployment run for a Power Pages solution. Selects a target stage, validates the package, optionally configures deployment settings (environment variables, connection references), then deploys and polls for completion. Use when asked to: "deploy pipeline", "run pipeline", "trigger deployment", "deploy to staging", "deploy to production", "run power platform pipeline", "deploy solution via pipeline", "promote solution", "push to staging", "push to production".

microsoft/power-platform-skills Claude Code author: microsoft 3 files body ≈ 26 650 tokens Open the sourcegithub.com↗ analyzed 2 h ago

Triggers a Power Platform Pipeline deployment run for a Power Pages solution.

As a process F 51/100 · Will not run — References files that are not bundled: scripts/lib/verify-env-var-values.js

ProcedureInfrastructuretype 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%
90
Quality 40%
68
Run on models
none yet
Process rating
F
51/100
Will not run
References files that are not bundled: scripts/lib/verify-env-var-values.js
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.

Concealment 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 tells the agent to hide things from you: not to show errors, not to mention actions, to report differently from what was done. You lose the ability to see what the agent really did.

For the author

Transparency beats a smooth answer. If the goal is to hide technical noise, ask the agent to "summarise briefly", not to "not mention".

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 · 2

✓ No critical or high findings

Medium and low: 2
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash
    allowed-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
  • medium Concealment en-hide-from-user SKILL.md:124
    Instruction to hide actions from the user (security demo / example)
    1. **Resolve the project's configured environment URL first, then assert PAC is actually connected to it.** `verify-alm-prerequisites.js` resolves the env from PAC's *ambient org context* (`pac env wh
    demo

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

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 26650 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: scripts/lib/verify-env-var-values.js
  • note edit-residue the text marks something as outdated (lines 102, 135, 140, 196, 258, 359): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 51/100

Will not run. References files that are not bundled: scripts/lib/verify-env-var-values.js
  • 0Tools and files. 1 referenced file(s) missing: scripts/lib/verify-env-var-values.js
  • 0Result and completion. Does not say what the result is
  • 10Execution cost. Instruction body is 26650 tokens: crowds the task out of the window
  • 50When it triggers. No condition that starts the skill
  • 60Steps. 150 steps, 4 vague phrases
  • 100Inputs and preconditions. Inputs and preconditions are listed
  • 100Failures and branches. 11 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 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

  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • -223 emoji in the instructions: noise for the model
  • -31 of 1 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 10 example trigger phrases
  • +3Description length 498: enough signal without eating the budget
  • +4Structure: 18 headings
  • +3Step-by-step instructions: 150 items
  • +4Has examples (54 code blocks)

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