SKILLEMALL.ai

BF setup-pipeline

Sets up a Power Platform Pipeline for automated Power Pages deployments. Power Platform Pipelines is Microsoft's native CI/CD tool built into the Power Platform — no external infrastructure required. Use when asked to: "set up ci/cd", "create pipeline", "setup pipeline", "set up power platform pipelines", "create power pipelines", "automate deployments", "set up automated deployment", "create deployment pipeline", "use power pipelines". Also handles: "set up github actions" or "set up azure devops pipeline" (shows coming-soon guidance for those platforms).

microsoft/power-platform-skills Claude Code author: microsoft 2 files body ≈ 10 490 tokens Open the sourcegithub.com analyzed 2 h ago

Sets up a Power Platform Pipeline for automated Power Pages deployments.

As a process F 55/100 · Will not run — References files that are not bundled: references/cicd-pipeline-patterns.md, scripts/lib/create-deployment-environment.js

ProcedureGitHubAzureInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
82/100
safety, quality, tests
Safety 60%
95
Quality 40%
62
Run on models
none yet
Process rating
F
55/100
Will not run
References files that are not bundled: references/cicd-pipeline-patterns.md, scripts/lib/create-deployment-environment.js
Tools and files w 18
0
Result and completion w 14
0
Execution cost w 6
40
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 TaskCreate TaskUpdate TaskList AskUserQuestion mcp__plugin_power-pages_microsoft-learn__microsoft_docs_search mcp__plugin_power-pages_microsoft-learn__mic

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

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 10490 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: references/cicd-pipeline-patterns.md
  • warning missing-ref reference to a missing file: scripts/lib/create-deployment-environment.js
  • note edit-residue the text marks something as outdated (lines 184, 478, 484): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 55/100

Will not run. References files that are not bundled: references/cicd-pipeline-patterns.md, scripts/lib/create-deployment-environment.js
  • 0Tools and files. 2 referenced file(s) missing: references/cicd-pipeline-patterns.md, scripts/lib/create-deployment-environment.js
  • 0Result and completion. Does not say what the result is
  • 40Execution cost. Instruction body is 10490 tokens: crowds the task out of the window
  • 70When it triggers. States when to use, but not when not to
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 85Steps. 84 steps, 1 vague phrases
  • 100Failures and branches. 7 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

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
  • -5TODO / placeholder text left in the skill
  • -31 of 1 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 11 example trigger phrases
  • +3Description length 562: enough signal without eating the budget
  • +4Structure: 19 headings
  • +3Step-by-step instructions: 84 items
  • +4Has examples (19 code blocks)

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