[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699YCN4ZDW2AMDP4NVJ2QGC":3,"skill-same:01M699YCN4ZDW2AMDP4NVJ2QGC":104},{"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":28,"publishedAt":32,"linkOnly":33,"markdownContent":34,"markdownBody":35,"frontMatter":36,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M699YCN4ZDW2AMDP4NVJ2QGC","visuals",null,"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 onInteraction selection\u002Fclick events host apps consume, named multi-table data input for layered overlays and reference lines, and Vega-Lite native selections. Triggers: chart, graph, plot, dashboard, KPI, metric, trend, scorecard, data grid, visualize.","microsoft\u002Frayfin","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M699VK9NEV8GH0Y5JKT1G8XG",662,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin\u002Fblob\u002Fmain\u002Fsamples\u002Funiversal-app\u002Ftemplate\u002F.agents\u002Fskills\u002Fvisuals\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000013","分析与可视化","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[5,29,30,31],"visualize","dashboard","components","2026-11-10 10:12:30",false,"---\nname: visuals\ndescription: >\n  Use when user wants to incorporate charts, graphs, data grid, \n  or other visual representations of data into their project.\n  Use VegaVisual and DataGrid components to create these visuals, \n  utilizing the shared DataTable input, formatting, theme, and interactivity.\n  Covers the onInteraction selection\u002Fclick events host apps consume, named\n  multi-table data input for layered overlays and reference lines, and\n  Vega-Lite native selections. Triggers: chart, graph, plot, dashboard, KPI,\n  metric, trend, scorecard, data grid, visualize.\n---\n\n# Visuals\n\n## Turn it on first\n\n```sh\nnpm run pack:add -- visuals\n```\n\nThat installs `@microsoft\u002Ffabric-visuals`, `@microsoft\u002Ffabric-visuals-core` and\n`@microsoft\u002Ffabric-datagrid`, copies in `toDataTable`, and wires\n`validate:visual`. Run it before writing any component that imports them — the\nbase app does not carry the visual packages, so the imports below do not resolve\nuntil it is applied.\n\nRe-applying is safe: an existing file is preserved, not overwritten.\n\nCharting is all this pack does.\nIf the numbers come from a Power BI semantic model, add `analytics` as well and\nread [`analytics`](..\u002Fanalytics\u002FSKILL.md) — it owns the connection, the queries\nand the semantic-model connector.\nCharts over sample data or over records the app owns need no analytics pack.\n\n## Types of visuals\n\nThere are 2 different types of visuals that can be used in a project:\n1. Charts and Graphs: These are used to represent data in a visual format, such as bar charts, line charts, pie charts, etc. These are built using vega-lite, see [references\u002Fvega-lite-visual.md](references\u002Fvega-lite-visual.md) for more details.\n2. Data Grids: These are used to display tabular data in a structured format, allowing for sorting, filtering, and pagination. See [references\u002Fdata-grid-visual.md](references\u002Fdata-grid-visual.md) for more details.\n\n## Packages & Imports\n\nThe visual components are provided by three packages. **Always use these package imports when creating visuals.**\n\n| Package | Primary exports | Example import |\n|---|---|---|\n| `@microsoft\u002Ffabric-visuals` | `VegaVisual`, types: `VisualizationSpec`, `VegaLiteConfig`, `VegaVisualProps` | `import { VegaVisual } from \"@microsoft\u002Ffabric-visuals\"` |\n| `@microsoft\u002Ffabric-datagrid` | `DataGrid`, types: `GridColumnDef`, `Row`, `CellValue`, `DataGridProps`, `DataGridTheme`, `SortConfig` | `import { DataGrid } from \"@microsoft\u002Ffabric-datagrid\"` |\n| `@microsoft\u002Ffabric-visuals-core` | `isDataTable`, `convertDataTableToRows`, design tokens | `import { isDataTable } from \"@microsoft\u002Ffabric-visuals-core\"` |\n\nThe `DataTable` type (used by both components) is defined in `@microsoft\u002Ffabric-visuals-core` and re-exported by the visual packages' type definitions.\n\n## Data Format\n\nThe chart and data grid components share a unified `data` prop of type `DataTable` (from `@microsoft\u002Ffabric-visuals-core`). This structured format carries column metadata (`displayName`, `format`, `semanticType`) that the components use for axis titles, grid headers, number formatting, and tooltips.\n\n**Using `DataTable`**: Pass a `DataTable` via the `data` prop. The visual uses its column metadata for formatting, axis titles, and tooltips.\n\n**From a query result**: the pack copies in `toDataTable()` at\n`packages\u002Ffrontend\u002Fsrc\u002Flib\u002Fto-data-table.ts`, which merges a query's table with the\n`columnMetadata` its factory exports to produce a `DataTable`. Its parameter is\n`QueryTableLike` — `{ columns: { name }[], rows }` — which the Fabric SDK's\n`QueryTable` satisfies, so it accepts a semantic-model result without this pack\ndepending on the `analytics` one.\n\n**Inline spec data — Vega-Lite only**: the `data` prop takes a `DataTable`\nwhatever the rows are, query results and static rows alike, and for `DataGrid` it\nis the only option. A Vega-Lite spec additionally accepts its own\n`data: { values: [...] }`, with the `data` prop omitted. That second form\ndiscards the `DataTable` metadata — `displayName`, `format` and `semanticType` —\nso axis titles and number formatting have to be part of the Vega-Lite spec; prefer the prop\nwhenever that metadata exists, which is normally the case for anything a query\nreturned.\n\n**Multiple tables in one visual**: the `data` prop also accepts a `Record\u003Cstring, DataTable>` for specs that bind separate layers to more than one dataset by name such as layered overlays, reference lines, and axis spines. See [references\u002Fmulti-data-input.md](references\u002Fmulti-data-input.md).\n\n```tsx\nimport { VegaVisual, useCssTheme } from \"@microsoft\u002Ffabric-visuals\";\nimport type { VisualizationSpec } from \"@microsoft\u002Ffabric-visuals\";\nimport { DataGrid } from \"@microsoft\u002Ffabric-datagrid\";\nimport type { DataTable } from \"@microsoft\u002Ffabric-visuals-core\";\n\n\u002F\u002F useCssTheme() reads --color-* vars from the page and updates automatically\n\u002F\u002F when the theme changes (e.g. dark-mode toggle adds\u002Fremoves the .dark class).\nconst theme = useCssTheme();\n\n\u002F\u002F Charts — pass a DataTable and Vega-Lite spec\n\u003CVegaVisual spec={vegaLiteSpec} data={dataTable} theme={theme} \u002F>\n\n\u002F\u002F Grids — displayName becomes column headers, format applies to cells\n\u003CDataGrid data={dataTable} theme={theme} \u002F>\n\n\u002F\u002F Inline spec data — Vega-Lite only, no data prop needed\nconst inlineSpec: VisualizationSpec = {\n  data: { values: [{ x: 1, y: 2 }, { x: 3, y: 4 }] },\n  mark: \"point\",\n  encoding: { ... },\n};\n\n\u003CVegaVisual spec={inlineSpec} theme={theme} \u002F>\n```\n\n**Type every spec you write**, with `VisualizationSpec` from\n`@microsoft\u002Ffabric-visuals` — on the constant, or as `useMemo\u003CVisualizationSpec>`\nwhen it is built per render. Without the annotation the object widens (`type:\n\"nominal\"` becomes `string`) and the compiler stops checking the parts that\nmatter. With it, build the spec however the chart needs — from a filter\nselection, a theme token, whatever — and `npm run typecheck` still checks the\nmark, encoding and field shapes.\n\n`validate:visual` adds the published Vega-Lite schema on top, catching value\nranges the types do not (`opacity: 5`), plus a spec that resolves to no mark at\nall. It can only read a spec whose values are literals, though; one assembled\nfrom variables is reported with `status: \"incomplete\"` and `ok: false`, not as a\ncompleted schema-validation pass.\nThe JSON report also carries `coverage: \"none\" | \"partial\" | \"complete\"`.\nWhen runtime or computed specs exist and zero schemas were checked, the normal\n`npm run validate:visual` gate exits nonzero.\nUse `npm run validate:visual:preview` only for that narrow zero-static-spec case\nto proceed to browser validation; actual failures still exit nonzero.\nWhen at least one schema was checked but runtime or computed specs remain,\nthe report stays `status: \"incomplete\"` and `ok: false` but exits zero without\nthe preview flag.\nThat partial result still requires browser validation and is not a completed\nvisual-validation gate.\nWhere a spec is static anyway, leave it literal or put it in a `.json` under\n`packages\u002Ffrontend\u002Fsrc\u002Fqueries\u002F` to get the schema check.\nWhere it genuinely varies at runtime, record the rendered browser check required\nby [`app-validation`](..\u002Fapp-validation\u002FSKILL.md) before calling the visual\ncomplete.\nMissing, unreadable, invalid, or uncompilable Vega-Lite\u002FAJV tooling is a failed\ninstall, not incomplete coverage.\nRestore the visuals pack dependencies; the preview flag never bypasses it.\n\nFor the `DataTable` schema and `ColumnDef` fields, see [references\u002Fdata-table.md](references\u002Fdata-table.md).\n\n## Formatting & Theme\n\n- **Formatting rules**: Number formatting, color palettes, chart-specific encoding rules, highlighting guidelines, and a default theme. See [references\u002Fformatting.md](references\u002Fformatting.md).\n\n## Custom visuals\n\nAlways use the above mentioned ways to create visual when possible. If the user's request doesn't allow creation using the above methods, ask the user if they are ok with using another library for creating the visual. If they are ok with it, use the library to create the visual. If they are not ok with it, then build that visual from scratch using HTML, CSS, and JS\u002FTS. Make sure to ask the user for any specific requirements they have for the visual, such as colors, labels, etc.\n\n## Container Layout\n\n- **`DataGrid`** — the direct parent must apply `overflow-auto` so content remains scrollable when it exceeds the container bounds (many rows).\n\n## Interactivity\n\nBoth `VegaVisual` and `DataGrid` expose an `onInteraction` prop that emits structured, predicate-based events when the user clicks a data point or row.\n\n**Always use the `onInteraction` prop** on `VegaVisual` and `DataGrid` to surface user selections. The component only emits the selection; the host app decides what it does — e.g. coordinating other visuals or queries on the page.\n\n> A visual renders a layered subset by binding two named datasets to two layers (`data={{ all, highlighted }}`) — see [references\u002Fmulti-data-input.md](references\u002Fmulti-data-input.md). The component renders whatever tables it is handed.\n\n```tsx\nimport type { InteractionEvent } from \"@microsoft\u002Ffabric-visuals-core\";\n\nfunction handleInteraction(source: string, events: InteractionEvent[]) {\n    for (const event of events) {\n        if (event.action === \"select\") {\n            \u002F\u002F event.selections describes the clicked data as predicates\n        } else if (event.action === \"clear\") {\n            \u002F\u002F user deselected (re-clicked same item or clicked empty space)\n        }\n    }\n}\n\n\u003CVegaVisual spec={spec} data={dataTable} theme={theme}\n    onInteraction={(events) => handleInteraction(\"salesChart\", events)} \u002F>\n\u003CDataGrid data={dataTable} theme={theme}\n    onInteraction={(events) => handleInteraction(\"detailTable\", events)} \u002F>\n```\n\n**Key concepts**:\n- Clicking a different data point emits a new `select` (replaces the prior selection — no preceding `clear`).\n- Re-clicking the same item or background space in a vega-lite visual emits `clear`.\n- Predicates include all fields from the datum; consumers filter to the ones that are relevant to them.\n","# Visuals\n\n## Turn it on first\n\n```sh\nnpm run pack:add -- visuals\n```\n\nThat installs `@microsoft\u002Ffabric-visuals`, `@microsoft\u002Ffabric-visuals-core` and\n`@microsoft\u002Ffabric-datagrid`, copies in `toDataTable`, and wires\n`validate:visual`. Run it before writing any component that imports them — the\nbase app does not carry the visual packages, so the imports below do not resolve\nuntil it is applied.\n\nRe-applying is safe: an existing file is preserved, not overwritten.\n\nCharting is all this pack does.\nIf the numbers come from a Power BI semantic model, add `analytics` as well and\nread [`analytics`](..\u002Fanalytics\u002FSKILL.md) — it owns the connection, the queries\nand the semantic-model connector.\nCharts over sample data or over records the app owns need no analytics pack.\n\n## Types of visuals\n\nThere are 2 different types of visuals that can be used in a project:\n1. Charts and Graphs: These are used to represent data in a visual format, such as bar charts, line charts, pie charts, etc. These are built using vega-lite, see [references\u002Fvega-lite-visual.md](references\u002Fvega-lite-visual.md) for more details.\n2. Data Grids: These are used to display tabular data in a structured format, allowing for sorting, filtering, and pagination. See [references\u002Fdata-grid-visual.md](references\u002Fdata-grid-visual.md) for more details.\n\n## Packages & Imports\n\nThe visual components are provided by three packages. **Always use these package imports when creating visuals.**\n\n| Package | Primary exports | Example import |\n|---|---|---|\n| `@microsoft\u002Ffabric-visuals` | `VegaVisual`, types: `VisualizationSpec`, `VegaLiteConfig`, `VegaVisualProps` | `import { VegaVisual } from \"@microsoft\u002Ffabric-visuals\"` |\n| `@microsoft\u002Ffabric-datagrid` | `DataGrid`, types: `GridColumnDef`, `Row`, `CellValue`, `DataGridProps`, `DataGridTheme`, `SortConfig` | `import { DataGrid } from \"@microsoft\u002Ffabric-datagrid\"` |\n| `@microsoft\u002Ffabric-visuals-core` | `isDataTable`, `convertDataTableToRows`, design tokens | `import { isDataTable } from \"@microsoft\u002Ffabric-visuals-core\"` |\n\nThe `DataTable` type (used by both components) is defined in `@microsoft\u002Ffabric-visuals-core` and re-exported by the visual packages' type definitions.\n\n## Data Format\n\nThe chart and data grid components share a unified `data` prop of type `DataTable` (from `@microsoft\u002Ffabric-visuals-core`). This structured format carries column metadata (`displayName`, `format`, `semanticType`) that the components use for axis titles, grid headers, number formatting, and tooltips.\n\n**Using `DataTable`**: Pass a `DataTable` via the `data` prop. The visual uses its column metadata for formatting, axis titles, and tooltips.\n\n**From a query result**: the pack copies in `toDataTable()` at\n`packages\u002Ffrontend\u002Fsrc\u002Flib\u002Fto-data-table.ts`, which merges a query's table with the\n`columnMetadata` its factory exports to produce a `DataTable`. Its parameter is\n`QueryTableLike` — `{ columns: { name }[], rows }` — which the Fabric SDK's\n`QueryTable` satisfies, so it accepts a semantic-model result without this pack\ndepending on the `analytics` one.\n\n**Inline spec data — Vega-Lite only**: the `data` prop takes a `DataTable`\nwhatever the rows are, query results and static rows alike, and for `DataGrid` it\nis the only option. A Vega-Lite spec additionally accepts its own\n`data: { values: [...] }`, with the `data` prop omitted. That second form\ndiscards the `DataTable` metadata — `displayName`, `format` and `semanticType` —\nso axis titles and number formatting have to be part of the Vega-Lite spec; prefer the prop\nwhenever that metadata exists, which is normally the case for anything a query\nreturned.\n\n**Multiple tables in one visual**: the `data` prop also accepts a `Record\u003Cstring, DataTable>` for specs that bind separate layers to more than one dataset by name such as layered overlays, reference lines, and axis spines. See [references\u002Fmulti-data-input.md](references\u002Fmulti-data-input.md).\n\n```tsx\nimport { VegaVisual, useCssTheme } from \"@microsoft\u002Ffabric-visuals\";\nimport type { VisualizationSpec } from \"@microsoft\u002Ffabric-visuals\";\nimport { DataGrid } from \"@microsoft\u002Ffabric-datagrid\";\nimport type { DataTable } from \"@microsoft\u002Ffabric-visuals-core\";\n\n\u002F\u002F useCssTheme() reads --color-* vars from the page and updates automatically\n\u002F\u002F when the theme changes (e.g. dark-mode toggle adds\u002Fremoves the .dark class).\nconst theme = useCssTheme();\n\n\u002F\u002F Charts — pass a DataTable and Vega-Lite spec\n\u003CVegaVisual spec={vegaLiteSpec} data={dataTable} theme={theme} \u002F>\n\n\u002F\u002F Grids — displayName becomes column headers, format applies to cells\n\u003CDataGrid data={dataTable} theme={theme} \u002F>\n\n\u002F\u002F Inline spec data — Vega-Lite only, no data prop needed\nconst inlineSpec: VisualizationSpec = {\n  data: { values: [{ x: 1, y: 2 }, { x: 3, y: 4 }] },\n  mark: \"point\",\n  encoding: { ... },\n};\n\n\u003CVegaVisual spec={inlineSpec} theme={theme} \u002F>\n```\n\n**Type every spec you write**, with `VisualizationSpec` from\n`@microsoft\u002Ffabric-visuals` — on the constant, or as `useMemo\u003CVisualizationSpec>`\nwhen it is built per render. Without the annotation the object widens (`type:\n\"nominal\"` becomes `string`) and the compiler stops checking the parts that\nmatter. With it, build the spec however the chart needs — from a filter\nselection, a theme token, whatever — and `npm run typecheck` still checks the\nmark, encoding and field shapes.\n\n`validate:visual` adds the published Vega-Lite schema on top, catching value\nranges the types do not (`opacity: 5`), plus a spec that resolves to no mark at\nall. It can only read a spec whose values are literals, though; one assembled\nfrom variables is reported with `status: \"incomplete\"` and `ok: false`, not as a\ncompleted schema-validation pass.\nThe JSON report also carries `coverage: \"none\" | \"partial\" | \"complete\"`.\nWhen runtime or computed specs exist and zero schemas were checked, the normal\n`npm run validate:visual` gate exits nonzero.\nUse `npm run validate:visual:preview` only for that narrow zero-static-spec case\nto proceed to browser validation; actual failures still exit nonzero.\nWhen at least one schema was checked but runtime or computed specs remain,\nthe report stays `status: \"incomplete\"` and `ok: false` but exits zero without\nthe preview flag.\nThat partial result still requires browser validation and is not a completed\nvisual-validation gate.\nWhere a spec is static anyway, leave it literal or put it in a `.json` under\n`packages\u002Ffrontend\u002Fsrc\u002Fqueries\u002F` to get the schema check.\nWhere it genuinely varies at runtime, record the rendered browser check required\nby [`app-validation`](..\u002Fapp-validation\u002FSKILL.md) before calling the visual\ncomplete.\nMissing, unreadable, invalid, or uncompilable Vega-Lite\u002FAJV tooling is a failed\ninstall, not incomplete coverage.\nRestore the visuals pack dependencies; the preview flag never bypasses it.\n\nFor the `DataTable` schema and `ColumnDef` fields, see [references\u002Fdata-table.md](references\u002Fdata-table.md).\n\n## Formatting & Theme\n\n- **Formatting rules**: Number formatting, color palettes, chart-specific encoding rules, highlighting guidelines, and a default theme. See [references\u002Fformatting.md](references\u002Fformatting.md).\n\n## Custom visuals\n\nAlways use the above mentioned ways to create visual when possible. If the user's request doesn't allow creation using the above methods, ask the user if they are ok with using another library for creating the visual. If they are ok with it, use the library to create the visual. If they are not ok with it, then build that visual from scratch using HTML, CSS, and JS\u002FTS. Make sure to ask the user for any specific requirements they have for the visual, such as colors, labels, etc.\n\n## Container Layout\n\n- **`DataGrid`** — the direct parent must apply `overflow-auto` so content remains scrollable when it exceeds the container bounds (many rows).\n\n## Interactivity\n\nBoth `VegaVisual` and `DataGrid` expose an `onInteraction` prop that emits structured, predicate-based events when the user clicks a data point or row.\n\n**Always use the `onInteraction` prop** on `VegaVisual` and `DataGrid` to surface user selections. The component only emits the selection; the host app decides what it does — e.g. coordinating other visuals or queries on the page.\n\n> A visual renders a layered subset by binding two named datasets to two layers (`data={{ all, highlighted }}`) — see [references\u002Fmulti-data-input.md](references\u002Fmulti-data-input.md). The component renders whatever tables it is handed.\n\n```tsx\nimport type { InteractionEvent } from \"@microsoft\u002Ffabric-visuals-core\";\n\nfunction handleInteraction(source: string, events: InteractionEvent[]) {\n    for (const event of events) {\n        if (event.action === \"select\") {\n            \u002F\u002F event.selections describes the clicked data as predicates\n        } else if (event.action === \"clear\") {\n            \u002F\u002F user deselected (re-clicked same item or clicked empty space)\n        }\n    }\n}\n\n\u003CVegaVisual spec={spec} data={dataTable} theme={theme}\n    onInteraction={(events) => handleInteraction(\"salesChart\", events)} \u002F>\n\u003CDataGrid data={dataTable} theme={theme}\n    onInteraction={(events) => handleInteraction(\"detailTable\", events)} \u002F>\n```\n\n**Key concepts**:\n- Clicking a different data point emits a new `select` (replaces the prior selection — no preceding `clear`).\n- Re-clicking the same item or background space in a vega-lite visual emits `clear`.\n- Predicates include all fields from the datum; consumers filter to the ones that are relevant to them.\n",{"name":5,"description":7},"main","0979439a7a0806abd0ee48c2619b37f297ae1324","samples\u002Funiversal-app\u002Ftemplate\u002F.agents\u002Fskills\u002Fvisuals",77,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-12 01:21:10",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add microsoft\u002Frayfin --skill visuals",{"tool":52,"command":53},"bunx","bunx skills add microsoft\u002Frayfin --skill visuals",{"tool":55,"command":56},"pnpm","pnpm dlx skills add microsoft\u002Frayfin --skill visuals","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin\u002Fblob\u002Fmain\u002Fsamples\u002Funiversal-app\u002Ftemplate\u002F.agents\u002Fskills\u002Fvisuals\u002FSKILL.md",true,[60,66,70,74,78,84,88,92,96,100],{"path":61,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":65},"kit\u002Flib\u002Fto-data-table.spec.ts","SCRIPT","脚本",2889,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin\u002Fblob\u002Fmain\u002Fsamples\u002Funiversal-app\u002Ftemplate\u002F.agents\u002Fskills\u002Fvisuals\u002Fkit\u002Flib\u002Fto-data-table.spec.ts",{"path":67,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":68,"sourceHtmlUrl":69},"kit\u002Flib\u002Fto-data-table.ts",2500,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin\u002Fblob\u002Fmain\u002Fsamples\u002Funiversal-app\u002Ftemplate\u002F.agents\u002Fskills\u002Fvisuals\u002Fkit\u002Flib\u002Fto-data-table.ts",{"path":71,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":72,"sourceHtmlUrl":73},"kit\u002Fscripts\u002Fvalidate-visual.mjs",57272,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin\u002Fblob\u002Fmain\u002Fsamples\u002Funiversal-app\u002Ftemplate\u002F.agents\u002Fskills\u002Fvisuals\u002Fkit\u002Fscripts\u002Fvalidate-visual.mjs",{"path":75,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":76,"sourceHtmlUrl":77},"kit\u002Fscripts\u002Fvalidate.test.mjs",107780,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin\u002Fblob\u002Fmain\u002Fsamples\u002Funiversal-app\u002Ftemplate\u002F.agents\u002Fskills\u002Fvisuals\u002Fkit\u002Fscripts\u002Fvalidate.test.mjs",{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"pack.json","REFERENCE","参考文档",1235,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin\u002Fblob\u002Fmain\u002Fsamples\u002Funiversal-app\u002Ftemplate\u002F.agents\u002Fskills\u002Fvisuals\u002Fpack.json",{"path":85,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fdata-grid-visual.md",5798,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin\u002Fblob\u002Fmain\u002Fsamples\u002Funiversal-app\u002Ftemplate\u002F.agents\u002Fskills\u002Fvisuals\u002Freferences\u002Fdata-grid-visual.md",{"path":89,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fdata-table.md",3922,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin\u002Fblob\u002Fmain\u002Fsamples\u002Funiversal-app\u002Ftemplate\u002F.agents\u002Fskills\u002Fvisuals\u002Freferences\u002Fdata-table.md",{"path":93,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fformatting.md",6465,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin\u002Fblob\u002Fmain\u002Fsamples\u002Funiversal-app\u002Ftemplate\u002F.agents\u002Fskills\u002Fvisuals\u002Freferences\u002Fformatting.md",{"path":97,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Fmulti-data-input.md",5640,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin\u002Fblob\u002Fmain\u002Fsamples\u002Funiversal-app\u002Ftemplate\u002F.agents\u002Fskills\u002Fvisuals\u002Freferences\u002Fmulti-data-input.md",{"path":101,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":102,"sourceHtmlUrl":103},"references\u002Fvega-lite-visual.md",3379,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin\u002Fblob\u002Fmain\u002Fsamples\u002Funiversal-app\u002Ftemplate\u002F.agents\u002Fskills\u002Fvisuals\u002Freferences\u002Fvega-lite-visual.md",[105,118,127,146,154,165],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":32},"01M699YEY2QDVPKTZS3HR9AX84","rayfin-getting-started","Use when starting or creating a NEW Rayfin app, or when a Rayfin task comes up and you are not yet inside a Rayfin project. Gets you into a project with the Rayfin CLI, then hands off to the authoritative, version-locked in-project rayfin skill\u002Fdocs that own all in-project work. Triggers: build a Rayfin app, start a Rayfin project, create a new Rayfin app, create-rayfin, npm create @microsoft\u002Frayfin, rayfin init, scaffold rayfin, rayfin CLI, rayfin template, universal app, awesome-rayfin gallery, get started with Rayfin","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin\u002Fblob\u002Fmain\u002Fskills\u002Frayfin-getting-started\u002FSKILL.md",[],[112,113,114,115,9,116,117],"rayfin getting started","rayfin","scaffold","init","docs","cli",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":32},"01M699YBEP146MJZJNN8YEBZ2G","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\u002Frayfin\u002Fblob\u002Fmain\u002Fsamples\u002Funiversal-app\u002Ftemplate\u002F.agents\u002Fskills\u002Fschema-discovery\u002FSKILL.md",[],[125,126],"schema discovery","dax",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":142,"publishedAt":32},"01M699Y9E80WYFKD1S4MT4B1CS","query-design","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.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin\u002Fblob\u002Fmain\u002Fsamples\u002Funiversal-app\u002Ftemplate\u002F.agents\u002Fskills\u002Fquery-design\u002FSKILL.md",[133,136,139],{"categoryNo":134,"categoryName":135,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":137,"categoryName":138,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":140,"categoryName":141,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师",[143,144,145,126],"design","query design","typescript",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":32},"01M699Y7CKZ55QSYFE827RRVJE","functions-capability","Apply and build the Universal App functions capability. Use for trusted server-side logic, secrets, external APIs, custom model endpoints, published Fabric data agents, webhooks, or privileged operations.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin\u002Fblob\u002Fmain\u002Fsamples\u002Funiversal-app\u002Ftemplate\u002F.agents\u002Fskills\u002Ffunctions-capability\u002FSKILL.md",[],[153],"functions capability",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":32},"01M699Y5R87YE620T78Z30KQSA","fabric-sdk","How to query Fabric data from a running app through the Rayfin connectors client. Use getRayfinClient().connectors.\u003Cname>.executeQuery to run DAX against a semantic model, and toQueryResult to normalize the response.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin\u002Fblob\u002Fmain\u002Fsamples\u002Funiversal-app\u002Ftemplate\u002F.agents\u002Fskills\u002Ffabric-sdk\u002FSKILL.md",[],[161,162,163,113,164,126],"sdk","fabric sdk","connectors","rayfin connectors",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":175,"publishedAt":32},"01M699Y412TNZ8EABAE8TABG0D","fabric-data-agent","Call a published Fabric data agent from a Universal App through a Rayfin function using application auth and MCP streamable HTTP. Use when the request names a Fabric data agent, data-agent MCP endpoint, or asks to chat with governed Fabric data through an app.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin\u002Fblob\u002Fmain\u002Fsamples\u002Funiversal-app\u002Ftemplate\u002F.agents\u002Fskills\u002Ffabric-data-agent\u002FSKILL.md",[171,174],{"categoryNo":172,"categoryName":173,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[176,177,113,178],"fabric data agent","MCP","auth"]