[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699R8GCA2SF2Y04G5WX49R3":3,"skill-same:01M699R8GCA2SF2Y04G5WX49R3":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},"01M699R8GCA2SF2Y04G5WX49R3","eventstream-cli",null,"Owns Fabric Eventstream items end to end: sources, operators, destinations, routing, retention, throughput and connection strings, plus read-only topology checks. Pick it for anything that names an Eventstream, creating and listing included. Where the rows finally land is eventhouse-cli.","microsoft\u002Fskills-for-fabric","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M699NAPJKS2WBHHDN86Q5MM6",1353,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fskills\u002Feventstream-cli\u002FSKILL.md",[],[19,20],"cli","eventstream cli","2026-11-10 10:12:30",false,"---\nname: eventstream-cli\ndescription: \"Owns Fabric Eventstream items end to end: sources, operators, destinations, routing, retention, throughput and connection strings, plus read-only topology checks. Pick it for anything that names an Eventstream, creating and listing included. Where the rows finally land is eventhouse-cli.\"\n---\n\n> **Telemetry — MANDATORY.** Every `api.fabric.microsoft.com` call must carry\n> `x-ms-fabric-skill: eventstream-cli` (`az rest`: `--headers \"x-ms-fabric-skill=eventstream-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 `eventstream-cli` for the Eventstream item itself -- how events flow from source through operators to destinations. Querying or shaping the data once it lands in an Eventhouse \u002F KQL Database uses the matching `eventhouse-cli` mode; alerting uses the matching Activator authoring or consumption skill.\n\n# Fabric Eventstream -- CLI Skill\n\nThis one skill owns Fabric Eventstream real-time ingestion topologies: sources, operators, destinations, routing, retention and health.\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, updates, wires, pauses, resumes or deletes an Eventstream topology | create eventstream, deploy topology, add source, add filter operator, wire destination, update definition | [references\u002Fauthoring.md](references\u002Fauthoring.md) |\n| `consumption` | lists or inspects Eventstreams, topology, retention, throughput, node health or Custom Endpoint connection metadata | list eventstreams, inspect topology, eventstream status, retention, throughput, connection string | [references\u002Fconsumption.md](references\u002Fconsumption.md) |\n\n### Mode boundary rule\n\n`consumption` is read-only for Eventstream definitions and topology. A request to create, update, delete, pause or resume an Eventstream requires `authoring`: say so, read `references\u002Fauthoring.md`, then proceed.\n\nBefore an authoring mutation, establish the source, destination, transformation, retention and throughput requirements that apply. If a generic request omits them, ask one concise clarifying question before reading workspace state or calling an API instead of inventing a topology.\n\nIf a request genuinely spans modes, 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 topology is NOT completing the task. Each mutating 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` | `POST \u002Fv1\u002Fworkspaces\u002F{ws}\u002Fitems` or `\u002Feventstreams` to create, `POST ...\u002FupdateDefinition` to persist topology changes, bodyless `POST ...\u002Fpause` or `POST ...\u002Fresume` with a required JSON `startType` body for lifecycle control, or `DELETE ...\u002Feventstreams\u002F{id}` to remove the item. Building or base64-encoding `eventstream.json` is not the write. |\n| `consumption` | none -- this mode is read-only |\n\nBefore you report an authoring task done, confirm the terminal call returned success and read the definition or runtime topology back when the reference documents a verification step.\n\n## Shared essentials (all modes)\n\nResolve the workspace and Eventstream 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.\n- Resolve workspace and Eventstream ids by listing and filtering, never by guessing a GUID.\n- Announce a mode switch explicitly when the request crosses a boundary.\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- Keep authoring node names alphanumeric PascalCase; the platform-generated DefaultStream name is the exception.\n- Get explicit user confirmation before retrieving Custom Endpoint credentials, and never print raw keys or connection strings unless the user explicitly requests them in a secure context.\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- Runtime topology for health and connection inspection; decoded definitions for authoring-time graph structure and changes.\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- Mutating anything while in the read-only consumption mode.\n- Querying landed event data through Eventstream APIs; use `eventhouse-cli` consumption mode for read-only KQL data.\n- Loading a different skill for work this skill already owns (see CRITICAL NOTES 3).\n\n## Examples\n\n| User request | Mode | Reference to read |\n|---|---|---|\n| \"Create an Eventstream with a SampleData source and a Lakehouse destination.\" | `authoring` | [references\u002Fauthoring.md](references\u002Fauthoring.md) |\n| \"Add a filter for temperature above 30 to my Eventstream.\" | `authoring` | [references\u002Fauthoring.md](references\u002Fauthoring.md) |\n| \"Show every source, operator and destination in SensorIngestion.\" | `consumption` | [references\u002Fconsumption.md](references\u002Fconsumption.md) |\n| \"What retention and throughput settings does this Eventstream use?\" | `consumption` | [references\u002Fconsumption.md](references\u002Fconsumption.md) |\n","> **Telemetry — MANDATORY.** Every `api.fabric.microsoft.com` call must carry\n> `x-ms-fabric-skill: eventstream-cli` (`az rest`: `--headers \"x-ms-fabric-skill=eventstream-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 `eventstream-cli` for the Eventstream item itself -- how events flow from source through operators to destinations. Querying or shaping the data once it lands in an Eventhouse \u002F KQL Database uses the matching `eventhouse-cli` mode; alerting uses the matching Activator authoring or consumption skill.\n\n# Fabric Eventstream -- CLI Skill\n\nThis one skill owns Fabric Eventstream real-time ingestion topologies: sources, operators, destinations, routing, retention and health.\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, updates, wires, pauses, resumes or deletes an Eventstream topology | create eventstream, deploy topology, add source, add filter operator, wire destination, update definition | [references\u002Fauthoring.md](references\u002Fauthoring.md) |\n| `consumption` | lists or inspects Eventstreams, topology, retention, throughput, node health or Custom Endpoint connection metadata | list eventstreams, inspect topology, eventstream status, retention, throughput, connection string | [references\u002Fconsumption.md](references\u002Fconsumption.md) |\n\n### Mode boundary rule\n\n`consumption` is read-only for Eventstream definitions and topology. A request to create, update, delete, pause or resume an Eventstream requires `authoring`: say so, read `references\u002Fauthoring.md`, then proceed.\n\nBefore an authoring mutation, establish the source, destination, transformation, retention and throughput requirements that apply. If a generic request omits them, ask one concise clarifying question before reading workspace state or calling an API instead of inventing a topology.\n\nIf a request genuinely spans modes, 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 topology is NOT completing the task. Each mutating 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` | `POST \u002Fv1\u002Fworkspaces\u002F{ws}\u002Fitems` or `\u002Feventstreams` to create, `POST ...\u002FupdateDefinition` to persist topology changes, bodyless `POST ...\u002Fpause` or `POST ...\u002Fresume` with a required JSON `startType` body for lifecycle control, or `DELETE ...\u002Feventstreams\u002F{id}` to remove the item. Building or base64-encoding `eventstream.json` is not the write. |\n| `consumption` | none -- this mode is read-only |\n\nBefore you report an authoring task done, confirm the terminal call returned success and read the definition or runtime topology back when the reference documents a verification step.\n\n## Shared essentials (all modes)\n\nResolve the workspace and Eventstream 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.\n- Resolve workspace and Eventstream ids by listing and filtering, never by guessing a GUID.\n- Announce a mode switch explicitly when the request crosses a boundary.\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- Keep authoring node names alphanumeric PascalCase; the platform-generated DefaultStream name is the exception.\n- Get explicit user confirmation before retrieving Custom Endpoint credentials, and never print raw keys or connection strings unless the user explicitly requests them in a secure context.\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- Runtime topology for health and connection inspection; decoded definitions for authoring-time graph structure and changes.\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- Mutating anything while in the read-only consumption mode.\n- Querying landed event data through Eventstream APIs; use `eventhouse-cli` consumption mode for read-only KQL data.\n- Loading a different skill for work this skill already owns (see CRITICAL NOTES 3).\n\n## Examples\n\n| User request | Mode | Reference to read |\n|---|---|---|\n| \"Create an Eventstream with a SampleData source and a Lakehouse destination.\" | `authoring` | [references\u002Fauthoring.md](references\u002Fauthoring.md) |\n| \"Add a filter for temperature above 30 to my Eventstream.\" | `authoring` | [references\u002Fauthoring.md](references\u002Fauthoring.md) |\n| \"Show every source, operator and destination in SensorIngestion.\" | `consumption` | [references\u002Fconsumption.md](references\u002Fconsumption.md) |\n| \"What retention and throughput settings does this Eventstream use?\" | `consumption` | [references\u002Fconsumption.md](references\u002Fconsumption.md) |\n",{"name":5,"description":7},"main","4c3986d2e5b498ce2d6e6025533b94b5e5bb2ccd","skills\u002Feventstream-cli",395,"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-12 20:10:24",{"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 eventstream-cli",{"tool":41,"command":42},"bunx","bunx skills add microsoft\u002Fskills-for-fabric --skill eventstream-cli",{"tool":44,"command":45},"pnpm","pnpm dlx skills add microsoft\u002Fskills-for-fabric --skill eventstream-cli","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fskills\u002Feventstream-cli\u002FSKILL.md",true,[49,55,59],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"apm.yml","REFERENCE","参考文档",392,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fskills\u002Feventstream-cli\u002Fapm.yml",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fauthoring.md",29923,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fskills\u002Feventstream-cli\u002Freferences\u002Fauthoring.md",{"path":60,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fconsumption.md",25622,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fskills\u002Feventstream-cli\u002Freferences\u002Fconsumption.md",[64,72,77,102,131,136],{"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":71},"01M78JNNY5VN2MZ7TSV040K3FJ","fabric-policies-cli","Author, review and manage Microsoft Fabric governance policies and PolicySet items. Invoke before clarifying underspecified lockdown requests or missing intent, identities or scope. Discover current contracts and roles, map scenarios to rules, and execute one approved API lifecycle. Not catalog audits or KQL policies. Triggers: Fabric policy, PolicySet, governance rule, latest Fabric policies, policy contract review.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fskills\u002Ffabric-policies-cli\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":73,"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":74,"categories":75,"keywords":76,"publishedAt":71},"01M78JNBFP3GAR4MSKEMHY2HDE","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fplugins\u002Ffabric-skills\u002Fskills\u002Ffabric-policies-cli\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"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",[],[19,84,85,86,9,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101],"ontology","ontology cli","ask","operations","bi","microsoft fabric","changes","queries","power bi","relationship","fabriciq","v1","Legacy","use","upgrades","for","model","power",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":113,"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",[108],{"categoryNo":109,"categoryName":110,"taxonomyType":111,"taxonomyTypeDesc":112},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",[19,114,115,116,117,118,119,120,121,99,97,122,123,124,125,126,127,128,129,130],"databasehub cli","database","CPU","database sql","security posture","postgresql","health","database security","triggers","cosmos","authentication","inventory","performance","db","memory","availability","warehouse",{"skillNo":132,"name":79,"nameZh":6,"description":80,"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},"01M6PHYVDVBD0VQN4FFAMN428Z","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fplugins\u002Ffabric-skills\u002Fskills\u002Fontology-cli\u002FSKILL.md",[],[19,84,85,99,100,101,94,98,90,9,87,88,89,91,92,93,86,95,96,97],{"skillNo":137,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":141,"publishedAt":21},"01M6PHYDZ17VY69E3GS71KFW09","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fplugins\u002Ffabric-skills\u002Fskills\u002Fdatabasehub-cli\u002FSKILL.md",[140],{"categoryNo":109,"categoryName":110,"taxonomyType":111,"taxonomyTypeDesc":112},[19,114,130,129,117,127,126,125,116,118,119,120,121,115,97,122,123,128,99,124]]