[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699R71NWZGVJXCSBSSRBWSV":3,"skill-same:01M699R71NWZGVJXCSBSSRBWSV":63},{"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":21,"linkOnly":22,"markdownContent":23,"markdownBody":24,"frontMatter":25,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M699R71NWZGVJXCSBSSRBWSV","eventschemaset-cli",null,"Governs Event Schema Sets, the Fabric registries of event types and message payload schemas. Covers create, rename, update and delete of a definition, and listing, property reads or base64 decoding. Every Event Schema Set task belongs here. Ingestion pipelines are eventstream-cli.","microsoft\u002Fskills-for-fabric","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M699NAPJKS2WBHHDN86Q5MM6",1339,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fskills\u002Feventschemaset-cli\u002FSKILL.md",[],[19,20],"cli","eventschemaset cli","2026-11-10 10:12:30",false,"---\nname: eventschemaset-cli\ndescription: \"Governs Event Schema Sets, the Fabric registries of event types and message payload schemas. Covers create, rename, update and delete of a definition, and listing, property reads or base64 decoding. Every Event Schema Set task belongs here. Ingestion pipelines are eventstream-cli.\"\n---\n\n> **Telemetry — MANDATORY.** Every `api.fabric.microsoft.com` call must carry\n> `x-ms-fabric-skill: eventschemaset-cli` (`az rest`: `--headers \"x-ms-fabric-skill=eventschemaset-cli\"`),\n> including every LRO poll, `fabric_lro` and retry. Snippets omit it — add it anyway.\n\n> **CRITICAL NOTES**\n> 1. To find the workspace details (including its ID) from workspace name: list all workspaces and, then, use JMESPath filtering\n> 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\n> 3. **Skill disambiguation**: use `eventschemaset-cli` for the EventSchemaSet catalog item (event types and message schemas). Eventstream is a different item -- a real-time ingestion and routing pipeline; use `eventstream-cli` for it. Eventhouse \u002F KQL Database is another different item; use `eventhouse-cli` for it.\n\n# Fabric Event Schema Set -- CLI Skill\n\nThis one skill owns Fabric Event Schema Sets: authoring the catalog (create, rename, override definition, delete) plus read-only inspection and decoding of its `eventTypes` and `schemas`.\n\n> **Preview**: The Fabric **EventSchemaSet** item and its REST operations are currently in **Preview** -- behavior, response shapes, and availability may change. Every operation is documented as **delegated (user) identity only** (service principals and managed identities listed as not supported), but because the item is in Preview, SP\u002FMI access can succeed and is **tenant-dependent**. Prefer `az login` as a user; on **401\u002F403** with an SP\u002FMI, fall back to a delegated user identity.\n\nIt is a **mode dispatcher** and contains NO procedures. Pick the mode that matches the request from the table below, then **read the matching `references\u002F\u003Cmode>.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.\n\n## Mode selection\n\n| Mode | Use when the request ... | Example triggers | Read this first |\n|---|---|---|---|\n| `authoring` | creates, renames\u002Fre-describes, overrides the definition of, or deletes an Event Schema Set (Create, Update, UpdateDefinition, Delete) | create event schema set, update event schema set definition, add event type to an event schema set, rename event schema set, delete event schema set | [references\u002Fauthoring.md](references\u002Fauthoring.md) |\n| `consumption` | lists or searches Event Schema Sets, inspects item properties, or decodes a definition to enumerate its `eventTypes` and `schemas` | list event schema sets, inspect event schema set, decode event schema set definition, get schema version, list business events | [references\u002Fconsumption.md](references\u002Fconsumption.md) |\n\n### Mode boundary rule\n\n`consumption` may only issue read-only calls (List, Get, GetDefinition). Any state-changing operation (Create, Update, UpdateDefinition, Delete) requires the authoring mode: say so, read `references\u002Fauthoring.md`, then proceed.\n\nIf a request genuinely spans modes (e.g. decode the current definition, then override it), handle them one at a time and read each reference before you start that part. If the mode is ambiguous after reading this table, ask one short clarifying question instead of guessing.\n\n## Terminal write -- the step you must not skip\n\nReading the reference and planning the change is NOT completing the task. The authoring mode ends with one state-changing call. If you did not issue it, nothing was persisted -- say so explicitly rather than reporting success.\n\n| Mode | Terminal write |\n|---|---|\n| `authoring` | The `POST ...\u002FeventSchemaSets`, `PATCH ...\u002FeventSchemaSets\u002F{id}`, `POST ...\u002FeventSchemaSets\u002F{id}\u002FupdateDefinition`, or `DELETE ...\u002FeventSchemaSets\u002F{id}` for the requested change. Composing the request body and showing it to the user is not executing it. |\n| `consumption` | none -- this mode is read-only |\n\nCreate and UpdateDefinition may return `202 Accepted` (LRO): capture the `Location` header and poll until `Succeeded` before reporting success. Where the reference documents a readback, read the artefact back to prove the change landed.\n\n## Shared essentials (all modes)\n\nResolve the workspace and item first; every mode depends on it.\n\n| Task | Reference | Notes |\n|---|---|---|\n| Finding Workspaces and Items in Fabric | [COMMON-CLI.md](..\u002F..\u002Fcommon\u002FCOMMON-CLI.md#finding-workspaces-and-items-in-fabric) | **Mandatory** -- read before resolving any workspace or item id |\n| Fabric Topology & Key Concepts | [COMMON-CORE.md](..\u002F..\u002Fcommon\u002FCOMMON-CORE.md#fabric-topology--key-concepts) | Item types, workspaces, capacities |\n| Environment URLs | [COMMON-CORE.md](..\u002F..\u002Fcommon\u002FCOMMON-CORE.md#environment-urls) | Sovereign \u002F non-public cloud hosts |\n| Authentication & Token Acquisition | [COMMON-CORE.md](..\u002F..\u002Fcommon\u002FCOMMON-CORE.md#authentication--token-acquisition) | Wrong audience = 401; read before any auth issue |\n| Authentication Recipes | [COMMON-CLI.md](..\u002F..\u002Fcommon\u002FCOMMON-CLI.md#authentication-recipes) | `az login` flows and token acquisition |\n| Core Control-Plane REST APIs | [COMMON-CORE.md](..\u002F..\u002Fcommon\u002FCOMMON-CORE.md#core-control-plane-rest-apis) | Pagination, LRO polling, rate limiting |\n| Gotchas & Troubleshooting | [COMMON-CLI.md](..\u002F..\u002Fcommon\u002FCOMMON-CLI.md#gotchas--troubleshooting-cli-specific) | `az rest` audience, shell escaping, token expiry |\n\n## Rules\n\n### MUST\n\n- Select exactly one mode from the table above before doing anything else.\n- Read `references\u002F\u003Cmode>.md` end to end, as your FIRST tool call, before the first command of that mode. Read it ONCE, in a single full read: do not re-open it, do not grep it again, and do not page through it. You already have it.\n- Apply the same read-once discipline to every other file you load, including shared `common\u002F*.md` files: open only the ones you actually need, read each ONCE end to end, and never grep or re-open one you already loaded.\n- Resolve workspace and item ids by listing and filtering, never by guessing a GUID.\n- Announce a mode switch explicitly when the request crosses a boundary.\n- Confirm destructive and overwrite actions before executing -- Delete is permanent (with `?hardDelete=true`) and UpdateDefinition **replaces** the whole definition. When the request already names the target item AND the destructive\u002Foverwrite action explicitly (e.g. \"delete the Event Schema Set X\", \"override X's definition to ...\"), that instruction IS the confirmation: echo the resolved `displayName` + `id` for the audit trail, then proceed with the single write. Pause for a separate yes\u002Fno confirmation ONLY when the target or intent is ambiguous (e.g. \"clean up my workspace\", an unqualified \"the first one\", or a bulk\u002Fwildcard delete).\n- Treat the reference as instructions, never as the deliverable. After reading it, RUN the documented commands against the live workspace and report the real results.\n\n### PREFER\n\n- The narrowest mode that satisfies the request.\n- Reading exactly ONE mode reference. Load a second only when the request genuinely spans modes, and say so before you do.\n- A delegated user identity (`az login`); fall back from SP\u002FMI to a user on 401\u002F403.\n- Reporting the mode you chose in your first response so the user can correct you.\n\n### AVOID\n\n- Acting from this dispatcher alone -- it intentionally omits the operational detail.\n- Answering with a summary of the reference instead of executing it.\n- Re-reading or re-grepping a reference you already loaded; it costs turns and tokens.\n- Mutating anything while in the read-only consumption mode.\n- Confusing EventSchemaSet with Eventstream or Eventhouse (see CRITICAL NOTES 3).\n\n## Examples\n\n| User request | Mode | Reference to read |\n|---|---|---|\n| \"List all Event Schema Sets in my Analytics workspace.\" | `consumption` | [references\u002Fconsumption.md](references\u002Fconsumption.md) |\n| \"Create an Event Schema Set called orders-catalog in Analytics.\" | `authoring` | [references\u002Fauthoring.md](references\u002Fauthoring.md) |\n| \"Decode the definition of orders-catalog and tell me its event types and schemas.\" | `consumption` | [references\u002Fconsumption.md](references\u002Fconsumption.md) |\n| \"Add a BusinessEventType event OrderPlaced (JSON) to orders-catalog.\" | `authoring` | [references\u002Fauthoring.md](references\u002Fauthoring.md) |\n| \"Delete the orders-catalog-old Event Schema Set from Analytics.\" | `authoring` | [references\u002Fauthoring.md](references\u002Fauthoring.md) |\n","> **Telemetry — MANDATORY.** Every `api.fabric.microsoft.com` call must carry\n> `x-ms-fabric-skill: eventschemaset-cli` (`az rest`: `--headers \"x-ms-fabric-skill=eventschemaset-cli\"`),\n> including every LRO poll, `fabric_lro` and retry. Snippets omit it — add it anyway.\n\n> **CRITICAL NOTES**\n> 1. To find the workspace details (including its ID) from workspace name: list all workspaces and, then, use JMESPath filtering\n> 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\n> 3. **Skill disambiguation**: use `eventschemaset-cli` for the EventSchemaSet catalog item (event types and message schemas). Eventstream is a different item -- a real-time ingestion and routing pipeline; use `eventstream-cli` for it. Eventhouse \u002F KQL Database is another different item; use `eventhouse-cli` for it.\n\n# Fabric Event Schema Set -- CLI Skill\n\nThis one skill owns Fabric Event Schema Sets: authoring the catalog (create, rename, override definition, delete) plus read-only inspection and decoding of its `eventTypes` and `schemas`.\n\n> **Preview**: The Fabric **EventSchemaSet** item and its REST operations are currently in **Preview** -- behavior, response shapes, and availability may change. Every operation is documented as **delegated (user) identity only** (service principals and managed identities listed as not supported), but because the item is in Preview, SP\u002FMI access can succeed and is **tenant-dependent**. Prefer `az login` as a user; on **401\u002F403** with an SP\u002FMI, fall back to a delegated user identity.\n\nIt is a **mode dispatcher** and contains NO procedures. Pick the mode that matches the request from the table below, then **read the matching `references\u002F\u003Cmode>.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.\n\n## Mode selection\n\n| Mode | Use when the request ... | Example triggers | Read this first |\n|---|---|---|---|\n| `authoring` | creates, renames\u002Fre-describes, overrides the definition of, or deletes an Event Schema Set (Create, Update, UpdateDefinition, Delete) | create event schema set, update event schema set definition, add event type to an event schema set, rename event schema set, delete event schema set | [references\u002Fauthoring.md](references\u002Fauthoring.md) |\n| `consumption` | lists or searches Event Schema Sets, inspects item properties, or decodes a definition to enumerate its `eventTypes` and `schemas` | list event schema sets, inspect event schema set, decode event schema set definition, get schema version, list business events | [references\u002Fconsumption.md](references\u002Fconsumption.md) |\n\n### Mode boundary rule\n\n`consumption` may only issue read-only calls (List, Get, GetDefinition). Any state-changing operation (Create, Update, UpdateDefinition, Delete) requires the authoring mode: say so, read `references\u002Fauthoring.md`, then proceed.\n\nIf a request genuinely spans modes (e.g. decode the current definition, then override it), handle them one at a time and read each reference before you start that part. If the mode is ambiguous after reading this table, ask one short clarifying question instead of guessing.\n\n## Terminal write -- the step you must not skip\n\nReading the reference and planning the change is NOT completing the task. The authoring mode ends with one state-changing call. If you did not issue it, nothing was persisted -- say so explicitly rather than reporting success.\n\n| Mode | Terminal write |\n|---|---|\n| `authoring` | The `POST ...\u002FeventSchemaSets`, `PATCH ...\u002FeventSchemaSets\u002F{id}`, `POST ...\u002FeventSchemaSets\u002F{id}\u002FupdateDefinition`, or `DELETE ...\u002FeventSchemaSets\u002F{id}` for the requested change. Composing the request body and showing it to the user is not executing it. |\n| `consumption` | none -- this mode is read-only |\n\nCreate and UpdateDefinition may return `202 Accepted` (LRO): capture the `Location` header and poll until `Succeeded` before reporting success. Where the reference documents a readback, read the artefact back to prove the change landed.\n\n## Shared essentials (all modes)\n\nResolve the workspace and item first; every mode depends on it.\n\n| Task | Reference | Notes |\n|---|---|---|\n| Finding Workspaces and Items in Fabric | [COMMON-CLI.md](..\u002F..\u002Fcommon\u002FCOMMON-CLI.md#finding-workspaces-and-items-in-fabric) | **Mandatory** -- read before resolving any workspace or item id |\n| Fabric Topology & Key Concepts | [COMMON-CORE.md](..\u002F..\u002Fcommon\u002FCOMMON-CORE.md#fabric-topology--key-concepts) | Item types, workspaces, capacities |\n| Environment URLs | [COMMON-CORE.md](..\u002F..\u002Fcommon\u002FCOMMON-CORE.md#environment-urls) | Sovereign \u002F non-public cloud hosts |\n| Authentication & Token Acquisition | [COMMON-CORE.md](..\u002F..\u002Fcommon\u002FCOMMON-CORE.md#authentication--token-acquisition) | Wrong audience = 401; read before any auth issue |\n| Authentication Recipes | [COMMON-CLI.md](..\u002F..\u002Fcommon\u002FCOMMON-CLI.md#authentication-recipes) | `az login` flows and token acquisition |\n| Core Control-Plane REST APIs | [COMMON-CORE.md](..\u002F..\u002Fcommon\u002FCOMMON-CORE.md#core-control-plane-rest-apis) | Pagination, LRO polling, rate limiting |\n| Gotchas & Troubleshooting | [COMMON-CLI.md](..\u002F..\u002Fcommon\u002FCOMMON-CLI.md#gotchas--troubleshooting-cli-specific) | `az rest` audience, shell escaping, token expiry |\n\n## Rules\n\n### MUST\n\n- Select exactly one mode from the table above before doing anything else.\n- Read `references\u002F\u003Cmode>.md` end to end, as your FIRST tool call, before the first command of that mode. Read it ONCE, in a single full read: do not re-open it, do not grep it again, and do not page through it. You already have it.\n- Apply the same read-once discipline to every other file you load, including shared `common\u002F*.md` files: open only the ones you actually need, read each ONCE end to end, and never grep or re-open one you already loaded.\n- Resolve workspace and item ids by listing and filtering, never by guessing a GUID.\n- Announce a mode switch explicitly when the request crosses a boundary.\n- Confirm destructive and overwrite actions before executing -- Delete is permanent (with `?hardDelete=true`) and UpdateDefinition **replaces** the whole definition. When the request already names the target item AND the destructive\u002Foverwrite action explicitly (e.g. \"delete the Event Schema Set X\", \"override X's definition to ...\"), that instruction IS the confirmation: echo the resolved `displayName` + `id` for the audit trail, then proceed with the single write. Pause for a separate yes\u002Fno confirmation ONLY when the target or intent is ambiguous (e.g. \"clean up my workspace\", an unqualified \"the first one\", or a bulk\u002Fwildcard delete).\n- Treat the reference as instructions, never as the deliverable. After reading it, RUN the documented commands against the live workspace and report the real results.\n\n### PREFER\n\n- The narrowest mode that satisfies the request.\n- Reading exactly ONE mode reference. Load a second only when the request genuinely spans modes, and say so before you do.\n- A delegated user identity (`az login`); fall back from SP\u002FMI to a user on 401\u002F403.\n- Reporting the mode you chose in your first response so the user can correct you.\n\n### AVOID\n\n- Acting from this dispatcher alone -- it intentionally omits the operational detail.\n- Answering with a summary of the reference instead of executing it.\n- Re-reading or re-grepping a reference you already loaded; it costs turns and tokens.\n- Mutating anything while in the read-only consumption mode.\n- Confusing EventSchemaSet with Eventstream or Eventhouse (see CRITICAL NOTES 3).\n\n## Examples\n\n| User request | Mode | Reference to read |\n|---|---|---|\n| \"List all Event Schema Sets in my Analytics workspace.\" | `consumption` | [references\u002Fconsumption.md](references\u002Fconsumption.md) |\n| \"Create an Event Schema Set called orders-catalog in Analytics.\" | `authoring` | [references\u002Fauthoring.md](references\u002Fauthoring.md) |\n| \"Decode the definition of orders-catalog and tell me its event types and schemas.\" | `consumption` | [references\u002Fconsumption.md](references\u002Fconsumption.md) |\n| \"Add a BusinessEventType event OrderPlaced (JSON) to orders-catalog.\" | `authoring` | [references\u002Fauthoring.md](references\u002Fauthoring.md) |\n| \"Delete the orders-catalog-old Event Schema Set from Analytics.\" | `authoring` | [references\u002Fauthoring.md](references\u002Fauthoring.md) |\n",{"name":5,"description":7},"main","4c3986d2e5b498ce2d6e6025533b94b5e5bb2ccd","skills\u002Feventschemaset-cli",393,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-06 03:33:28",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add microsoft\u002Fskills-for-fabric --skill eventschemaset-cli",{"tool":41,"command":42},"bunx","bunx skills add microsoft\u002Fskills-for-fabric --skill eventschemaset-cli",{"tool":44,"command":45},"pnpm","pnpm dlx skills add microsoft\u002Fskills-for-fabric --skill eventschemaset-cli","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fskills\u002Feventschemaset-cli\u002FSKILL.md",true,[49,55,59],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"apm.yml","REFERENCE","参考文档",328,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fskills\u002Feventschemaset-cli\u002Fapm.yml",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fauthoring.md",21187,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fskills\u002Feventschemaset-cli\u002Freferences\u002Fauthoring.md",{"path":60,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fconsumption.md",20544,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fskills\u002Feventschemaset-cli\u002Freferences\u002Fconsumption.md",[64,89,118,123,129,137],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":21},"01M6PHZNVB6K7DCCJH4YZHKC4F","ontology-cli","Manages Microsoft Fabric Ontology items: authors legacy V1 entity\u002Frelationship definitions and answers questions for new-experience (V2) Ontologies through ask_ontology. Use for Ontology item operations or grounded questions; V2 authoring\u002Fupgrades and V1 queries are unsupported. Power BI data questions use fabriciq, report authoring powerbi-report-cli, and model\u002FDAX changes semantic-model-authoring.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fskills\u002Fontology-cli\u002FSKILL.md",[],[71,72,19,73,74,75,76,77,78,79,80,81,9,82,83,84,85,86,87,88],"ontology cli","ontology","use","changes","for","v1","bi","relationship","queries","Legacy","power","operations","upgrades","ask","model","power bi","microsoft fabric","fabriciq",{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":100,"publishedAt":21},"01M6PHZ91CSTP67DM6JN8TYEFV","databasehub-cli","Analyzes Database Hub inventory, health, and security posture through Entra-authenticated Fabric APIs. Use for estate counts; SQL\u002FPostgreSQL CPU, storage, and memory; Cosmos DB availability\u002FRU; authentication\u002Fauditing\u002FCMK warnings; and Fabric SQL inventory. Fabric SQL tuning routes to sqldb-cli; Warehouse\u002FLakehouse\u002FMirrored Database SQL to sqldw-cli. Triggers: data estate performance, database estate health, database security posture.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fskills\u002Fdatabasehub-cli\u002FSKILL.md",[95],{"categoryNo":96,"categoryName":97,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",[101,19,102,103,75,104,105,106,107,108,109,110,111,112,73,113,114,115,116,117],"databasehub cli","triggers","authentication","warehouse","database security","availability","CPU","cosmos","database sql","postgresql","db","security posture","health","database","inventory","performance","memory",{"skillNo":119,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":21},"01M6PHYVDVBD0VQN4FFAMN428Z","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fplugins\u002Ffabric-skills\u002Fskills\u002Fontology-cli\u002FSKILL.md",[],[71,72,19,87,88,9,86,74,75,76,77,78,79,80,81,73,82,83,84,85],{"skillNo":124,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":128,"publishedAt":21},"01M6PHYDZ17VY69E3GS71KFW09","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fplugins\u002Ffabric-skills\u002Fskills\u002Fdatabasehub-cli\u002FSKILL.md",[127],{"categoryNo":96,"categoryName":97,"taxonomyType":98,"taxonomyTypeDesc":99},[19,101,117,107,114,75,104,105,106,108,109,102,111,112,73,113,115,103,116,110],{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":21},"01M699SMYSV15Z37ZCCX9EMP85","variable-library-cli","Manages Fabric Variable Library items, including definitions, libraryVariables and valueSets overrides. Covers which consumers can reference a variable and with what syntax -- pipelines, notebooks via notebookutils variableLibrary, Dataflow Gen2, Copy Jobs, shortcuts, UDFs and Plan items -- the active value set per workspace or deployment stage, and Git serialization for CI\u002FCD.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fskills\u002Fvariable-library-cli\u002FSKILL.md",[],[19,136],"variable library cli",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":148,"publishedAt":21},"01M699SGQ4VSWBR73HQKX1YH3Y","synapse-migration","Converts Synapse workspaces to Fabric: Spark items, Lake Databases, Linked Services, and Dedicated SQL Pool schema\u002Fprocedures for Lakehouse or Warehouse. During Pool-to-Lakehouse migration only, can migrate approved dependent procedure callers after notebook readiness. Excludes standalone pipelines and Warehouse administration. Triggers: Synapse workspace to Fabric, Dedicated SQL Pool to Lakehouse, Dedicated SQL Pool to Fabric Warehouse.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fskills\u002Fsynapse-migration\u002FSKILL.md",[143],{"categoryNo":144,"categoryName":145,"taxonomyType":146,"taxonomyTypeDesc":147},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[149],"synapse migration"]