[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PHZ91CSTP67DM6JN8TYEFV":3,"skill-same:01M6PHZ91CSTP67DM6JN8TYEFV":94},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M6PHZ91CSTP67DM6JN8TYEFV","databasehub-cli",null,"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.","microsoft\u002Fskills-for-fabric","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M699NAPJKS2WBHHDN86Q5MM6",1346,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fskills\u002Fdatabasehub-cli\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"databasehub cli","cli","security posture","for","warehouse","database security","availability","CPU","cosmos","database sql","triggers","db","use","health","inventory","postgresql","database","authentication","performance","memory","2026-11-10 10:12:30",false,"---\nname: databasehub-cli\ndescription: \"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.\"\n---\n\n> **Telemetry — MANDATORY.** Every `api.fabric.microsoft.com` call must carry\n> `x-ms-fabric-skill: databasehub-cli` (`az rest`: `--headers \"x-ms-fabric-skill=databasehub-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. Database Hub estate routes are tenant-scoped and usually need neither a workspace nor an item ID. Apply notes 1-2 only when resolving a Fabric SQL catalog item or handing off to an item-specific skill.\n\n# Database Hub CLI\n\nRead-only analysis of the database estate exposed through Database Hub. This\nskill executes live API calls; it does not answer estate questions from generic\nbest practices or from files in the current directory.\n\n## Prerequisite knowledge\n\n- [Private-over-public API contract](references\u002Fprivate-over-public-api.md) —\n  required authentication, transport, pagination, partial-result, error, and\n  route-safety rules.\n- [Health drill-downs and filtered snapshots](references\u002Fhealth-drilldowns.md)\n  — required for named SQL\u002FPostgreSQL resources, per-resource SQL metrics, and\n  filtered health comparisons.\n- [Fabric authentication and CLI patterns](..\u002F..\u002Fcommon\u002FCOMMON-CLI.md)\n- [Fabric REST API concepts](..\u002F..\u002Fcommon\u002FCOMMON-CORE.md)\n- [Databases in Fabric documentation](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Ffabric\u002Fdatabase\u002F)\n\n## Select one mode\n\n| Mode | Use when the request asks for | Read next |\n| --- | --- | --- |\n| `consumption` | estate counts, subscriptions, resource hierarchy, mixed or engine-specific inventory, saved-view membership, or Fabric SQL catalog entries | [references\u002Fconsumption.md](references\u002Fconsumption.md) |\n| `operations` | cross-engine performance, CPU\u002Fstorage\u002Fmemory, Cosmos DB availability\u002FRU use, critical or monitored resources, issues\u002Fsuggestions, or authentication\u002Fauditing\u002FCMK posture | [references\u002Foperations.md](references\u002Foperations.md) |\n\nFor a request spanning both modes, establish inventory scope first, then run\noperations against that scope. Read each reference before issuing its calls.\n\n## Scope and routing boundaries\n\n| Request | Route to |\n| --- | --- |\n| Cross-engine estate inventory, health, findings, or security posture | `databasehub-cli` |\n| Query Store, DMVs, blocking, plans, indexes, T-SQL, or tuning for one Fabric SQL Database | `sqldb-cli` |\n| Warehouse, Lakehouse SQL endpoint, or Mirrored Database SQL queries and `queryinsights` | `sqldw-cli` |\n| OneLake domains, labels, workspace\u002Fcapacity governance, descriptions, endorsement, or tags | `onelake-catalog-cli` |\n| Fabric workspace item search by name, description, workspace, or type | `search-consumption-cli` |\n| Eventhouse or KQL Database queries | `eventhouse-cli` |\n| Azure Monitor mirrored-catalog onboarding and business-impact correlation | `azmon-mirroredcatalogs-operations-cli` |\n\nFabric SQL support here is **catalog inventory only**. Do not claim Database Hub\nhealth or posture coverage for Fabric SQL items. Do not substitute a\nsingle-database diagnostic skill for a cross-engine estate request.\n\n## Execution contract\n\n1. Confirm the active Entra identity and requested scope. Portal-provided\n   subscriptions, resource filters, or time range are query hints, never\n   authorization.\n2. Before the first Database Hub call, read\n   [references\u002Fprivate-over-public-api.md](references\u002Fprivate-over-public-api.md)\n   and the selected mode reference. For named-resource or filtered health\n   drill-downs, read [references\u002Fhealth-drilldowns.md](references\u002Fhealth-drilldowns.md)\n   in addition to `operations.md`, not instead of it.\n3. Run the documented live calls through `https:\u002F\u002Fapi.fabric.microsoft.com`.\n4. Follow every continuation token needed for the requested scope.\n5. Report timeframe, aggregation, engine coverage, pagination completeness,\n   `coverage`, and sanitized `errors`.\n6. For prompts containing \"all\", \"across\", or \"estate\", complete every required\n   summary\u002Fposture call in the selected workflow before answering. Attempt\n   independent required calls even when another route fails; collect each\n   route's error instead of short-circuiting the workflow. Only a page that\n   depends on a failed prior page\u002Ftoken may be skipped. Do not defer required\n   calls as an optional follow-up.\n7. If a route or permission is unavailable, state the exact missing coverage;\n   never invent data, switch to a workload host, or query ADX directly.\n\n## Must \u002F Prefer \u002F Avoid\n\n### MUST\n\n- Remain read-only. Decline create, deploy, enable, disable, update, delete, or\n  remediation requests and route them to the owning product flow or skill.\n- Use a delegated Entra user token for the Fabric API and include\n  `x-ms-fabric-skill: databasehub-cli` on every request.\n- Emit SQL and PostgreSQL health summaries only through the compact\n  `Select-Object` projection in `operations.md`; never print raw summaries\n  with their `series` arrays. A populated estate's raw summaries exceed the\n  tool-output limit, and answering from partial file reads misattributes\n  metrics.\n- For general cross-engine health\u002Fperformance that includes Cosmos\n  availability or RU, query Microsoft SQL, PostgreSQL, and Cosmos DB\n  separately; preserve their different metric contracts in the answer. For a\n  CPU-only request, query SQL and PostgreSQL and state that Cosmos CPU is not\n  exposed by this contract.\n- For general cross-engine health\u002Fperformance requests that include Cosmos\n  availability\u002FRU, and for all-findings requests, page Cosmos health with the\n  filtered POST form until `continuationToken` is absent. A first-page Cosmos\n  result is incomplete. Do not call Cosmos health for inventory-only or\n  CPU-only requests.\n- In every Cosmos health answer, label `processedAccounts` and `totalAccounts`\n  separately even when they are equal; do not compress them into one unlabeled\n  account count. When they differ, literally label coverage `partial` or\n  `inconsistent`. When `totalAccounts` is `0`, report `totalAccounts: 0`, say\n  there are no Cosmos DB accounts in scope and therefore no availability or\n  normalized RU data, and do not call Cosmos healthy.\n- For CPU-only requests, report CPU evidence only. Do not add storage or memory\n  counts merely because the summary response also contains them.\n- Treat HTTP 200 with non-empty `errors`, incomplete `coverage`, or remaining\n  continuation tokens as partial, not complete success.\n- Label posture denominators exactly: authentication counts cover Azure SQL\n  databases plus Arc SQL Server, while auditing and CMK counts cover Azure SQL\n  databases only. Repeat the literal scope on each posture line: \"Azure SQL +\n  Arc SQL Server\" for authentication and \"Azure SQL only\" for both auditing and\n  CMK.\n- For \"all issues and suggestions\" output, report both `totalFindingCount` and\n  `totalAffectedResourceCount` for every returned database family. Do not\n  substitute affected-resource counts for finding totals.\n- State that Cosmos DB exposes availability and normalized RU consumption here,\n  not CPU, memory, storage, latency, or throttled-request diagnostics.\n- State normalized RU saturation and explicitly say it does **not** prove\n  throttled requests because this contract exposes no throttling metric. Do not\n  rephrase saturation as a confirmed, likely, or potential throttling risk.\n\n### PREFER\n\n- Start with summary\u002Fcount routes, then drill into only the affected population.\n- Use server-provided finding summaries and high\u002Flow usage classifications\n  instead of inventing thresholds.\n- Project compact typed summaries from API responses. Do not dump full metric\n  series or finding `targetSummaries` unless the user asks for them; oversized\n  tool output is harder to ground reliably.\n- Group results by database family and priority, with affected counts and named\n  examples only when the user asks for detail.\n- Reuse an immutable filter snapshot across pages and related filtered calls.\n\n### AVOID\n\n- Direct calls to ADX, Kusto, `arcdataservices.com`, workload regional hosts, or\n  any MWC-token flow.\n- Agent-authored KQL, schema discovery, or arbitrary telemetry queries.\n- Claiming IO support; the current health contract exposes CPU, storage, and\n  memory for Microsoft SQL\u002FPostgreSQL.\n- Inferring throttled requests or throttling from normalized RU consumption\n  alone. This contract reports RU saturation, not throttling events.\n- Treating an empty response as healthy when authorization, coverage, paging,\n  or partial errors are unresolved.\n\n## Examples\n\n```text\nUser: Are there any performance issues I should know about in my data estate?\nMode: operations\nAction: Query all three health families, report performance findings and partial coverage, then drill into high-usage SQL\u002FPostgreSQL resources when needed.\n```\n\n```text\nUser: What should I fix first to improve security across my databases?\nMode: operations\nAction: Compare security issues with authentication, auditing, and CMK posture; prioritize affected resources without changing them.\n```\n\n```text\nUser: Show my database estate by engine and subscription.\nMode: consumption\nAction: Read counts, page the requested inventory, and group returned resources by type and subscription.\n```\n\n```text\nUser: How is my CPU consumption looking across my databases recently?\nMode: operations\nAction: Query Microsoft SQL and PostgreSQL CPU coverage and explicitly note that this Database Hub Cosmos contract has no CPU metric.\n```\n\n```text\nUser: Give me a breakdown of all issues and suggestions across my data estate.\nMode: operations\nAction: Combine health finding summaries with security issue\u002Fsuggestion summaries and list affected resources through read-only drill-down routes.\n```\n","> **Telemetry — MANDATORY.** Every `api.fabric.microsoft.com` call must carry\n> `x-ms-fabric-skill: databasehub-cli` (`az rest`: `--headers \"x-ms-fabric-skill=databasehub-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. Database Hub estate routes are tenant-scoped and usually need neither a workspace nor an item ID. Apply notes 1-2 only when resolving a Fabric SQL catalog item or handing off to an item-specific skill.\n\n# Database Hub CLI\n\nRead-only analysis of the database estate exposed through Database Hub. This\nskill executes live API calls; it does not answer estate questions from generic\nbest practices or from files in the current directory.\n\n## Prerequisite knowledge\n\n- [Private-over-public API contract](references\u002Fprivate-over-public-api.md) —\n  required authentication, transport, pagination, partial-result, error, and\n  route-safety rules.\n- [Health drill-downs and filtered snapshots](references\u002Fhealth-drilldowns.md)\n  — required for named SQL\u002FPostgreSQL resources, per-resource SQL metrics, and\n  filtered health comparisons.\n- [Fabric authentication and CLI patterns](..\u002F..\u002Fcommon\u002FCOMMON-CLI.md)\n- [Fabric REST API concepts](..\u002F..\u002Fcommon\u002FCOMMON-CORE.md)\n- [Databases in Fabric documentation](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Ffabric\u002Fdatabase\u002F)\n\n## Select one mode\n\n| Mode | Use when the request asks for | Read next |\n| --- | --- | --- |\n| `consumption` | estate counts, subscriptions, resource hierarchy, mixed or engine-specific inventory, saved-view membership, or Fabric SQL catalog entries | [references\u002Fconsumption.md](references\u002Fconsumption.md) |\n| `operations` | cross-engine performance, CPU\u002Fstorage\u002Fmemory, Cosmos DB availability\u002FRU use, critical or monitored resources, issues\u002Fsuggestions, or authentication\u002Fauditing\u002FCMK posture | [references\u002Foperations.md](references\u002Foperations.md) |\n\nFor a request spanning both modes, establish inventory scope first, then run\noperations against that scope. Read each reference before issuing its calls.\n\n## Scope and routing boundaries\n\n| Request | Route to |\n| --- | --- |\n| Cross-engine estate inventory, health, findings, or security posture | `databasehub-cli` |\n| Query Store, DMVs, blocking, plans, indexes, T-SQL, or tuning for one Fabric SQL Database | `sqldb-cli` |\n| Warehouse, Lakehouse SQL endpoint, or Mirrored Database SQL queries and `queryinsights` | `sqldw-cli` |\n| OneLake domains, labels, workspace\u002Fcapacity governance, descriptions, endorsement, or tags | `onelake-catalog-cli` |\n| Fabric workspace item search by name, description, workspace, or type | `search-consumption-cli` |\n| Eventhouse or KQL Database queries | `eventhouse-cli` |\n| Azure Monitor mirrored-catalog onboarding and business-impact correlation | `azmon-mirroredcatalogs-operations-cli` |\n\nFabric SQL support here is **catalog inventory only**. Do not claim Database Hub\nhealth or posture coverage for Fabric SQL items. Do not substitute a\nsingle-database diagnostic skill for a cross-engine estate request.\n\n## Execution contract\n\n1. Confirm the active Entra identity and requested scope. Portal-provided\n   subscriptions, resource filters, or time range are query hints, never\n   authorization.\n2. Before the first Database Hub call, read\n   [references\u002Fprivate-over-public-api.md](references\u002Fprivate-over-public-api.md)\n   and the selected mode reference. For named-resource or filtered health\n   drill-downs, read [references\u002Fhealth-drilldowns.md](references\u002Fhealth-drilldowns.md)\n   in addition to `operations.md`, not instead of it.\n3. Run the documented live calls through `https:\u002F\u002Fapi.fabric.microsoft.com`.\n4. Follow every continuation token needed for the requested scope.\n5. Report timeframe, aggregation, engine coverage, pagination completeness,\n   `coverage`, and sanitized `errors`.\n6. For prompts containing \"all\", \"across\", or \"estate\", complete every required\n   summary\u002Fposture call in the selected workflow before answering. Attempt\n   independent required calls even when another route fails; collect each\n   route's error instead of short-circuiting the workflow. Only a page that\n   depends on a failed prior page\u002Ftoken may be skipped. Do not defer required\n   calls as an optional follow-up.\n7. If a route or permission is unavailable, state the exact missing coverage;\n   never invent data, switch to a workload host, or query ADX directly.\n\n## Must \u002F Prefer \u002F Avoid\n\n### MUST\n\n- Remain read-only. Decline create, deploy, enable, disable, update, delete, or\n  remediation requests and route them to the owning product flow or skill.\n- Use a delegated Entra user token for the Fabric API and include\n  `x-ms-fabric-skill: databasehub-cli` on every request.\n- Emit SQL and PostgreSQL health summaries only through the compact\n  `Select-Object` projection in `operations.md`; never print raw summaries\n  with their `series` arrays. A populated estate's raw summaries exceed the\n  tool-output limit, and answering from partial file reads misattributes\n  metrics.\n- For general cross-engine health\u002Fperformance that includes Cosmos\n  availability or RU, query Microsoft SQL, PostgreSQL, and Cosmos DB\n  separately; preserve their different metric contracts in the answer. For a\n  CPU-only request, query SQL and PostgreSQL and state that Cosmos CPU is not\n  exposed by this contract.\n- For general cross-engine health\u002Fperformance requests that include Cosmos\n  availability\u002FRU, and for all-findings requests, page Cosmos health with the\n  filtered POST form until `continuationToken` is absent. A first-page Cosmos\n  result is incomplete. Do not call Cosmos health for inventory-only or\n  CPU-only requests.\n- In every Cosmos health answer, label `processedAccounts` and `totalAccounts`\n  separately even when they are equal; do not compress them into one unlabeled\n  account count. When they differ, literally label coverage `partial` or\n  `inconsistent`. When `totalAccounts` is `0`, report `totalAccounts: 0`, say\n  there are no Cosmos DB accounts in scope and therefore no availability or\n  normalized RU data, and do not call Cosmos healthy.\n- For CPU-only requests, report CPU evidence only. Do not add storage or memory\n  counts merely because the summary response also contains them.\n- Treat HTTP 200 with non-empty `errors`, incomplete `coverage`, or remaining\n  continuation tokens as partial, not complete success.\n- Label posture denominators exactly: authentication counts cover Azure SQL\n  databases plus Arc SQL Server, while auditing and CMK counts cover Azure SQL\n  databases only. Repeat the literal scope on each posture line: \"Azure SQL +\n  Arc SQL Server\" for authentication and \"Azure SQL only\" for both auditing and\n  CMK.\n- For \"all issues and suggestions\" output, report both `totalFindingCount` and\n  `totalAffectedResourceCount` for every returned database family. Do not\n  substitute affected-resource counts for finding totals.\n- State that Cosmos DB exposes availability and normalized RU consumption here,\n  not CPU, memory, storage, latency, or throttled-request diagnostics.\n- State normalized RU saturation and explicitly say it does **not** prove\n  throttled requests because this contract exposes no throttling metric. Do not\n  rephrase saturation as a confirmed, likely, or potential throttling risk.\n\n### PREFER\n\n- Start with summary\u002Fcount routes, then drill into only the affected population.\n- Use server-provided finding summaries and high\u002Flow usage classifications\n  instead of inventing thresholds.\n- Project compact typed summaries from API responses. Do not dump full metric\n  series or finding `targetSummaries` unless the user asks for them; oversized\n  tool output is harder to ground reliably.\n- Group results by database family and priority, with affected counts and named\n  examples only when the user asks for detail.\n- Reuse an immutable filter snapshot across pages and related filtered calls.\n\n### AVOID\n\n- Direct calls to ADX, Kusto, `arcdataservices.com`, workload regional hosts, or\n  any MWC-token flow.\n- Agent-authored KQL, schema discovery, or arbitrary telemetry queries.\n- Claiming IO support; the current health contract exposes CPU, storage, and\n  memory for Microsoft SQL\u002FPostgreSQL.\n- Inferring throttled requests or throttling from normalized RU consumption\n  alone. This contract reports RU saturation, not throttling events.\n- Treating an empty response as healthy when authorization, coverage, paging,\n  or partial errors are unresolved.\n\n## Examples\n\n```text\nUser: Are there any performance issues I should know about in my data estate?\nMode: operations\nAction: Query all three health families, report performance findings and partial coverage, then drill into high-usage SQL\u002FPostgreSQL resources when needed.\n```\n\n```text\nUser: What should I fix first to improve security across my databases?\nMode: operations\nAction: Compare security issues with authentication, auditing, and CMK posture; prioritize affected resources without changing them.\n```\n\n```text\nUser: Show my database estate by engine and subscription.\nMode: consumption\nAction: Read counts, page the requested inventory, and group returned resources by type and subscription.\n```\n\n```text\nUser: How is my CPU consumption looking across my databases recently?\nMode: operations\nAction: Query Microsoft SQL and PostgreSQL CPU coverage and explicitly note that this Database Hub Cosmos contract has no CPU metric.\n```\n\n```text\nUser: Give me a breakdown of all issues and suggestions across my data estate.\nMode: operations\nAction: Combine health finding summaries with security issue\u002Fsuggestion summaries and list affected resources through read-only drill-down routes.\n```\n",{"name":5,"description":7},"main","f8fac110ac3b93e9d1f7b0bd8feac5c6a468ce43","skills\u002Fdatabasehub-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-12 20:10:24",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add microsoft\u002Fskills-for-fabric --skill databasehub-cli",{"tool":64,"command":65},"bunx","bunx skills add microsoft\u002Fskills-for-fabric --skill databasehub-cli",{"tool":67,"command":68},"pnpm","pnpm dlx skills add microsoft\u002Fskills-for-fabric --skill databasehub-cli","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fskills\u002Fdatabasehub-cli\u002FSKILL.md",true,[72,78,82,86,90],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"apm.yml","REFERENCE","参考文档",332,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fskills\u002Fdatabasehub-cli\u002Fapm.yml",{"path":79,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fconsumption.md",8773,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fskills\u002Fdatabasehub-cli\u002Freferences\u002Fconsumption.md",{"path":83,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fhealth-drilldowns.md",6001,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fskills\u002Fdatabasehub-cli\u002Freferences\u002Fhealth-drilldowns.md",{"path":87,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Foperations.md",17245,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fskills\u002Fdatabasehub-cli\u002Freferences\u002Foperations.md",{"path":91,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fprivate-over-public-api.md",7040,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fskills\u002Fdatabasehub-cli\u002Freferences\u002Fprivate-over-public-api.md",[95,118,123,129,137,150],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":44},"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",[],[102,25,103,9,104,105,106,107,108,109,110,36,111,112,113,114,115,116,27,117],"ontology cli","ontology","fabriciq","microsoft fabric","power bi","model","ask","upgrades","operations","power","Legacy","queries","relationship","bi","v1","changes",{"skillNo":119,"name":97,"nameZh":6,"description":98,"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":44},"01M6PHYVDVBD0VQN4FFAMN428Z","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fplugins\u002Ffabric-skills\u002Fskills\u002Fontology-cli\u002FSKILL.md",[],[102,25,103,114,113,115,116,27,117,108,112,111,9,104,105,106,107,109,110,36],{"skillNo":124,"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":125,"categories":126,"keywords":128,"publishedAt":44},"01M6PHYDZ17VY69E3GS71KFW09","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fplugins\u002Ffabric-skills\u002Fskills\u002Fdatabasehub-cli\u002FSKILL.md",[127],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[24,25,33,43,42,41,40,39,38,37,36,26,35,34,32,31,30,29,28,27],{"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":44},"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",[],[136,25],"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":44},"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",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":157,"publishedAt":44},"01M699SDYKTDE0BT9AGDHEJ4HP","sqldw-cli","Manage Fabric Warehouse, Lakehouse SQL endpoints, and Mirrored Databases: DDL\u002FDML, COPY INTO, read-only T-SQL, Query Insights diagnostics, and Capacity Metrics CU-spike correlation. Synapse migration target SQL belongs to synapse-migration; Fabric SQL database belongs to sqldb-cli. Triggers: query warehouse, create warehouse table, failed or canceled query, CU spike, Capacity Metrics app, custom SQL pool, Lakehouse table health.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fskills\u002Fsqldw-cli\u002FSKILL.md",[156],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[25,158,159,160,149],"sqldw cli","spike","capacity"]