[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F4HSGC77EGZSVPDT0A2E9J":3,"skill-same:01M7F4HSGC77EGZSVPDT0A2E9J":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7F4HSGC77EGZSVPDT0A2E9J","microsoft-fabric-pipeline-operations",null,"Create, update, run, schedule, and monitor Microsoft Fabric Data Factory pipelines through the Fabric REST API. Use for Fabric pipeline items (DataPipeline) and Copy Jobs, pipeline definition JSON payloads, pipeline activities (Copy, Notebook, Lookup, ForEach), triggering a pipeline run via the job scheduler API, monitoring pipeline runs and activity runs, or setting up pipeline schedules in Microsoft Fabric.","cwik-tech\u002Foctopus","cwik-tech","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54542292?v=4","01M7F42E123GEHVK6RWC5MSWJ9","Tomasz Cwik","01M7F42E1PD4P54MTG8PG32VCV",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fagents\u002Fdata-pipeline-engineer\u002Fskills\u002Fmicrosoft-fabric-pipeline-operations\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: microsoft-fabric-pipeline-operations\ndescription: >\n  Create, update, run, schedule, and monitor Microsoft Fabric Data Factory pipelines through the Fabric REST API. Use for Fabric pipeline items (DataPipeline) and Copy Jobs, pipeline definition JSON payloads, pipeline activities (Copy, Notebook, Lookup, ForEach), triggering a pipeline run via the job scheduler API, monitoring pipeline runs and activity runs, or setting up pipeline schedules in Microsoft Fabric.\n---\n\n# Microsoft Fabric Pipeline Operations\n\n## Outcome\n\nManage Fabric Data Factory pipelines as code: create or update pipeline item definitions via REST, trigger runs, monitor them to a terminal state, and attach schedules — with approval for every mutation.\n\n## Setup\n\n1. Follow the `microsoft-fabric-api-operations` skill first: Entra ID identity, token scope `https:\u002F\u002Fapi.fabric.microsoft.com\u002F.default`, base URL `https:\u002F\u002Fapi.fabric.microsoft.com\u002Fv1`, LRO polling, and 429 handling all apply. Never place connection credentials or tokens in pipeline JSON or artifacts — Fabric pipelines reference connection objects and workspace identities, not inline secrets.\n2. Verify the workspace and capacity: `GET \u002Fv1\u002Fworkspaces` and confirm the target workspace ID. Pipeline creation requires a workspace on a Fabric capacity and Member or Admin workspace role for writes.\n3. Check item-type support for your identity: the DataPipeline item reference pages state service-principal support; verify before automating with one.\n\n## Pipeline definitions as items\n\n- A pipeline is an item of `type: \"DataPipeline\"`. Create it: `POST \u002Fv1\u002Fworkspaces\u002F{workspaceId}\u002Fitems` with `{displayName, type: \"DataPipeline\"}`, or with a `definition` payload for a fully defined pipeline. `POST` may return 202 — poll the `Location` header until `Succeeded`.\n- The definition is a set of base64-encoded parts under `definition.parts[]`: `pipeline-content.json` (the pipeline: `properties.activities[]` with `dependsOn`, `parameters`, `variables`) plus the `.platform` metadata part. Fetch the current definition with `POST \u002Fv1\u002Fworkspaces\u002F{wsId}\u002Fitems\u002F{itemId}\u002FgetDefinition`; replace it with `POST ...\u002FupdateDefinition`. Always `getDefinition` before `updateDefinition` so the change is a reviewable diff and the prior definition is the rollback.\n- Activities: `Copy` (data movement with source\u002Fsink, translator, staging), `Lookup`, `SetVariable`, `ForEach`, `IfCondition`, `Notebook`, plus `ExecutePipeline`. Chained execution uses `dependsOn: [{activity, dependencyConditions: [\"Succeeded\"]}]`.\n- Copy Job: a separate item type (`CopyJob`) for managed copy-with-incremental behavior; create it the same way with `type: \"CopyJob\"`. Prefer it over hand-built Copy activities when the requirement is simple ongoing data movement.\n\n## Run, monitor, schedule\n\n- Trigger on demand: `POST \u002Fv1\u002Fworkspaces\u002F{wsId}\u002Fitems\u002F{itemId}\u002Fjobs\u002Finstances?jobType=Pipeline` returns 202 with a `Location` header pointing at the job instance.\n- Monitor: `GET \u003CLocation>` (or `GET \u002Fv1\u002Fworkspaces\u002F{wsId}\u002Fitems\u002F{itemId}\u002Fjobs\u002Finstances\u002F{jobInstanceId}`) until `status` is `Completed`, `Failed`, or `Cancelled`. List recent runs with `GET ...\u002Fjobs\u002Finstances`. For activity-level detail, use the pipeline run monitoring guidance in the Data Factory docs.\n- Schedule: create a schedule on the item via the job scheduler schedules API (`POST \u002Fv1\u002Fworkspaces\u002F{wsId}\u002Fitems\u002F{itemId}\u002Fjobs\u002FPipeline\u002Fschedules`) with `enabled`, `configuration` (cron-type with `startDateTime`, `endDateTime`, `localTimeZoneId`, `times`), and `owner`. New schedules start disabled until approved.\n- Cancel: `POST ...\u002Fjobs\u002Finstances\u002F{id}\u002Fcancel` — mutating, requires approval and a reason.\n\n## Permissions and safety\n\n- Reads (`getDefinition`, item\u002Frun lists) are unrestricted. Creates, definition updates, runs, schedule changes, and deletes require a written plan (workspace ID, item ID, definition diff or run parameters) and explicit user approval. Deleting a pipeline item requires confirming no schedule or downstream dependency uses it, and a saved definition for rollback.\n- Workflow: inspect (get item + definition) → plan (definition diff) → execute (update, poll LRO) → verify (re-read definition; trigger a run and watch it reach terminal state) → rollback (re-`updateDefinition` from the saved definition).\n\n## Troubleshooting\n\n- `updateDefinition` fails validation: `pipeline-content.json` must be valid pipeline JSON and base64-encoded per part; check part `path` values exactly match (`pipeline-content.json`, `.platform`).\n- Run stuck or never starts: you ignored the 202 `Location` — poll the job instance; also check capacity throttling (429 with `Retry-After`).\n- Copy activity fails on connection: the pipeline references a Fabric connection ID that does not exist in this workspace or the caller lacks access; list connections and rebind before rerunning.\n- Run shows `Failed` with no detail at the job level: fetch activity-run details per the monitoring doc; job-instance status alone hides the failing activity.\n- Schedule fires at the wrong time: `localTimeZoneId` must be a valid Windows\u002FIANA zone; verify with a get-schedule call after creation.\n\n## References\n\n- Fabric pipelines via REST (Data Factory): https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Ffabric\u002Fdata-factory\u002Fpipeline-rest-api\n- Create Data Pipeline: https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Frest\u002Fapi\u002Ffabric\u002Fdatapipeline\u002Fitems\u002Fcreate-data-pipeline\n- Update pipeline definition: https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Frest\u002Fapi\u002Ffabric\u002Fdatapipeline\u002Fitems\u002Fupdate-data-pipeline-definition\n- Data pipeline item reference: https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Frest\u002Fapi\u002Ffabric\u002Fdatapipeline\u002Fitems\n- Run on-demand item job: https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Frest\u002Fapi\u002Ffabric\u002Fcore\u002Fjob-scheduler\u002Frun-on-demand-item-job\n- Monitor pipeline runs: https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Ffabric\u002Fdata-factory\u002Fmonitor-pipeline-runs\n- Item definition format: https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Frest\u002Fapi\u002Ffabric\u002Farticles\u002Fitem-management\u002Fdefinitions\u002Fitem-definition-overview\n\n## Shared resources\n\nLoad only if the task needs them; the skill is self-contained without them.\n\n- `..\u002F..\u002Ftemplates\u002Fpipeline-design-specification.md`\n- `..\u002F..\u002Ftemplates\u002Fincident-runbook.md`\n- `..\u002F..\u002Freferences\u002Freliability-and-slo-guide.md`\n\n## Completion check\n\n`getDefinition` matches the approved pipeline definition, the triggered run reached `Completed` (or a diagnosed terminal state) with activity-level evidence, any schedule exists with the approved times and timezone, and no credentials appear in the pipeline JSON or any artifact.\n","# Microsoft Fabric Pipeline Operations\n\n## Outcome\n\nManage Fabric Data Factory pipelines as code: create or update pipeline item definitions via REST, trigger runs, monitor them to a terminal state, and attach schedules — with approval for every mutation.\n\n## Setup\n\n1. Follow the `microsoft-fabric-api-operations` skill first: Entra ID identity, token scope `https:\u002F\u002Fapi.fabric.microsoft.com\u002F.default`, base URL `https:\u002F\u002Fapi.fabric.microsoft.com\u002Fv1`, LRO polling, and 429 handling all apply. Never place connection credentials or tokens in pipeline JSON or artifacts — Fabric pipelines reference connection objects and workspace identities, not inline secrets.\n2. Verify the workspace and capacity: `GET \u002Fv1\u002Fworkspaces` and confirm the target workspace ID. Pipeline creation requires a workspace on a Fabric capacity and Member or Admin workspace role for writes.\n3. Check item-type support for your identity: the DataPipeline item reference pages state service-principal support; verify before automating with one.\n\n## Pipeline definitions as items\n\n- A pipeline is an item of `type: \"DataPipeline\"`. Create it: `POST \u002Fv1\u002Fworkspaces\u002F{workspaceId}\u002Fitems` with `{displayName, type: \"DataPipeline\"}`, or with a `definition` payload for a fully defined pipeline. `POST` may return 202 — poll the `Location` header until `Succeeded`.\n- The definition is a set of base64-encoded parts under `definition.parts[]`: `pipeline-content.json` (the pipeline: `properties.activities[]` with `dependsOn`, `parameters`, `variables`) plus the `.platform` metadata part. Fetch the current definition with `POST \u002Fv1\u002Fworkspaces\u002F{wsId}\u002Fitems\u002F{itemId}\u002FgetDefinition`; replace it with `POST ...\u002FupdateDefinition`. Always `getDefinition` before `updateDefinition` so the change is a reviewable diff and the prior definition is the rollback.\n- Activities: `Copy` (data movement with source\u002Fsink, translator, staging), `Lookup`, `SetVariable`, `ForEach`, `IfCondition`, `Notebook`, plus `ExecutePipeline`. Chained execution uses `dependsOn: [{activity, dependencyConditions: [\"Succeeded\"]}]`.\n- Copy Job: a separate item type (`CopyJob`) for managed copy-with-incremental behavior; create it the same way with `type: \"CopyJob\"`. Prefer it over hand-built Copy activities when the requirement is simple ongoing data movement.\n\n## Run, monitor, schedule\n\n- Trigger on demand: `POST \u002Fv1\u002Fworkspaces\u002F{wsId}\u002Fitems\u002F{itemId}\u002Fjobs\u002Finstances?jobType=Pipeline` returns 202 with a `Location` header pointing at the job instance.\n- Monitor: `GET \u003CLocation>` (or `GET \u002Fv1\u002Fworkspaces\u002F{wsId}\u002Fitems\u002F{itemId}\u002Fjobs\u002Finstances\u002F{jobInstanceId}`) until `status` is `Completed`, `Failed`, or `Cancelled`. List recent runs with `GET ...\u002Fjobs\u002Finstances`. For activity-level detail, use the pipeline run monitoring guidance in the Data Factory docs.\n- Schedule: create a schedule on the item via the job scheduler schedules API (`POST \u002Fv1\u002Fworkspaces\u002F{wsId}\u002Fitems\u002F{itemId}\u002Fjobs\u002FPipeline\u002Fschedules`) with `enabled`, `configuration` (cron-type with `startDateTime`, `endDateTime`, `localTimeZoneId`, `times`), and `owner`. New schedules start disabled until approved.\n- Cancel: `POST ...\u002Fjobs\u002Finstances\u002F{id}\u002Fcancel` — mutating, requires approval and a reason.\n\n## Permissions and safety\n\n- Reads (`getDefinition`, item\u002Frun lists) are unrestricted. Creates, definition updates, runs, schedule changes, and deletes require a written plan (workspace ID, item ID, definition diff or run parameters) and explicit user approval. Deleting a pipeline item requires confirming no schedule or downstream dependency uses it, and a saved definition for rollback.\n- Workflow: inspect (get item + definition) → plan (definition diff) → execute (update, poll LRO) → verify (re-read definition; trigger a run and watch it reach terminal state) → rollback (re-`updateDefinition` from the saved definition).\n\n## Troubleshooting\n\n- `updateDefinition` fails validation: `pipeline-content.json` must be valid pipeline JSON and base64-encoded per part; check part `path` values exactly match (`pipeline-content.json`, `.platform`).\n- Run stuck or never starts: you ignored the 202 `Location` — poll the job instance; also check capacity throttling (429 with `Retry-After`).\n- Copy activity fails on connection: the pipeline references a Fabric connection ID that does not exist in this workspace or the caller lacks access; list connections and rebind before rerunning.\n- Run shows `Failed` with no detail at the job level: fetch activity-run details per the monitoring doc; job-instance status alone hides the failing activity.\n- Schedule fires at the wrong time: `localTimeZoneId` must be a valid Windows\u002FIANA zone; verify with a get-schedule call after creation.\n\n## References\n\n- Fabric pipelines via REST (Data Factory): https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Ffabric\u002Fdata-factory\u002Fpipeline-rest-api\n- Create Data Pipeline: https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Frest\u002Fapi\u002Ffabric\u002Fdatapipeline\u002Fitems\u002Fcreate-data-pipeline\n- Update pipeline definition: https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Frest\u002Fapi\u002Ffabric\u002Fdatapipeline\u002Fitems\u002Fupdate-data-pipeline-definition\n- Data pipeline item reference: https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Frest\u002Fapi\u002Ffabric\u002Fdatapipeline\u002Fitems\n- Run on-demand item job: https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Frest\u002Fapi\u002Ffabric\u002Fcore\u002Fjob-scheduler\u002Frun-on-demand-item-job\n- Monitor pipeline runs: https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Ffabric\u002Fdata-factory\u002Fmonitor-pipeline-runs\n- Item definition format: https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Frest\u002Fapi\u002Ffabric\u002Farticles\u002Fitem-management\u002Fdefinitions\u002Fitem-definition-overview\n\n## Shared resources\n\nLoad only if the task needs them; the skill is self-contained without them.\n\n- `..\u002F..\u002Ftemplates\u002Fpipeline-design-specification.md`\n- `..\u002F..\u002Ftemplates\u002Fincident-runbook.md`\n- `..\u002F..\u002Freferences\u002Freliability-and-slo-guide.md`\n\n## Completion check\n\n`getDefinition` matches the approved pipeline definition, the triggered run reached `Completed` (or a diagnosed terminal state) with activity-level evidence, any schedule exists with the approved times and timezone, and no credentials appear in the pipeline JSON or any artifact.\n",{"name":5,"description":7},"main","f0f0efe1d4c64b51a51f44427ad147750d29154e","agents\u002Fdata-pipeline-engineer\u002Fskills\u002Fmicrosoft-fabric-pipeline-operations","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus","www.cuteoctopus.site","https:\u002F\u002Fgithub.com\u002Fcwik-tech","2026-10-27 06:12:19",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add cwik-tech\u002Foctopus --skill microsoft-fabric-pipeline-operations",{"tool":37,"command":38},"bunx","bunx skills add cwik-tech\u002Foctopus --skill microsoft-fabric-pipeline-operations",{"tool":40,"command":41},"pnpm","pnpm dlx skills add cwik-tech\u002Foctopus --skill microsoft-fabric-pipeline-operations","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fagents\u002Fdata-pipeline-engineer\u002Fskills\u002Fmicrosoft-fabric-pipeline-operations\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7F5MQVQ3CHGM77Q51M4B1AC","twenty-year-land-plan","Apply the Bren discipline of evaluating every land and development decision on a twenty-year horizon, with a comprehensive plan for how the land, the community, and the surrounding public infrastructure evolve together. Deals optimized for a five-year exit are structurally different from deals that compound across generations; insist on knowing which kind you are making. Use when evaluating land, entitlements, master-planned development, or phasing decisions, and when separating five-year exit deals from generational holds.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Ftwenty-year-land-plan\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7F5MGQ8JSV27SFDQVVGFQE3","thematic-gut-check","Apply the Gray discipline of identifying the structural theme behind every real estate deal, testing where that theme sits in its capital-flow lifecycle, and insisting that deals without a named theme — or deals late in a crowded theme — clear a higher bar. A mediocre deal in a strong theme usually beats a clever deal in a weak one. Use when naming the structural thesis behind a deal, judging whether that theme is early or crowded, and setting the bar the deal must clear.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Fthematic-gut-check\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7F5M8V64Y0ZD8PTPWEJQXJ9","supply-pipeline-gut-check","Apply the Zell discipline of grounding every real estate thesis in the local supply pipeline. Demand counts over adjectives — units under construction, units permitted, units proposed — and convert them into a forward absorption schedule. A deal that ignores the pipeline is a bet on a market you have not actually studied. Use when validating a market thesis, forecasting absorption and rent growth, or counting units under construction, permitted, and proposed.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Fsupply-pipeline-gut-check\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7F5M3J2Q146BJC13TD3YCXF","ruin-scenario-mapping","Apply the Taleb discipline of identifying, for every real estate deal, the specific chain of events that produces ruin — permanent, unrecoverable capital loss — and verifying that no single such chain has non-trivial probability. Deals with any plausible ruin path must be restructured or abandoned. Use when sizing leverage, testing refinancing, covenant, and liquidity risk, or checking whether any single failure chain can permanently wipe out the position.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Fruin-scenario-mapping\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7F5KZDS0DYD172P6HS0WXEM","revenue-cost-architecture","Design a venture's revenue streams, pricing logic, cost structure, and unit economics so the business model has a coherent theory of value capture, not just value creation. Use after the value proposition and customer segment are set and before financial projections, when choosing a pricing model, calculating contribution margin or CAC payback, or checking whether the unit economics hold at scale.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Frevenue-cost-architecture\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7F5KP1CNQMYAVCDTV4EEW3J","replacement-cost-stress-test","Apply the Buffett discipline of pricing every real estate asset against the cost to rebuild it from scratch. The ratio of purchase price to replacement cost sets a ceiling on long-run downside: below replacement cost, new supply cannot profitably undercut you; at or above it, you are buying a liability disguised as an asset. Use when setting a purchase price, judging downside protection, or testing how exposed an asset is to newly built competing supply.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Freplacement-cost-stress-test\u002FSKILL.md",[],[]]