setup-pipeline SKILL.md skillA
setup-pipeline from microsoft/power-platform-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add microsoft/power-platform-skills/setup-pipeline@git:20261024.aed70bfPins git:20261024.aed70bf in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- microsoft/power-platform-skills
- Path
plugins/power-pages/skills/setup-pipeline/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261024.aed70bf, committed Oct 24, 2026
- First version recorded
- Jun 12, 2026
- Size
- 43,214 bytes
- Repository stars
- 1,123
- License
- MIT
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…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
> **Plugin check**: Run `node "${PLUGIN_ROOT}/scripts/check-version.js"` — if it outputs a message, show it to the user before proceeding.
# setup-pipeline
Sets up a **Power Platform Pipeline** for automated Power Pages solution deployments. Creates the pipeline configuration directly in Dataverse using the PP Pipelines OData API — no YAML files, no external CI/CD infrastructure needed.
GitHub Actions and Azure DevOps Pipeline options are shown in the platform menu as **coming soon**.
> Refer to `${PLUGIN_ROOT}/references/cicd-pipeline-patterns.md` for all HAR-confirmed API patterns used in this skill.
## Prerequisites
- `powerpages.config.json` exists in the project root
- `.solution-manifest.json` exists (solution must be created first via `setup-solution`)
- Azure CLI logged in (`az account show` succeeds)
- PAC CLI logged in (`pac env who` succeeds)
- A Power Platform environment with Pipelines package installed (the "host" environment)
## Phases
### Phase 0 — ALM plan gate
…Read the whole file at its exact version.
How to install
mdr add microsoft/power-platform-skills/setup-pipeline@sha256:e4e47e71af0e9a47The line at the top of this page pins the label git:20261024.aed70bf, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_23sg6v7swzcpbfl3)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Jun 12, 2026 and Oct 24, 2026, about one every 27 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261024.aed70bf latest | 2026-10-24 | aed70bf | 43,214 B | A | view · diff |
| git:20260622.64b8451 | 2026-06-22 | 64b8451 | 43,239 B | A | view · diff |
| git:20260622.c419336 | 2026-06-22 | c419336 | 42,898 B | A | view · diff |
| git:20260619.f001179 | 2026-06-19 | f001179 | 41,412 B | A | view · diff |
| git:20260618.a781215 | 2026-06-18 | a781215 | 41,517 B | A | view · diff |
| git:20260612.180ed78 | 2026-06-12 | 180ed78 | 40,731 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (43214 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
microsoft/power-platform-skills · 1,123 stars · license MIT · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_23sg6v7swzcpbfl3 GET https://markdownregistry.com/api/v1/resolve?ref=microsoft/power-platform-skills/setup-pipeline GET https://markdownregistry.com/api/v1/blob/e4e47e71af0e9a4702722dc32d01bd4a9b5480ea1d41d8e3b991b04e2f030d9b
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.