deploylisted
Install: claude install-skill wardawgmalvicious/claude-plugins
# Deploying Fabric content
A deploy moves item definitions from a source, a Git branch or a
workspace, into a target workspace. Four routes do it, each with its own
reference; this file picks one and wraps it in the steps every route
shares. Take them in order: a wrong route invalidates every step after
it.
Past a route's reference, its tool's own docs as markdown source,
`curl -s https://raw.githubusercontent.com/microsoft/<repo>/main/docs/<path>.md`
with `<repo>` `fabric-cicd` or `fabric-cli`, then Learn, by
`microsoft-learn-mcp` (`microsoft_docs_search`, then
`microsoft_docs_fetch`), or with no server, `curl -sL -H 'Accept: text/markdown' <page URL>` (undocumented, read 2026-11-07). A live page that contradicts a line here wins:
say so, act on the page, and route the fix by `capture-learning`, bar
a dated measured line that names the page it overrules and the call that
measured it, which a page changed since its date sends back to re-measure.
An observed claim is cited or marked pending a doc check, and stands, marked
observed, only where no page covers it.
## 1. Pick the route
| Source of truth | Route | Learn's option | Read |
| --- | --- | --- | --- |
| Git, one branch pushed to each stage by a script or CI | the fabric-cicd Python library | 2 | [fabric-cicd.md](references/fabric-cicd.md) |
| Git, the same in one command | `fab deploy --config`, which wraps the library and reads its `config.yml` and `parameter.yml` | 2 | [fab-deploy.md](references/fab-deploy.md), th