Individual skill
dataflows-cli
Manages Fabric Dataflow Gen2 items, including creation, M editing, connections, output destinations, getDefinition and updateDefinition inspection, executeQuery, refresh history, and Gen1-to-Gen2 save-as upgrades via saveAsNativeArtifact. Use for Dataflow items or Power Query M definitions. For pipeline JSON use pipeline-migration; for Spark or Warehouse transformations use their own skills.
skills/dataflows-cli/SKILL.md
Source commit 4c3986d2e5b498ce2d6e6025533b94b5e5bb2ccd
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,325
- Repository last updated
- Nov 5, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- writing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 9,709 bytesSKILL.mdcore · 9,709 bytesSKILL.mdcore · 9,709 bytesapm.ymlasset · 445 bytesreferences/authoring.mddoc · 56,644 bytesreferences/authoring/authoring-cli-quickref.mddoc · 23,953 bytesreferences/authoring/authoring-script-templates.mddoc · 81,609 bytesreferences/authoring/charts/bar_chart.pyruns · 3,949 bytesreferences/authoring/charts/line_chart.pyruns · 3,624 bytesreferences/authoring/connection-management.mddoc · 40,768 bytesreferences/authoring/connectors.mddoc · 15,055 bytesreferences/authoring/m-language.mddoc · 9,953 bytesreferences/authoring/mashup-preview.mddoc · 28,938 bytesreferences/authoring/output-destinations.mddoc · 40,559 bytesreferences/consumption.mddoc · 29,427 bytesreferences/consumption/chart-visualization.mddoc · 2,632 bytesreferences/consumption/charts/bar_chart.pyruns · 3,949 bytesreferences/consumption/charts/line_chart.pyruns · 3,624 bytesreferences/consumption/consumption-cli-quickref.mddoc · 6,810 bytesreferences/consumption/discovery-queries.mddoc · 7,156 bytesreferences/consumption/script-templates.mddoc · 17,483 bytesreferences/upgrade.mddoc · 21,472 bytesreferences/upgrade/risk-assessment-guide.mddoc · 11,512 bytesreferences/upgrade/upgrade-cli-quickref.mddoc · 8,967 bytes
Read excerpt
> **Telemetry — MANDATORY.** Every `api.fabric.microsoft.com` call must carry
> `x-ms-fabric-skill: dataflows-cli` (`az rest`: `--headers "x-ms-fabric-skill=dataflows-cli"`),
> including every LRO poll, `fabric_lro` and retry. Snippets omit it — add it anyway.
> **CRITICAL NOTES**
> 1. To find the workspace details (including its ID) from workspace name: list all workspaces and, then, use JMESPath filtering
> 2. To find the item details (including its ID) from workspace ID, item type, and item name: list all items of that type in that workspace and, then, use JMESPath filtering
> 3. **Skill disambiguation**: use `dataflows-cli` for every Fabric Dataflow Gen2 item and Power Query M concern. Synapse / ADF pipeline and dataset JSON translation is `pipeline-migration`; Spark notebook transformations are `spark-cli`; T-SQL transformations are `sqldw-cli`.
# Fabric Dataflow Gen2 -- CLI Skill
This one skill owns Fabric Dataflow Gen2 items: connections, Power Query M, output destinations, saved definitions, refresh history, and Gen1 upgrades.
It is a **mode dispatcher** and contains NO procedures. Pick the mode that matches the request from the table below, then **read the matching `references/<mode>.md` file end to end with your file-reading tool BEFORE issuing a single command**. That file holds the endpoints, payload shapes, templates and gotchas; acting without it produces wrong payloads and wrong results.