[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69AGBTGYJ965FWA4ZZPTFRK":3,"skill-same:01M69AGBTGYJ965FWA4ZZPTFRK":90},{"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":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M69AGBTGYJ965FWA4ZZPTFRK","ff-oce-kusto",null,"Use this skill for any Kusto query or telemetry investigation specifically related to Fluid Framework or its partners. Triggers include: writing or running a Kusto query against the Office Fluid database, investigating Fluid Framework telemetry or error rates, querying Office_Fluid_FluidRuntime_* tables, looking up a Fluid session by Session_Id or docId, investigating a Fluid-related error in Loop or Whiteboard telemetry, monitoring an FF bump or partner ring deployment, checking Fluid render reliability or Scriptor errors, or when the user mentions Fluid-specific tables (Office_Fluid_FluidRuntime_*, OwhLoads, HostTracker, Scriptor) or Fluid-specific error types (dataCorruptionError, dataProcessingError, DeltaConnectionFailureToConnect, ICE, ACE). Do NOT trigger for general Kusto questions that are not related to Fluid Framework.","microsoft\u002FFluidFramework","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69AG0BQKNGBJQ5YNG09HXXW",4949,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.agency\u002Fplugins\u002Fff-oce\u002Fskills\u002Fff-oce-kusto\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"ff oce kusto","bump","running","when","for","tables","whiteboard","errors","render","types","error","query","do","writing","up","reliability","loop","monitoring","database","framework","fluid framework","fluid","telemetry","2026-11-10 10:12:30",false,"---\nname: ff-oce-kusto\ndescription: \"Use this skill for any Kusto query or telemetry investigation specifically related to Fluid Framework or its partners. Triggers include: writing or running a Kusto query against the Office Fluid database, investigating Fluid Framework telemetry or error rates, querying Office_Fluid_FluidRuntime_* tables, looking up a Fluid session by Session_Id or docId, investigating a Fluid-related error in Loop or Whiteboard telemetry, monitoring an FF bump or partner ring deployment, checking Fluid render reliability or Scriptor errors, or when the user mentions Fluid-specific tables (Office_Fluid_FluidRuntime_*, OwhLoads, HostTracker, Scriptor) or Fluid-specific error types (dataCorruptionError, dataProcessingError, DeltaConnectionFailureToConnect, ICE, ACE). Do NOT trigger for general Kusto questions that are not related to Fluid Framework.\"\nversion: 1.0.0\n---\n\n# Fluid Framework Kusto Reference\n\nThis skill provides a comprehensive reference for Fluid Framework telemetry investigation in Kusto. Load it whenever a Kusto query needs to be written, interpreted, or run against the Office Fluid database.\n\n> **VPN required.** The Office Fluid Kusto cluster (`https:\u002F\u002Fkusto.aria.microsoft.com`) is only reachable on the Microsoft internal network. If a query fails to connect or returns no results unexpectedly, remind the user to check that their VPN is on before troubleshooting further.\n\n## Cluster & Access\n\n- **Cluster:** `https:\u002F\u002Fkusto.aria.microsoft.com`\n- **Primary database:** `Office Fluid`\n- **Database ID:** `6a8929bcfc6d44e9b13fee392ada9cf0` (use this, not the pretty name, as the `database` parameter in `kusto_query`)\n- **Automation\u002Fstress test database:** `Office Fluid Test`\n- **Database ID:** `742fa5a288b045e5beab1a2b8e445a71` — contains `office_fluid_ffautomation_*` tables used for stress test \u002F pipeline telemetry. **These tables are NOT in the primary \"Office Fluid\" database.**\n- **Retention:** ~28 days\n- **VPN:** Required (Microsoft internal network)\n- **Access requirement:** M365HeartbeatTenantUsers group membership\n\n## Quick Orientation\n\nThe primary tables are:\n- `Office_Fluid_FluidRuntime_Error` — all errors (first stop)\n- `Office_Fluid_FluidRuntime_Performance` — timing events\n- `Office_Fluid_FluidRuntime_Generic` — everything else\n- `union Office_Fluid_FluidRuntime_*` — all three at once\n- `OwhLoads` (stored function) — denominator for ICE\u002FACE error rate queries\n\nKey correlation ID hierarchy: `Session_Id`\u002F`Data_hostCorrelationId` → `Data_pageCorrelationId` → `Data_docId` → `Data_containerId`\n\nKey deployment ring field: `Loop_Audience` (FluidRuntime tables), `Release_AudienceGroup` (OWH\u002FQoS tables)\n\n## Using the Full Reference\n\nBefore writing any non-trivial Kusto query, read the full reference file:\n\n**`references\u002Fkusto-query-reference.md`**\n\nThis reference contains:\n- **Part 1** — All tables, fields, correlation IDs, version fields, stored functions, partner database schemas (OneNote, OWA, Loop FFX, Video, Scriptor, HostTracker, automation)\n- **Part 2** — Query Cookbook with ~20 sections of ready-to-use queries (session lookup, error timecharts, breadth assessment, version correlation, ICE rate calculations, EU global queries, ODSP flight changes, etc.)\n- **Part 3** — Investigation playbook patterns (incoming partner incident, dataCorruptionError triage, ICE error rate, important notes)\n- **Part 4** — Additional query sections: FF bump tracking (5 queries), render reliability, Scriptor errors, Video telemetry (10+ queries), container reconnects \u002F `WhyIsTheContainerStuck()`, stress test automation (`FindBuildErrors`, `DidSummarizerRecover`, `SummarizerView`)\n\n## Key Reminders\n\n- Always use **absolute timestamps** in IcM notes (not `ago()`) so queries remain reproducible\n- Always filter `Data_stack !has '.goskope.com'` and `Data_channelFactoryType !has '.myshn.net'` in corruption queries to exclude known reverse proxies\n- The `hll()` \u002F `dcount_hll(hll_merge(...))` pattern is required for EU-compliant distinct user counts across clusters\n- For EU data, use `macro-expand force_remote = true officefluid_global as X (...) | summarize ...`\n- `Loop_Audience` (FluidRuntime) and `Release_AudienceGroup` (OWH\u002FQoS) are the same concept; filter `== \"Production\"` to exclude dogfood noise\n","# Fluid Framework Kusto Reference\n\nThis skill provides a comprehensive reference for Fluid Framework telemetry investigation in Kusto. Load it whenever a Kusto query needs to be written, interpreted, or run against the Office Fluid database.\n\n> **VPN required.** The Office Fluid Kusto cluster (`https:\u002F\u002Fkusto.aria.microsoft.com`) is only reachable on the Microsoft internal network. If a query fails to connect or returns no results unexpectedly, remind the user to check that their VPN is on before troubleshooting further.\n\n## Cluster & Access\n\n- **Cluster:** `https:\u002F\u002Fkusto.aria.microsoft.com`\n- **Primary database:** `Office Fluid`\n- **Database ID:** `6a8929bcfc6d44e9b13fee392ada9cf0` (use this, not the pretty name, as the `database` parameter in `kusto_query`)\n- **Automation\u002Fstress test database:** `Office Fluid Test`\n- **Database ID:** `742fa5a288b045e5beab1a2b8e445a71` — contains `office_fluid_ffautomation_*` tables used for stress test \u002F pipeline telemetry. **These tables are NOT in the primary \"Office Fluid\" database.**\n- **Retention:** ~28 days\n- **VPN:** Required (Microsoft internal network)\n- **Access requirement:** M365HeartbeatTenantUsers group membership\n\n## Quick Orientation\n\nThe primary tables are:\n- `Office_Fluid_FluidRuntime_Error` — all errors (first stop)\n- `Office_Fluid_FluidRuntime_Performance` — timing events\n- `Office_Fluid_FluidRuntime_Generic` — everything else\n- `union Office_Fluid_FluidRuntime_*` — all three at once\n- `OwhLoads` (stored function) — denominator for ICE\u002FACE error rate queries\n\nKey correlation ID hierarchy: `Session_Id`\u002F`Data_hostCorrelationId` → `Data_pageCorrelationId` → `Data_docId` → `Data_containerId`\n\nKey deployment ring field: `Loop_Audience` (FluidRuntime tables), `Release_AudienceGroup` (OWH\u002FQoS tables)\n\n## Using the Full Reference\n\nBefore writing any non-trivial Kusto query, read the full reference file:\n\n**`references\u002Fkusto-query-reference.md`**\n\nThis reference contains:\n- **Part 1** — All tables, fields, correlation IDs, version fields, stored functions, partner database schemas (OneNote, OWA, Loop FFX, Video, Scriptor, HostTracker, automation)\n- **Part 2** — Query Cookbook with ~20 sections of ready-to-use queries (session lookup, error timecharts, breadth assessment, version correlation, ICE rate calculations, EU global queries, ODSP flight changes, etc.)\n- **Part 3** — Investigation playbook patterns (incoming partner incident, dataCorruptionError triage, ICE error rate, important notes)\n- **Part 4** — Additional query sections: FF bump tracking (5 queries), render reliability, Scriptor errors, Video telemetry (10+ queries), container reconnects \u002F `WhyIsTheContainerStuck()`, stress test automation (`FindBuildErrors`, `DidSummarizerRecover`, `SummarizerView`)\n\n## Key Reminders\n\n- Always use **absolute timestamps** in IcM notes (not `ago()`) so queries remain reproducible\n- Always filter `Data_stack !has '.goskope.com'` and `Data_channelFactoryType !has '.myshn.net'` in corruption queries to exclude known reverse proxies\n- The `hll()` \u002F `dcount_hll(hll_merge(...))` pattern is required for EU-compliant distinct user counts across clusters\n- For EU data, use `macro-expand force_remote = true officefluid_global as X (...) | summarize ...`\n- `Loop_Audience` (FluidRuntime) and `Release_AudienceGroup` (OWH\u002FQoS) are the same concept; filter `== \"Production\"` to exclude dogfood noise\n",{"name":5,"version":47,"description":7},"1.0.0","main","5e94cbfa27965a98428f7d26b69dd5b0a8abeb0d",".agency\u002Fplugins\u002Fff-oce\u002Fskills\u002Fff-oce-kusto",590,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework","https:\u002F\u002Ffluidframework.com","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-14 08:12:05",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add microsoft\u002FFluidFramework --skill ff-oce-kusto",{"tool":64,"command":65},"bunx","bunx skills add microsoft\u002FFluidFramework --skill ff-oce-kusto",{"tool":67,"command":68},"pnpm","pnpm dlx skills add microsoft\u002FFluidFramework --skill ff-oce-kusto","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.agency\u002Fplugins\u002Fff-oce\u002Fskills\u002Fff-oce-kusto\u002FSKILL.md",true,[72,78,82,86],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fcheckpoint-safety.md","REFERENCE","参考文档",9559,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgoogle-cloud-storage-fuse\u002Freferences\u002Fcheckpoint-safety.md",{"path":79,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fgke-training-deployment.md",13402,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgoogle-cloud-storage-fuse\u002Freferences\u002Fgke-training-deployment.md",{"path":83,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fkusto-query-reference.md",78203,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.agency\u002Fplugins\u002Fff-oce\u002Fskills\u002Fff-oce-kusto\u002Freferences\u002Fkusto-query-reference.md",{"path":87,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fperformance-diagnosis.md",9401,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgoogle-cloud-storage-fuse\u002Freferences\u002Fperformance-diagnosis.md",[91,112,150,174,191,213],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":42},"01M6PJ5SAHYFZFWDG5Y4RW56EP","trigger-pipelines-for-copilot-pr","Trigger ADO pipelines for a Copilot-created PR by posting \u002Fazp run comments. Use when the user asks to trigger CI pipelines for a specific PR.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftrigger-pipelines-for-copilot-pr\u002FSKILL.md",[],[98,99,23,100,101,102,103,104,105,106,107,108,109,110,111,22],"pr","trigger pipelines for copilot pr","trigger","copilot","pipelines","ado","posting","run","ci","use","number","URL","comments","user",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":131,"publishedAt":42},"01M6PJ5M4ZG7E78C4GM4041HEP","review","Review changes relative to a prior state, such as a diff, pull request, branch, commit, or working-tree changes. Use for change-focused code review and regression analysis. Do not use to assess an existing file, API, design, implementation, or other artifact without a comparison; if the request is ambiguous, ask whether the user wants a change review and what prior state to compare against.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Freview\u002FSKILL.md",[118,123,126],{"categoryNo":119,"categoryName":120,"taxonomyType":121,"taxonomyTypeDesc":122},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":124,"categoryName":125,"taxonomyType":121,"taxonomyTypeDesc":122},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":127,"categoryName":128,"taxonomyType":129,"taxonomyTypeDesc":130},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[114,132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,31,147,23,148,149],"branch","regression","code review","design","ask","analysis","code","commit","api","change","artifact","request","pull","tree","as","diff","assess","ambiguous",{"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":159,"publishedAt":42},"01M6PJ5E3PCBDS319FFMHPFACN","review-pr-local","The authority on pulling a pull request — Azure DevOps or GitHub — into an isolated local worktree so a human can review it in their editor, and on posting human-controlled review comments back to the PR (ADO via the ado PR-thread MCP tools or the Azure DevOps REST API, GitHub via the gh CLI). Auto-detects the platform and all identifiers from the PR URL; not tied to any specific repository. The AI assists an interactive human review and only ever posts comments the human explicitly requests. If you find yourself checking out a PR branch over the user's own working tree, or posting AI-authored review prose the human did not ask for, invoke this skill instead.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Freview-pr-local\u002FSKILL.md",[156],{"categoryNo":157,"categoryName":158,"taxonomyType":121,"taxonomyTypeDesc":122},"01JBSEEDCAT000000000000023","Skill与智能体开发",[160,114,98,161,162,163,132,164,165,166,167,168,169,170,109,171,136,140,172,173],"local","review pr local","review pr","back","posts","only","MCP","authority","auto","invoke","azure devops","you","cli","worktree",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":180,"publishedAt":42},"01M6PJ5AVZAS0AEBPCYJZ9ZMMD","policy-check","This skill should be used when the user asks to \"run policy check\", \"check policy\", \"policy-check\", or needs to validate package compliance. Provides guidance on running policy checks for specific packages or the entire repository.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fpolicy-check\u002FSKILL.md",[],[181,182,183,184,185,23,105,186,187,188,189,111,21,22,190],"policy check","policy","check","packages","compliance","repository","guidance","validate","package","entire",{"skillNo":192,"name":193,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":195,"categories":196,"keywords":200,"publishedAt":42},"01M6PJ54H068MZF2WD2JDKCVDC","pipeline-test-triage","Triage test failures in an Azure DevOps pipeline run for Fluid Framework. Use when the user shares an ADO build\u002Fpipeline URL or build ID and wants failures analyzed, when they ask \"why did this pipeline fail\", \"summarize the test failures\", \"is this test flaky or a real bug\", \"compare these runs\", or wants bugs filed for genuine failures. Covers the Real Service End to End Tests pipeline as the worked example but applies to any FF test pipeline.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fpipeline-test-triage\u002FSKILL.md",[197],{"categoryNo":198,"categoryName":199,"taxonomyType":121,"taxonomyTypeDesc":122},"01JBSEEDCAT000000000000008","测试与质量",[201,202,203,204,205,206,207,208,170,109,136,105,209,210,211,38,103,146,212,23,22],"pipeline","test triage","pipeline test triage","pipeline test","test","triage","end","test pipeline","why","bug","but","bugs",{"skillNo":214,"name":215,"nameZh":6,"description":216,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":217,"categories":218,"keywords":219,"publishedAt":42},"01M6PJ4ZJASDV2CGQTG1JWKBFE","fluid-release","Fluid Framework client release group — minor releases, patch releases, and post-release type test updates. Covers release prep, branching, version bumps, changelogs, release notes, and type test baselines. In autonomous mode, auto-detects state from the repo, attempts to execute, and falls back to a GitHub issue on failure. Triggers on \"release\", \"do the release\", \"release status\", version bump, release notes, changelog, release branch, or release engineering.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ffluid-release\u002FSKILL.md",[],[220,221,40,163,132,20,222,223,224,225,168,226,227,228,229,230,231,232,233,234],"release","fluid release","mode","autonomous","release notes","release status","updates","patch","notes","changelog","release prep","releases","status","issue","branching"]