[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69BDWVVR2905APG7WHV1XST":3,"skill-same:01M69BDWVVR2905APG7WHV1XST":102},{"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":31,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":57,"commitSha":58,"skillDirectory":59,"forksCount":60,"repositoryHtmlUrl":61,"repositoryHomepageUrl":6,"ownerHtmlUrl":62,"ownerBlogUrl":63,"ownerDescription":64,"updatedAt":65,"install":66,"resources":79},"01M69BDWVVR2905APG7WHV1XST","query-design",null,"Separates DAX data-fetching from TypeScript presentation. Guides when to use  DAX vs. TypeScript vs. Vega-Lite for aggregation, total rows, FORMAT(), SELECTCOLUMNS,  BLANK handling, filtering, multi-grain queries, cross-filtering and cross-highlight subset\u002Foverlay queries, and format strings.","microsoft\u002FValueLens-for-Microsoft-Copilot","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69BCX78JTCQ42HNQPM53DBN",23,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FValueLens-for-Microsoft-Copilot\u002Fblob\u002Fmain\u002Ffabric-app\u002F.agents\u002Fskills\u002Fquery-design\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000003","演示文稿","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"query design","design","query","data-fetching","when","grain","overlay","when to use","for","strings","multi","guides","queries","use","filtering","format","aggregation","data","dax","typescript","2026-11-10 10:12:30",false,"---\nname: query-design\ndescription: >\n  Separates DAX data-fetching from TypeScript presentation. Guides when to use \n  DAX vs. TypeScript vs. Vega-Lite for aggregation, total rows, FORMAT(), SELECTCOLUMNS, \n  BLANK handling, filtering, multi-grain queries, cross-filtering and\n  cross-highlight subset\u002Foverlay queries, and format strings.\n---\n\n# Query Design — Separation of Data and Presentation\n\n**DAX computes and fetches data. TypeScript shapes it for display. VegaVisual and DataGrid render it.**\n\nAggregate in DAX to the visual's grain — never fetch lower-grain rows to roll up client-side. When a visual layout changes, only the TypeScript or spec layer should change — not the DAX query.\n\n## Responsibility Matrix\n\n| Concern | Owner |\n|---|---|\n| Semantic measures (SUM, DISTINCTCOUNT, etc.) | DAX |\n| Filters and slicers | DAX or TypeScript ([see Filter Strategy](references\u002Ffilter-strategy.md)) |\n| Grouping grain (SUMMARIZECOLUMNS) | DAX |\n| Time intelligence (YTD, YoY) | DAX |\n| TopN \u002F payload reduction | DAX |\n| Deterministic row ordering (ORDER BY) | DAX (for debugging — not presentation sort) |\n| Partitioning a flagged result table | TypeScript |\n| Coordinating separate query results | TypeScript (one hook call per result table) |\n| Server-provided grand totals (preferred, supports all aggregation types) | DAX + TypeScript row partitioning |\n| DataGrid-computed grand totals | DataGrid (alternative only for additive `sum` values or a count of fetched leaf rows) |\n| Filling dimension gaps | TypeScript (stitch dimension list into sparse results) |\n| Reshaping (pivot, unpivot) | TypeScript |\n| Column display names | `columnMetadata` in factory file |\n| Vega-Lite \u002F DataGrid field identifiers | `columnMetadata.name` (bracket-free alias) |\n| Number\u002Fdate formatting | `columnMetadata.format` \u002F Vega-Lite spec |\n| User-facing sort order | TypeScript \u002F Vega-Lite `sort` \u002F DataGrid `sort` |\n| Decorative labels, icons | DataGrid `cellRenderer` or Vega-Lite condition |\n| Axis titles, legends, color encoding | Vega-Lite spec |\n\n## Rules\n\n### Must\n\n- Aggregate in DAX to the visual's grain — never fetch lower-grain rows just to roll them up to that grain in TypeScript\n- One `EVALUATE` per `.dax` file; use `ROLLUPADDISSUBTOTAL` when DataGrid body and grand-total grains share one result table\n- `ORDER BY` in DAX for stable, diffable results — not presentation sort\n- Same filters\u002Fmeasures across related split-grain queries to prevent drift\n\n### Prefer\n\n- `SUMMARIZECOLUMNS` for grouped aggregation — it also drops BLANK-measure rows, keeping payloads small\n- DAX's natural column names (`'Table'[Column]`, `[Measure]`) as `columnMetadata` **keys**, mapped to a bracket-free `name` and a human-readable `displayName`\n- Raw typed values from DAX — format via `columnMetadata.format` or Vega-Lite, never `FORMAT()`\n- Model-defined format strings (from `INFO.VIEW.MEASURES()`) over invented ones\n- Multiple lightweight queries for independently shaped datasets; one flagged rollup query for a DataGrid body and grand total\n- User-facing sort in TypeScript \u002F Vega-Lite \u002F DataGrid — never re-query for sort\n\n### Avoid\n\n- `SELECTCOLUMNS` solely for renaming — use `columnMetadata` (`name` + `displayName`) instead\n- Reusing the raw DAX column name as `columnMetadata.name` — `[` `]` `.` make the visual read `undefined`\n- `UNION` to mix body and total grains — use `ROLLUPADDISSUBTOTAL` and partition its flagged rows\n- `FORMAT()` in DAX — converts to text, breaks sorting and charting\n- Converting BLANK to `0` \u002F `\"\"` \u002F `\"N\u002FA\"` in DAX — causes result-set explosion\n- `CONCATENATEX`, `UNICHAR`, emoji prefixes — decorative text belongs in `cellRenderer` or Vega-Lite\n- Fetching all members of high-cardinality dimensions just to fill gaps\n\n## Decision Flowchart\n\n```\nNeed to add something to the query result?\n  |-- Calculation \u002F aggregation \u002F filter?\n  |     -> DAX (measures, CALCULATE, SUMMARIZECOLUMNS)\n  |-- Interactive filter the user controls?\n  |     -> Low-cardinality: widen grain, filter in TypeScript or Vega-Lite transform\n  |     -> High-cardinality: push filter to DAX, re-query\n  |-- Adding a DataGrid grand total?\n  |     -> DAX rollup query: split body and total rows with toRollupDataTables\n  |        and always pass the returned grandTotalTable via grandTotals.data\n  |     -> DataGrid-computed sum\u002Fcount: pass grandTotals without data and set defaultAggregation\n  |-- Merging datasets or adding other synthetic rows?\n  |     -> Charts: pass multiple DataTables to VegaVisual, layer in spec\n  |     -> Grids: append rows in TypeScript, style via cellRenderer\n  |-- Renaming a column for display?\n  |     -> columnMetadata in the factory file (displayName)\n  |-- Formatting, labeling, or encoding?\n  |     -> Vega-Lite spec or DataGrid cellRenderer\n  |-- Decorating values (icons, status badges, null placeholders)?\n  |     -> DataGrid cellRenderer or Vega-Lite condition encoding\n  |-- Not sure?\n        -> Does it change what the data *means* (filter, measure, grain)? -> DAX\n           Does it change only how data is *rendered* (labels, icons, layout)? -> TypeScript \u002F Vega-Lite spec \u002F DataGrid cellRenderer\n           Still unclear? -> Read the relevant reference above\n```\n\n## Interactivity\n\nReports coordinate multiple visuals: a selection in one changes what the others show. Two distinct behaviors, with different data work behind them:\n\n- **Cross-filtering** — a selection in one visual constrains the data shown in another, removing or narrowing the non-matching rows from the target's view. The target shows *less*. Applying that constraint is a cost\u002Fcardinality tradeoff — widen the grain and filter client-side, or push the filter into DAX and re-query. See [Filter strategy](references\u002Ffilter-strategy.md).\n- **Cross-highlighting** — a selection in one visual emphasizes the matching subset *within* another while the full context stays visible. The target keeps its baseline (dimmed) and draws the selected subset bright on top. The subset is a separate aggregation aligned to the baseline's grouping, measures, and row set — not a client-side filter of the baseline. See [Highlight queries](references\u002Fhighlight-queries.md).\n\nBoth consume the predicate-based selection events the visual components emit (`onInteraction`). The components render only the `DataTable`s they are handed; this skill produces those tables. For how a spec binds and layers multiple datasets, see the visuals skill's [multi-data input](..\u002Fvisuals\u002Freferences\u002Fmulti-data-input.md) reference.\n\n## Reference Materials\n\nRead these when working on a specific topic:\n\n- **[Anti-patterns and corrections](references\u002Fanti-patterns.md)** — Open when reviewing a query that uses `UNION` for totals, `FORMAT()`, `SELECTCOLUMNS` for renaming, `CONCATENATEX`\u002Femoji decoration, BLANK-to-`0` conversion, or `GENERATE`\u002F`CROSSJOIN` for gap-filling.\n- **[Multi-grain patterns](references\u002Fmulti-grain-patterns.md)** — Open when a single visualization needs data at multiple grains (e.g., bars + reference line, region detail + total row, monthly trend + YTD), to choose between one flagged rollup result and separate queries while keeping related factories, hooks, and `DataTable`s aligned.\n- **[Filter strategy](references\u002Ffilter-strategy.md)** — Open when adding a user-controlled filter or implementing cross-filtering, and deciding whether to widen the grain (filter client-side) or push the filter into DAX (re-query on each change).\n- **[Highlight queries](references\u002Fhighlight-queries.md)** — Open when writing the \"selected subset\" overlay query for a cross-highlight visual: an aligned `CALCULATETABLE` \u002F `TREATAS` query whose rows match the baseline.\n- **[Format strings](references\u002Fformat-strings.md)** — Open when picking a `columnMetadata.format` value, when a measure has a dynamic format string, or when formatting needs to flow into a Vega-Lite axis.\n\n## Integration with Sibling Skills\n\n- **[schema-discovery](..\u002Fschema-discovery\u002FSKILL.md)** — Schema exploration; discover tables, columns, and relationships before writing queries.\n- **[dax-authoring](..\u002Fdax-authoring\u002FSKILL.md)** — DAX syntax, query patterns, and testing workflow. Apply this skill's principles when deciding what DAX should compute.\n- **[visuals](..\u002Fvisuals\u002FSKILL.md)** — Vega-Lite specs and DataGrid configuration. Push formatting and labels into specs, not DAX.","# Query Design — Separation of Data and Presentation\n\n**DAX computes and fetches data. TypeScript shapes it for display. VegaVisual and DataGrid render it.**\n\nAggregate in DAX to the visual's grain — never fetch lower-grain rows to roll up client-side. When a visual layout changes, only the TypeScript or spec layer should change — not the DAX query.\n\n## Responsibility Matrix\n\n| Concern | Owner |\n|---|---|\n| Semantic measures (SUM, DISTINCTCOUNT, etc.) | DAX |\n| Filters and slicers | DAX or TypeScript ([see Filter Strategy](references\u002Ffilter-strategy.md)) |\n| Grouping grain (SUMMARIZECOLUMNS) | DAX |\n| Time intelligence (YTD, YoY) | DAX |\n| TopN \u002F payload reduction | DAX |\n| Deterministic row ordering (ORDER BY) | DAX (for debugging — not presentation sort) |\n| Partitioning a flagged result table | TypeScript |\n| Coordinating separate query results | TypeScript (one hook call per result table) |\n| Server-provided grand totals (preferred, supports all aggregation types) | DAX + TypeScript row partitioning |\n| DataGrid-computed grand totals | DataGrid (alternative only for additive `sum` values or a count of fetched leaf rows) |\n| Filling dimension gaps | TypeScript (stitch dimension list into sparse results) |\n| Reshaping (pivot, unpivot) | TypeScript |\n| Column display names | `columnMetadata` in factory file |\n| Vega-Lite \u002F DataGrid field identifiers | `columnMetadata.name` (bracket-free alias) |\n| Number\u002Fdate formatting | `columnMetadata.format` \u002F Vega-Lite spec |\n| User-facing sort order | TypeScript \u002F Vega-Lite `sort` \u002F DataGrid `sort` |\n| Decorative labels, icons | DataGrid `cellRenderer` or Vega-Lite condition |\n| Axis titles, legends, color encoding | Vega-Lite spec |\n\n## Rules\n\n### Must\n\n- Aggregate in DAX to the visual's grain — never fetch lower-grain rows just to roll them up to that grain in TypeScript\n- One `EVALUATE` per `.dax` file; use `ROLLUPADDISSUBTOTAL` when DataGrid body and grand-total grains share one result table\n- `ORDER BY` in DAX for stable, diffable results — not presentation sort\n- Same filters\u002Fmeasures across related split-grain queries to prevent drift\n\n### Prefer\n\n- `SUMMARIZECOLUMNS` for grouped aggregation — it also drops BLANK-measure rows, keeping payloads small\n- DAX's natural column names (`'Table'[Column]`, `[Measure]`) as `columnMetadata` **keys**, mapped to a bracket-free `name` and a human-readable `displayName`\n- Raw typed values from DAX — format via `columnMetadata.format` or Vega-Lite, never `FORMAT()`\n- Model-defined format strings (from `INFO.VIEW.MEASURES()`) over invented ones\n- Multiple lightweight queries for independently shaped datasets; one flagged rollup query for a DataGrid body and grand total\n- User-facing sort in TypeScript \u002F Vega-Lite \u002F DataGrid — never re-query for sort\n\n### Avoid\n\n- `SELECTCOLUMNS` solely for renaming — use `columnMetadata` (`name` + `displayName`) instead\n- Reusing the raw DAX column name as `columnMetadata.name` — `[` `]` `.` make the visual read `undefined`\n- `UNION` to mix body and total grains — use `ROLLUPADDISSUBTOTAL` and partition its flagged rows\n- `FORMAT()` in DAX — converts to text, breaks sorting and charting\n- Converting BLANK to `0` \u002F `\"\"` \u002F `\"N\u002FA\"` in DAX — causes result-set explosion\n- `CONCATENATEX`, `UNICHAR`, emoji prefixes — decorative text belongs in `cellRenderer` or Vega-Lite\n- Fetching all members of high-cardinality dimensions just to fill gaps\n\n## Decision Flowchart\n\n```\nNeed to add something to the query result?\n  |-- Calculation \u002F aggregation \u002F filter?\n  |     -> DAX (measures, CALCULATE, SUMMARIZECOLUMNS)\n  |-- Interactive filter the user controls?\n  |     -> Low-cardinality: widen grain, filter in TypeScript or Vega-Lite transform\n  |     -> High-cardinality: push filter to DAX, re-query\n  |-- Adding a DataGrid grand total?\n  |     -> DAX rollup query: split body and total rows with toRollupDataTables\n  |        and always pass the returned grandTotalTable via grandTotals.data\n  |     -> DataGrid-computed sum\u002Fcount: pass grandTotals without data and set defaultAggregation\n  |-- Merging datasets or adding other synthetic rows?\n  |     -> Charts: pass multiple DataTables to VegaVisual, layer in spec\n  |     -> Grids: append rows in TypeScript, style via cellRenderer\n  |-- Renaming a column for display?\n  |     -> columnMetadata in the factory file (displayName)\n  |-- Formatting, labeling, or encoding?\n  |     -> Vega-Lite spec or DataGrid cellRenderer\n  |-- Decorating values (icons, status badges, null placeholders)?\n  |     -> DataGrid cellRenderer or Vega-Lite condition encoding\n  |-- Not sure?\n        -> Does it change what the data *means* (filter, measure, grain)? -> DAX\n           Does it change only how data is *rendered* (labels, icons, layout)? -> TypeScript \u002F Vega-Lite spec \u002F DataGrid cellRenderer\n           Still unclear? -> Read the relevant reference above\n```\n\n## Interactivity\n\nReports coordinate multiple visuals: a selection in one changes what the others show. Two distinct behaviors, with different data work behind them:\n\n- **Cross-filtering** — a selection in one visual constrains the data shown in another, removing or narrowing the non-matching rows from the target's view. The target shows *less*. Applying that constraint is a cost\u002Fcardinality tradeoff — widen the grain and filter client-side, or push the filter into DAX and re-query. See [Filter strategy](references\u002Ffilter-strategy.md).\n- **Cross-highlighting** — a selection in one visual emphasizes the matching subset *within* another while the full context stays visible. The target keeps its baseline (dimmed) and draws the selected subset bright on top. The subset is a separate aggregation aligned to the baseline's grouping, measures, and row set — not a client-side filter of the baseline. See [Highlight queries](references\u002Fhighlight-queries.md).\n\nBoth consume the predicate-based selection events the visual components emit (`onInteraction`). The components render only the `DataTable`s they are handed; this skill produces those tables. For how a spec binds and layers multiple datasets, see the visuals skill's [multi-data input](..\u002Fvisuals\u002Freferences\u002Fmulti-data-input.md) reference.\n\n## Reference Materials\n\nRead these when working on a specific topic:\n\n- **[Anti-patterns and corrections](references\u002Fanti-patterns.md)** — Open when reviewing a query that uses `UNION` for totals, `FORMAT()`, `SELECTCOLUMNS` for renaming, `CONCATENATEX`\u002Femoji decoration, BLANK-to-`0` conversion, or `GENERATE`\u002F`CROSSJOIN` for gap-filling.\n- **[Multi-grain patterns](references\u002Fmulti-grain-patterns.md)** — Open when a single visualization needs data at multiple grains (e.g., bars + reference line, region detail + total row, monthly trend + YTD), to choose between one flagged rollup result and separate queries while keeping related factories, hooks, and `DataTable`s aligned.\n- **[Filter strategy](references\u002Ffilter-strategy.md)** — Open when adding a user-controlled filter or implementing cross-filtering, and deciding whether to widen the grain (filter client-side) or push the filter into DAX (re-query on each change).\n- **[Highlight queries](references\u002Fhighlight-queries.md)** — Open when writing the \"selected subset\" overlay query for a cross-highlight visual: an aligned `CALCULATETABLE` \u002F `TREATAS` query whose rows match the baseline.\n- **[Format strings](references\u002Fformat-strings.md)** — Open when picking a `columnMetadata.format` value, when a measure has a dynamic format string, or when formatting needs to flow into a Vega-Lite axis.\n\n## Integration with Sibling Skills\n\n- **[schema-discovery](..\u002Fschema-discovery\u002FSKILL.md)** — Schema exploration; discover tables, columns, and relationships before writing queries.\n- **[dax-authoring](..\u002Fdax-authoring\u002FSKILL.md)** — DAX syntax, query patterns, and testing workflow. Apply this skill's principles when deciding what DAX should compute.\n- **[visuals](..\u002Fvisuals\u002FSKILL.md)** — Vega-Lite specs and DataGrid configuration. Push formatting and labels into specs, not DAX.",{"name":5,"description":7},"main","492bde55156d338649198105a73f7954165568ea","fabric-app\u002F.agents\u002Fskills\u002Fquery-design",5,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FValueLens-for-Microsoft-Copilot","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-11 02:35:05",{"source":8,"skillName":5,"commands":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add microsoft\u002FValueLens-for-Microsoft-Copilot --skill query-design",{"tool":72,"command":73},"bunx","bunx skills add microsoft\u002FValueLens-for-Microsoft-Copilot --skill query-design",{"tool":75,"command":76},"pnpm","pnpm dlx skills add microsoft\u002FValueLens-for-Microsoft-Copilot --skill query-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FValueLens-for-Microsoft-Copilot\u002Fblob\u002Fmain\u002Ffabric-app\u002F.agents\u002Fskills\u002Fquery-design\u002FSKILL.md",true,[80,86,90,94,98],{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fanti-patterns.md","REFERENCE","参考文档",10877,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FValueLens-for-Microsoft-Copilot\u002Fblob\u002Fmain\u002Ffabric-app\u002F.agents\u002Fskills\u002Fquery-design\u002Freferences\u002Fanti-patterns.md",{"path":87,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Ffilter-strategy.md",3106,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FValueLens-for-Microsoft-Copilot\u002Fblob\u002Fmain\u002Ffabric-app\u002F.agents\u002Fskills\u002Fquery-design\u002Freferences\u002Ffilter-strategy.md",{"path":91,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fformat-strings.md",2918,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FValueLens-for-Microsoft-Copilot\u002Fblob\u002Fmain\u002Ffabric-app\u002F.agents\u002Fskills\u002Fquery-design\u002Freferences\u002Fformat-strings.md",{"path":95,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fhighlight-queries.md",5650,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FValueLens-for-Microsoft-Copilot\u002Fblob\u002Fmain\u002Ffabric-app\u002F.agents\u002Fskills\u002Fquery-design\u002Freferences\u002Fhighlight-queries.md",{"path":99,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Fmulti-grain-patterns.md",11171,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FValueLens-for-Microsoft-Copilot\u002Fblob\u002Fmain\u002Ffabric-app\u002F.agents\u002Fskills\u002Fquery-design\u002Freferences\u002Fmulti-grain-patterns.md",[103,125,150,174,196,214],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":52},"01M69BE0DTF2948C1JH2JZQV3P","visuals","Use when user wants to incorporate charts, graphs, data grid,  or other visual representations of data into their project. Use VegaVisual and DataGrid components to create these visuals,  utilizing the shared DataTable input, formatting, theme, and interactivity. Covers the VisualContainer chrome every visual gets by default, the onInteraction selection\u002Fclick events host apps consume, named multi-table data input for layered overlays and reference lines, and Vega-Lite native selections.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FValueLens-for-Microsoft-Copilot\u002Fblob\u002Fmain\u002Ffabric-app\u002F.agents\u002Fskills\u002Fvisuals\u002FSKILL.md",[],[105,110,111,112,113,45,114,115,116,117,118,119,120,121,122,42,123,124,40,36],"chrome","components","create","Charts","default","selection","visual","shared","project","click","host","apps","theme","grid","overlays",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":52},"01M69BDYMX0FVKJE5GPWECAVZC","schema-discovery","Explore Power BI semantic model schemas using DAX INFO functions. Progressive metadata discovery strategy, scope estimation, and narrowing techniques for tables, columns, measures, and relationships.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FValueLens-for-Microsoft-Copilot\u002Fblob\u002Fmain\u002Ffabric-app\u002F.agents\u002Fskills\u002Fschema-discovery\u002FSKILL.md",[],[132,133,134,50,135,136,137,138,139,140,141,142,143,144,145,146,147,148,40,149],"schema discovery","discovery","schema","power bi","explore","model","strategy","power","functions","info","relationships","estimation","scope","bi","columns","tables","techniques","progressive",{"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":52},"01M69BDTFG1HXNFSSNTZZ17TKK","playwright-cli","Automate browser interactions, test web pages and work with Playwright tests.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FValueLens-for-Microsoft-Copilot\u002Fblob\u002Fmain\u002Ffabric-app\u002F.agents\u002Fskills\u002Fplaywright-cli\u002FSKILL.md",[156],{"categoryNo":157,"categoryName":158,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[160,161,162,163,164,165,166,167,168,169,170,69,171,172,173,152],"cli","playwright","playwright cli","test","web","browser","npm","Bash","automate","work","test web","tests","pages","with",{"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":52},"01M69BDRQ0WNVATNFD6H4S98KH","fabric-sdk","How to use @microsoft\u002Ffabric-app-data to connect web applications to Fabric data sources at runtime. Build browser-based apps that query semantic models via DAX using the FabricClient API.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FValueLens-for-Microsoft-Copilot\u002Fblob\u002Fmain\u002Ffabric-app\u002F.agents\u002Fskills\u002Ffabric-sdk\u002FSKILL.md",[],[181,182,183,164,9,50,184,185,186,165,49,187,188,189,45,34,190,191,121,192,193,194,195],"sdk","fabric sdk","fabric","connect","fabric data","semantic models","applications","api","how","runtime","app","how to","sources","at","data sources",{"skillNo":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":200,"categories":201,"keywords":202,"publishedAt":52},"01M69BDQ6CVBSZA9N5RBZR60J1","fabric-cli","How to use fabric-app-data CLI to manage Fabric data source connections. Maintain workspace\u002Fitem IDs in a fabric.yaml file with profiles, add connections by ID or Fabric portal URL, and generate TypeScript config for use with @microsoft\u002Ffabric-app-data.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FValueLens-for-Microsoft-Copilot\u002Fblob\u002Fmain\u002Ffabric-app\u002F.agents\u002Fskills\u002Ffabric-cli\u002FSKILL.md",[],[160,203,183,51,9,204,205,185,206,207,189,45,208,209,210,191,211,192,173,212,213,40],"fabric cli","config","generate","file","ids","manage","maintain","connections","id","URL","profiles",{"skillNo":215,"name":216,"nameZh":6,"description":217,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":218,"categories":219,"keywords":221,"publishedAt":52},"01M69BDN8Q4V54H7MTZQFDG0V6","dax-authoring","Write and test DAX queries against Power BI semantic models. Covers DAX syntax rules, query patterns, time intelligence, and an iterative test workflow using the Fabric CLI query command.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FValueLens-for-Microsoft-Copilot\u002Fblob\u002Fmain\u002Ffabric-app\u002F.agents\u002Fskills\u002Fdax-authoring\u002FSKILL.md",[220],{"categoryNo":157,"categoryName":158,"taxonomyType":21,"taxonomyTypeDesc":22},[50,222,223,160,224,163,203,135,183,186,225,226,227,228,139,229,44,34,230,145],"dax authoring","authoring","workflow","Rules","syntax","command","write","models","time"]