[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699Y5R87YE620T78Z30KQSA":3,"skill-same:01M699Y5R87YE620T78Z30KQSA":73},{"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":25,"linkOnly":26,"markdownContent":27,"markdownBody":28,"frontMatter":29,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":36,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M699Y5R87YE620T78Z30KQSA","fabric-sdk",null,"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.","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\u002Ffabric-sdk\u002FSKILL.md",[],[19,20,21,22,23,24],"sdk","fabric sdk","dax","rayfin connectors","rayfin","connectors","2026-11-10 10:12:30",false,"---\nname: fabric-sdk\ndescription: >\n  How to query Fabric data from a running app through the Rayfin connectors\n  client. Use getRayfinClient().connectors.\u003Cname>.executeQuery to run DAX\n  against a semantic model, and toQueryResult to normalize the response.\n---\n\n# Fabric Data Access at Runtime\n\n## Overview\n\nThe app reaches Fabric through the Rayfin connectors client. Each connector\nis declared in `rayfin.yml` and surfaced as\n`getRayfinClient().connectors.\u003Cname>`, with operations typed by the connector\nmarker package.\n\nThe connector's `workspaceId` and `itemId` are injected server-side from\n`rayfin.yml`. The app sends only the query, so no ids reach the bundle and\nthere is no generated config to keep in sync.\n\n## Quick Start\n\nPrefer the hook. It normalizes the response and never throws — but it reports\nfailures on two channels, so check `error` as well as `data.status`:\n\n```typescript\nimport { useSemanticModelQuery } from \"@\u002Fhooks\u002Fuse-semantic-model-query\";\n\nconst { data, isLoading, error, refetch } = useSemanticModelQuery({\n  connection: \"sales\",\n  query: 'EVALUATE SUMMARIZECOLUMNS(Product[Category], \"Total\", [Sales Amount])',\n});\n\nif (error) {\n  \u002F\u002F The connector threw: transport, auth, or server failure.\n  \u002F\u002F `data` is undefined here, so checking only data.status renders nothing.\n  \u002F\u002F error.message\n} else if (data?.status === \"success\") {\n  \u002F\u002F data.table.columns — [{ name, dataType }]\n  \u002F\u002F data.table.rows    — unknown[][]\n} else if (data?.status === \"error\") {\n  \u002F\u002F The query reached Power BI and failed there.\n  \u002F\u002F data.error.category — \"api\" | \"query\" | \"network\" | \"overflow\" | \"unknown\"\n  \u002F\u002F data.error.message\n}\n```\n\nDrop to the client only when you need something the hook does not expose:\n\n```typescript\nimport { toQueryResult } from \"@microsoft\u002Frayfin-connector-fabric-semanticmodel\";\nimport { getRayfinClient } from \"@\u002Flib\u002Frayfin-client\";\n\n\u002F\u002F `getRayfinClient` is async in this template, so await it into a variable\n\u002F\u002F first — `await client().connectors` would read `.connectors` off the Promise.\nconst client = await getRayfinClient();\nconst response = await client.connectors.sales.executeQuery({\n  query: \"EVALUATE ...\",\n});\nconst result = toQueryResult(response);\n```\n\n## Key Concepts\n\n### Declaring connectors\n\nConnectors come from `rayfin\u002Frayfin.yml`, managed by `rayfin connector add`. See\n`AGENTS.md` to register one, and the `rayfin-connectors` skill that `add`\ninstalls for the YAML schema. `AppConnectorsSchema` in\n`packages\u002Ffrontend\u002Fsrc\u002Flib\u002Fconnectors.ts` types the names; it accepts any string\nby default, so adding a connector needs no code change.\n\n### Querying\n\nOne operation for DAX:\n\n```typescript\nconst client = await getRayfinClient();\nawait client.connectors[name].executeQuery({ query });\n```\n\nEach query must contain exactly one `EVALUATE` statement.\n\n### Bounding rows\n\nThere is no default row cap, so bound the DAX with an aggregation or `TOPN(...)`.\n\nThe connector's `executeQuery` will also accept an optional\n`resultSetRowCountLimit` alongside `query`. Prefer that over `TOPN(...)` when you\nwant a guard rather than a deliberately ranked subset: exceeding it fails the\nquery with an `overflow` error, so a truncated result announces itself, where\n`TOPN` returns a complete-looking partial answer.\n\n`useSemanticModelQuery` does not forward the field, so from app code shape the\nDAX itself. The CLI's `invoke` accepts it.\n\n### The connector throws, the hook does not\n\nThis is the one behavior that trips people up.\n\n`executeQuery` **throws** on wiring, transport, auth, and server failures. A\nquery that reaches Power BI and fails there does not throw; it resolves with the\nerror nested in the response body.\n\n`useSemanticModelQuery` catches the throw rather than re-throwing, and keeps the\ntwo **disjoint**, so a hook caller has two channels and each is reachable:\n\n- `error` — what was thrown, surfaced as-is so its status and service code\n  survive. `data` is cleared when this is set.\n- `data.status === \"error\"` — what Power BI returned, already categorised.\n  `error` stays `undefined` for these.\n\nA component that checks only one renders nothing for half its failures. Check\nboth — the order does not matter, because they never both apply:\n\n```tsx\nif (error) return \u003CError message={error.message} \u002F>;\nif (data?.status === \"error\") return \u003CError message={data.error.message} \u002F>;\nif (isLoading || !data) return \u003CSpinner \u002F>;\n\u002F\u002F data.status === \"success\"\n```\n\nIf you call the client directly, the same two cases arrive as a throw and a\nresolved error result:\n\n```typescript\ntry {\n  const result = toQueryResult(await connector.executeQuery({ query }));\n  if (result.status === \"error\") { \u002F* Power BI rejected the query *\u002F }\n} catch (err) {\n  \u002F* never reached Power BI *\u002F\n}\n```\n\n### Result Handling\n\n`toQueryResult` returns a discriminated union on `status`. On success the\n`table` has:\n- `columns`: `Array\u003C{ name: string, dataType: string }>`\n- `rows`: `unknown[][]`, row-major, values aligned with `columns` by index\n\n```typescript\n\u002F\u002F result.table.columns = [{ name: \"Product[Name]\", dataType: \"unknown\" },\n\u002F\u002F                          { name: \"[Sales]\", dataType: \"unknown\" }]\n\u002F\u002F result.table.rows    = [[\"Widget\", 42], [\"Gadget\", 17]]\n```\n\n**Do not branch on `dataType`.** It is `\"unknown\"` whenever the payload carries\nno column metadata, which is the common in-app case: column names are then\ninferred from the first row. Supply display types yourself through\n`columnMetadata` and `toDataTable`.\n\nBecause names are inferred from the first row in that fallback, a query whose\nfirst row omits a column (or returns no rows) yields no columns for it. Shape\nthe DAX so every column is present in the first row.\n\n### Caching\n\nThere is none. The connectors client does not cache, and this template does not\nadd one — every call reaches Power BI.\n\nIf a screen re-queries more than you want, hold the result in state or memoize at\nthe call site. Don't introduce a shared, process-global store without a\nper-principal key and a TTL: without the first it serves one user's rows to the\nnext after a sign-in change, and without the second it serves stale rows after a\nmodel refresh.\n\n### Error Categories\n\n| Category | Meaning | Example |\n|----------|---------|---------|\n| `query` | Invalid DAX | `\"Syntax error at position 18\"` |\n| `overflow` | Row or byte cap exceeded, data truncated | `\"More than 1000000 rows in a query result\"` |\n| `api` | Auth or dataset-level failure — usually needs you to change something | 401 Unauthorized |\n| `network` | The request never left the machine — worth retrying as-is | Connection reset |\n| `unknown` | Could not categorize | Parse failure |\n\nThese are the categories the connector puts on a **returned** result\n(`data.status === \"error\"`). A failure that never reached Power BI — a wiring\nmistake, transport, or auth — is thrown instead and arrives on the hook's `error`,\nwith the original on `error.cause`.\n\n`overflow` means the result is **truncated but present**. Treat it as a\nfailure rather than rendering partial data as if it were complete.\n\n## Common Patterns\n\n### Multiple models\n\n```typescript\nconst sales = useSemanticModelQuery({ connection: \"sales\", query: salesDax });\nconst inventory = useSemanticModelQuery({ connection: \"inventory\", query: invDax });\n```\n\n### Re-running a query\n\n```typescript\nconst { data, refetch } = useSemanticModelQuery({ connection: \"sales\", query });\nawait refetch();\n```\n\n## Anti-Patterns\n\n- **Don't branch on `dataType`** — it is `\"unknown\"` whenever column metadata was absent and names had to be inferred from the first row.\n- **Don't treat a resolved promise as success** — check `status`.\n- **Don't send `workspaceId` or `itemId`** — they come from `rayfin.yml` server-side.\n- **Don't read only one error channel** — a thrown failure leaves `data` undefined, so a component that checks only `data.status` renders nothing and looks broken.\n- **Don't return unbounded results** — there is no default row cap. Bound the DAX with an aggregation or `TOPN(...)`.\n\n## Type Reference\n\n```typescript\nimport type {\n  ExecuteQueryInput,\n  FabricSemanticModelTabularResponse,\n  SemanticModelQueryResult,\n  QueryTable,\n  QueryColumn,\n  QueryError,\n} from \"@microsoft\u002Frayfin-connector-fabric-semanticmodel\";\n```\n\nFor full type definitions, see `references\u002Ftypes.md` in this skill.\n","# Fabric Data Access at Runtime\n\n## Overview\n\nThe app reaches Fabric through the Rayfin connectors client. Each connector\nis declared in `rayfin.yml` and surfaced as\n`getRayfinClient().connectors.\u003Cname>`, with operations typed by the connector\nmarker package.\n\nThe connector's `workspaceId` and `itemId` are injected server-side from\n`rayfin.yml`. The app sends only the query, so no ids reach the bundle and\nthere is no generated config to keep in sync.\n\n## Quick Start\n\nPrefer the hook. It normalizes the response and never throws — but it reports\nfailures on two channels, so check `error` as well as `data.status`:\n\n```typescript\nimport { useSemanticModelQuery } from \"@\u002Fhooks\u002Fuse-semantic-model-query\";\n\nconst { data, isLoading, error, refetch } = useSemanticModelQuery({\n  connection: \"sales\",\n  query: 'EVALUATE SUMMARIZECOLUMNS(Product[Category], \"Total\", [Sales Amount])',\n});\n\nif (error) {\n  \u002F\u002F The connector threw: transport, auth, or server failure.\n  \u002F\u002F `data` is undefined here, so checking only data.status renders nothing.\n  \u002F\u002F error.message\n} else if (data?.status === \"success\") {\n  \u002F\u002F data.table.columns — [{ name, dataType }]\n  \u002F\u002F data.table.rows    — unknown[][]\n} else if (data?.status === \"error\") {\n  \u002F\u002F The query reached Power BI and failed there.\n  \u002F\u002F data.error.category — \"api\" | \"query\" | \"network\" | \"overflow\" | \"unknown\"\n  \u002F\u002F data.error.message\n}\n```\n\nDrop to the client only when you need something the hook does not expose:\n\n```typescript\nimport { toQueryResult } from \"@microsoft\u002Frayfin-connector-fabric-semanticmodel\";\nimport { getRayfinClient } from \"@\u002Flib\u002Frayfin-client\";\n\n\u002F\u002F `getRayfinClient` is async in this template, so await it into a variable\n\u002F\u002F first — `await client().connectors` would read `.connectors` off the Promise.\nconst client = await getRayfinClient();\nconst response = await client.connectors.sales.executeQuery({\n  query: \"EVALUATE ...\",\n});\nconst result = toQueryResult(response);\n```\n\n## Key Concepts\n\n### Declaring connectors\n\nConnectors come from `rayfin\u002Frayfin.yml`, managed by `rayfin connector add`. See\n`AGENTS.md` to register one, and the `rayfin-connectors` skill that `add`\ninstalls for the YAML schema. `AppConnectorsSchema` in\n`packages\u002Ffrontend\u002Fsrc\u002Flib\u002Fconnectors.ts` types the names; it accepts any string\nby default, so adding a connector needs no code change.\n\n### Querying\n\nOne operation for DAX:\n\n```typescript\nconst client = await getRayfinClient();\nawait client.connectors[name].executeQuery({ query });\n```\n\nEach query must contain exactly one `EVALUATE` statement.\n\n### Bounding rows\n\nThere is no default row cap, so bound the DAX with an aggregation or `TOPN(...)`.\n\nThe connector's `executeQuery` will also accept an optional\n`resultSetRowCountLimit` alongside `query`. Prefer that over `TOPN(...)` when you\nwant a guard rather than a deliberately ranked subset: exceeding it fails the\nquery with an `overflow` error, so a truncated result announces itself, where\n`TOPN` returns a complete-looking partial answer.\n\n`useSemanticModelQuery` does not forward the field, so from app code shape the\nDAX itself. The CLI's `invoke` accepts it.\n\n### The connector throws, the hook does not\n\nThis is the one behavior that trips people up.\n\n`executeQuery` **throws** on wiring, transport, auth, and server failures. A\nquery that reaches Power BI and fails there does not throw; it resolves with the\nerror nested in the response body.\n\n`useSemanticModelQuery` catches the throw rather than re-throwing, and keeps the\ntwo **disjoint**, so a hook caller has two channels and each is reachable:\n\n- `error` — what was thrown, surfaced as-is so its status and service code\n  survive. `data` is cleared when this is set.\n- `data.status === \"error\"` — what Power BI returned, already categorised.\n  `error` stays `undefined` for these.\n\nA component that checks only one renders nothing for half its failures. Check\nboth — the order does not matter, because they never both apply:\n\n```tsx\nif (error) return \u003CError message={error.message} \u002F>;\nif (data?.status === \"error\") return \u003CError message={data.error.message} \u002F>;\nif (isLoading || !data) return \u003CSpinner \u002F>;\n\u002F\u002F data.status === \"success\"\n```\n\nIf you call the client directly, the same two cases arrive as a throw and a\nresolved error result:\n\n```typescript\ntry {\n  const result = toQueryResult(await connector.executeQuery({ query }));\n  if (result.status === \"error\") { \u002F* Power BI rejected the query *\u002F }\n} catch (err) {\n  \u002F* never reached Power BI *\u002F\n}\n```\n\n### Result Handling\n\n`toQueryResult` returns a discriminated union on `status`. On success the\n`table` has:\n- `columns`: `Array\u003C{ name: string, dataType: string }>`\n- `rows`: `unknown[][]`, row-major, values aligned with `columns` by index\n\n```typescript\n\u002F\u002F result.table.columns = [{ name: \"Product[Name]\", dataType: \"unknown\" },\n\u002F\u002F                          { name: \"[Sales]\", dataType: \"unknown\" }]\n\u002F\u002F result.table.rows    = [[\"Widget\", 42], [\"Gadget\", 17]]\n```\n\n**Do not branch on `dataType`.** It is `\"unknown\"` whenever the payload carries\nno column metadata, which is the common in-app case: column names are then\ninferred from the first row. Supply display types yourself through\n`columnMetadata` and `toDataTable`.\n\nBecause names are inferred from the first row in that fallback, a query whose\nfirst row omits a column (or returns no rows) yields no columns for it. Shape\nthe DAX so every column is present in the first row.\n\n### Caching\n\nThere is none. The connectors client does not cache, and this template does not\nadd one — every call reaches Power BI.\n\nIf a screen re-queries more than you want, hold the result in state or memoize at\nthe call site. Don't introduce a shared, process-global store without a\nper-principal key and a TTL: without the first it serves one user's rows to the\nnext after a sign-in change, and without the second it serves stale rows after a\nmodel refresh.\n\n### Error Categories\n\n| Category | Meaning | Example |\n|----------|---------|---------|\n| `query` | Invalid DAX | `\"Syntax error at position 18\"` |\n| `overflow` | Row or byte cap exceeded, data truncated | `\"More than 1000000 rows in a query result\"` |\n| `api` | Auth or dataset-level failure — usually needs you to change something | 401 Unauthorized |\n| `network` | The request never left the machine — worth retrying as-is | Connection reset |\n| `unknown` | Could not categorize | Parse failure |\n\nThese are the categories the connector puts on a **returned** result\n(`data.status === \"error\"`). A failure that never reached Power BI — a wiring\nmistake, transport, or auth — is thrown instead and arrives on the hook's `error`,\nwith the original on `error.cause`.\n\n`overflow` means the result is **truncated but present**. Treat it as a\nfailure rather than rendering partial data as if it were complete.\n\n## Common Patterns\n\n### Multiple models\n\n```typescript\nconst sales = useSemanticModelQuery({ connection: \"sales\", query: salesDax });\nconst inventory = useSemanticModelQuery({ connection: \"inventory\", query: invDax });\n```\n\n### Re-running a query\n\n```typescript\nconst { data, refetch } = useSemanticModelQuery({ connection: \"sales\", query });\nawait refetch();\n```\n\n## Anti-Patterns\n\n- **Don't branch on `dataType`** — it is `\"unknown\"` whenever column metadata was absent and names had to be inferred from the first row.\n- **Don't treat a resolved promise as success** — check `status`.\n- **Don't send `workspaceId` or `itemId`** — they come from `rayfin.yml` server-side.\n- **Don't read only one error channel** — a thrown failure leaves `data` undefined, so a component that checks only `data.status` renders nothing and looks broken.\n- **Don't return unbounded results** — there is no default row cap. Bound the DAX with an aggregation or `TOPN(...)`.\n\n## Type Reference\n\n```typescript\nimport type {\n  ExecuteQueryInput,\n  FabricSemanticModelTabularResponse,\n  SemanticModelQueryResult,\n  QueryTable,\n  QueryColumn,\n  QueryError,\n} from \"@microsoft\u002Frayfin-connector-fabric-semanticmodel\";\n```\n\nFor full type definitions, see `references\u002Ftypes.md` in this skill.\n",{"name":5,"description":7},"main","0979439a7a0806abd0ee48c2619b37f297ae1324","samples\u002Funiversal-app\u002Ftemplate\u002F.agents\u002Fskills\u002Ffabric-sdk",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":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add microsoft\u002Frayfin --skill fabric-sdk",{"tool":45,"command":46},"bunx","bunx skills add microsoft\u002Frayfin --skill fabric-sdk",{"tool":48,"command":49},"pnpm","pnpm dlx skills add microsoft\u002Frayfin --skill fabric-sdk","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin\u002Fblob\u002Fmain\u002Fsamples\u002Funiversal-app\u002Ftemplate\u002F.agents\u002Fskills\u002Ffabric-sdk\u002FSKILL.md",true,[53,59,63,69],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"package.json","REFERENCE","参考文档",23,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fagent-transcript\u002Fpackage.json",{"path":60,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Ftypes.md",3465,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin\u002Fblob\u002Fmain\u002Fsamples\u002Funiversal-app\u002Ftemplate\u002F.agents\u002Fskills\u002Ffabric-sdk\u002Freferences\u002Ftypes.md",{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"scripts\u002Fagent-transcript","SCRIPT","脚本",34195,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fagent-transcript\u002Fscripts\u002Fagent-transcript",{"path":70,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":71,"sourceHtmlUrl":72},"scripts\u002Fagent-transcript.test.mjs",18190,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fagent-transcript\u002Fscripts\u002Fagent-transcript.test.mjs",[74,86,106,114,133,141],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":25},"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",[],[81,23,82,83,9,84,85],"rayfin getting started","scaffold","init","docs","cli",{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":102,"publishedAt":25},"01M699YCN4ZDW2AMDP4NVJ2QGC","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 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.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin\u002Fblob\u002Fmain\u002Fsamples\u002Funiversal-app\u002Ftemplate\u002F.agents\u002Fskills\u002Fvisuals\u002FSKILL.md",[92,97],{"categoryNo":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000013","分析与可视化","SCENARIO","使用场景",{"categoryNo":98,"categoryName":99,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[88,103,104,105],"visualize","components","dashboard",{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":25},"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",[],[113,21],"schema discovery",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":129,"publishedAt":25},"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",[120,123,126],{"categoryNo":121,"categoryName":122,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":124,"categoryName":125,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":127,"categoryName":128,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000032","设计师",[130,131,21,132],"design","query design","typescript",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":25},"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",[],[140],"functions capability",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":151,"publishedAt":25},"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",[147,150],{"categoryNo":148,"categoryName":149,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":98,"categoryName":99,"taxonomyType":100,"taxonomyTypeDesc":101},[152,153,23,154],"fabric data agent","MCP","auth"]