[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699XTVG0Q166E412MW6EC6A":3,"skill-same:01M699XTVG0Q166E412MW6EC6A":81},{"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":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":38,"commitSha":39,"skillDirectory":40,"forksCount":41,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":44,"ownerDescription":45,"updatedAt":46,"install":47,"resources":60},"01M699XTVG0Q166E412MW6EC6A","connectors",null,"Connect a Universal App to existing Fabric data sources: a Warehouse, SQL database, Lakehouse SQL analytics endpoint, or Power BI semantic model. Use whenever the user says \"connect to\", names an existing Fabric item, asks to query data that already exists, or needs to discover available sources. This skill owns the Universal App pack, source routing, and the handoff to the installed Rayfin connector catalog and package docs. It does not cover app-owned CRUD data (use `data-modeling`) or arbitrary external APIs (use `functions-capability`).","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\u002Fconnectors\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[5,29,30,31,32],"handoff","docs","analytics","rayfin","2026-11-10 10:12:30",false,"---\nname: connectors\ndescription: >\n  Connect a Universal App to existing Fabric data sources: a Warehouse, SQL\n  database, Lakehouse SQL analytics endpoint, or Power BI semantic model. Use\n  whenever the user says \"connect to\", names an existing Fabric item, asks to\n  query data that already exists, or needs to discover available sources. This\n  skill owns the Universal App pack, source routing, and the handoff to the\n  installed Rayfin connector catalog and package docs. It does not cover\n  app-owned CRUD data (use `data-modeling`) or arbitrary external APIs (use\n  `functions-capability`).\n---\n\n# Connect to an existing Fabric data source\n\nFirst install the app-side connector support:\n\n```sh\nnpm run pack:add -- connectors\n```\n\nThe `rayfin connector` command group is always available and requires no pack\nor service flag.\nThis pack adds the frontend connector SDK and seeds\n`packages\u002Ffrontend\u002Fsrc\u002Flib\u002Fconnectors.ts` plus the composable Rayfin client.\nIt does not add `services.connectors` or declare a data source.\n`rayfin connector add` owns the top-level `connectors:` configuration and the\nper-source files under `rayfin\u002Fconnectors\u002F`.\nRe-applying the pack is safe.\n\n## Read the live connector contracts\n\nDo not copy connector capabilities, operations, package versions, or client APIs\nfrom this skill.\nRead the installed, version-matched contracts before authoring:\n\n1. Run `npx rayfin connector types --json` for the live type catalog.\n2. Read\n   `node_modules\u002F@microsoft\u002Frayfin-guide\u002Fassets\u002Fdocs\u002Fcli\u002Fconnectors\u002Findex.md`\n   and the page for the command you are about to run.\n3. After `connector add`, read the installed connector package's `package.json`,\n   follow its `rayfinDocs.dir`, and use its entity-generation and typed-client\n   pages.\n\nThe guide routes Category A details to\n`@microsoft\u002Frayfin-connector-fabric-graphql`.\nIts installed docs own `metadata.json`, entity generation, aggregate\n`schema.ts`, authorization, typed queries, and mutation behavior.\n\n## Route by source type\n\n| User's source                                             | Connector type or route                                                 |\n| --------------------------------------------------------- | ----------------------------------------------------------------------- |\n| Fabric Warehouse                                          | `fabric-warehouse`                                                      |\n| Fabric SQL database                                       | `fabric-sqldatabase`                                                    |\n| Lakehouse SQL analytics endpoint                          | `fabric-sqlanalytics`                                                   |\n| Power BI semantic model                                   | `npm run pack:add -- connectors`, then `npm run pack:add -- analytics`  |\n| Kusto \u002F KQL database                                      | Check the live catalog; if it is absent, say it is unavailable and stop |\n| External API, custom model endpoint, or Fabric data agent | `npm run pack:add -- functions`, then follow `functions-capability`     |\n\nThe Lakehouse route is its SQL analytics endpoint, not direct access to files.\nDo not substitute a nearby source type or sample data when the requested type\nis unavailable.\n\n## Discover before connecting\n\nSet `\u003Csource-type>` to the exact value from the table and confirm it still\nappears in `connector types --json`.\nIf the user named a source but did not provide explicit IDs, search for it:\n\n```sh\nnpx rayfin connector search \"\u003Cname>\" --type \u003Csource-type> --all-workspaces --json\n```\n\nBefore deployment there is no workspace scope to infer.\nUse `--all-workspaces` for a tenant-wide scan, or replace it with\n`--workspace-id \u003Cid>` when the workspace is known.\nBoth explicit scopes require `--type`.\nPrefer `--json` so you can compare `displayName`, `workspaceName`,\n`workspaceId`, `itemId`, and `connectorType` without parsing a table.\nEach result also carries a ready-to-run `addCommand`; prefer that command over\nreconstructing `connector add` flags by hand.\n\n- One unambiguous match: use it.\n- Several plausible matches: show the workspace names and ask which one.\n- No match: say what you searched for and ask for a corrected name or explicit\n  IDs.\n\nNever guess a source.\n\n## Add the connector\n\n```sh\nnpx rayfin connector add --type \u003Csource-type> \\\n  --workspace-id \u003CworkspaceId> --item-id \u003CitemId> --name \u003Calias>\n```\n\nUse a short lower-camel-case alias such as `salesWarehouse`.\n`add` records the connection in `rayfin\u002Frayfin.yml`, creates\na placeholder `rayfin\u002Fconnectors\u002F\u003Calias>\u002Fschema.ts` plus `metadata.json` when\nschema discovery succeeds, and prints version-pinned package specifications.\nInstall those exact versions into the frontend workspace from the app root:\n\n```sh\nnpm install -w @rayfin-app\u002Ffrontend \u003Cprinted-packages-and-versions>\n```\n\nDo not install them at the workspace root or create a nested lockfile.\n\n## Generate and wire Category A entities\n\n`connector add` discovers metadata but does not emit the entity files.\nUse `rayfin\u002Fconnectors\u002F\u003Calias>\u002Fmetadata.json` only through the installed\npackage's generation contract.\nFollow the installed\n`@microsoft\u002Frayfin-connector-fabric-graphql` docs to generate only the entities\nthe app needs and replace the placeholder aggregate `schema.ts`.\nDo not recreate those package-owned contracts from memory.\n\nThe CLI-generated `packages\u002Ffrontend\u002Fsrc\u002Flib\u002Fconnectors.ts` carries this\nownership marker:\n\n```ts\n\u002F\u002F @generated by `rayfin connector add` — do not edit below this line.\n```\n\nAfter the aggregate schema exports `\u003CName>Schema` and `connectorConfig`, take\nownership before editing by deleting that generated-marker line.\nThen add the same connector name in all matching locations:\n\n- import `\u003CName>Schema` and `connectorConfig` from the aggregate `schema.ts`;\n- add `\u003Calias>: \u003CName>Schema` to `AppConnectorsSchema`;\n- add `\u003Calias>: connectorConfig` to `connectorConfigs`.\n\nCategory A needs no `connectorRuntimes` entry.\nDo not rerun `rayfin connector add --yes` after authoring entities: `--yes`\nopts in to replacing the hand-authored aggregate `schema.ts` with a placeholder.\nIf the CLI later reports manual wiring, merge its printed maps into the\nBuilder-owned file instead of restoring the generated marker.\n\n## Sample the source before building UI\n\nList the real entities, then sample one through the read-only inspection path:\n\n```sh\nnpx rayfin connector inspect --name \u003Calias>\nnpx rayfin connector inspect --name \u003Calias> --entity \u003Centity> --rows 1\n```\n\nUse the typed client surface documented by the installed connector package for\napplication reads and writes.\nThat is the generated `client.connectors.\u003Calias>.\u003CEntity>` surface, not a raw\nquery operation invented in application code.\nCategory A SQL connectors do not use `connector invoke` as their authoring\nworkflow.\nThis CLI sample proves source access and shape only.\nIt does not replace deployed browser validation from\n[`app-validation`](..\u002Fapp-validation\u002FSKILL.md).\nTreat connector errors as configuration, permissions, or query errors to fix,\nnot warnings to bypass.\n\nAfter wiring application code, run the normal project gates from the workspace\nroot:\n\n```sh\nnpm run typecheck\nnpm run build\nnpm run lint\nnpm test\n```\n\nBefore browser validation, follow the connector deployment-outcome invariant in\n[`app-deployment`](..\u002Fapp-deployment\u002FSKILL.md).\nDo not treat overall `rayfin up` success as proof that a required connector was\ngenerated and applied.\n","# Connect to an existing Fabric data source\n\nFirst install the app-side connector support:\n\n```sh\nnpm run pack:add -- connectors\n```\n\nThe `rayfin connector` command group is always available and requires no pack\nor service flag.\nThis pack adds the frontend connector SDK and seeds\n`packages\u002Ffrontend\u002Fsrc\u002Flib\u002Fconnectors.ts` plus the composable Rayfin client.\nIt does not add `services.connectors` or declare a data source.\n`rayfin connector add` owns the top-level `connectors:` configuration and the\nper-source files under `rayfin\u002Fconnectors\u002F`.\nRe-applying the pack is safe.\n\n## Read the live connector contracts\n\nDo not copy connector capabilities, operations, package versions, or client APIs\nfrom this skill.\nRead the installed, version-matched contracts before authoring:\n\n1. Run `npx rayfin connector types --json` for the live type catalog.\n2. Read\n   `node_modules\u002F@microsoft\u002Frayfin-guide\u002Fassets\u002Fdocs\u002Fcli\u002Fconnectors\u002Findex.md`\n   and the page for the command you are about to run.\n3. After `connector add`, read the installed connector package's `package.json`,\n   follow its `rayfinDocs.dir`, and use its entity-generation and typed-client\n   pages.\n\nThe guide routes Category A details to\n`@microsoft\u002Frayfin-connector-fabric-graphql`.\nIts installed docs own `metadata.json`, entity generation, aggregate\n`schema.ts`, authorization, typed queries, and mutation behavior.\n\n## Route by source type\n\n| User's source                                             | Connector type or route                                                 |\n| --------------------------------------------------------- | ----------------------------------------------------------------------- |\n| Fabric Warehouse                                          | `fabric-warehouse`                                                      |\n| Fabric SQL database                                       | `fabric-sqldatabase`                                                    |\n| Lakehouse SQL analytics endpoint                          | `fabric-sqlanalytics`                                                   |\n| Power BI semantic model                                   | `npm run pack:add -- connectors`, then `npm run pack:add -- analytics`  |\n| Kusto \u002F KQL database                                      | Check the live catalog; if it is absent, say it is unavailable and stop |\n| External API, custom model endpoint, or Fabric data agent | `npm run pack:add -- functions`, then follow `functions-capability`     |\n\nThe Lakehouse route is its SQL analytics endpoint, not direct access to files.\nDo not substitute a nearby source type or sample data when the requested type\nis unavailable.\n\n## Discover before connecting\n\nSet `\u003Csource-type>` to the exact value from the table and confirm it still\nappears in `connector types --json`.\nIf the user named a source but did not provide explicit IDs, search for it:\n\n```sh\nnpx rayfin connector search \"\u003Cname>\" --type \u003Csource-type> --all-workspaces --json\n```\n\nBefore deployment there is no workspace scope to infer.\nUse `--all-workspaces` for a tenant-wide scan, or replace it with\n`--workspace-id \u003Cid>` when the workspace is known.\nBoth explicit scopes require `--type`.\nPrefer `--json` so you can compare `displayName`, `workspaceName`,\n`workspaceId`, `itemId`, and `connectorType` without parsing a table.\nEach result also carries a ready-to-run `addCommand`; prefer that command over\nreconstructing `connector add` flags by hand.\n\n- One unambiguous match: use it.\n- Several plausible matches: show the workspace names and ask which one.\n- No match: say what you searched for and ask for a corrected name or explicit\n  IDs.\n\nNever guess a source.\n\n## Add the connector\n\n```sh\nnpx rayfin connector add --type \u003Csource-type> \\\n  --workspace-id \u003CworkspaceId> --item-id \u003CitemId> --name \u003Calias>\n```\n\nUse a short lower-camel-case alias such as `salesWarehouse`.\n`add` records the connection in `rayfin\u002Frayfin.yml`, creates\na placeholder `rayfin\u002Fconnectors\u002F\u003Calias>\u002Fschema.ts` plus `metadata.json` when\nschema discovery succeeds, and prints version-pinned package specifications.\nInstall those exact versions into the frontend workspace from the app root:\n\n```sh\nnpm install -w @rayfin-app\u002Ffrontend \u003Cprinted-packages-and-versions>\n```\n\nDo not install them at the workspace root or create a nested lockfile.\n\n## Generate and wire Category A entities\n\n`connector add` discovers metadata but does not emit the entity files.\nUse `rayfin\u002Fconnectors\u002F\u003Calias>\u002Fmetadata.json` only through the installed\npackage's generation contract.\nFollow the installed\n`@microsoft\u002Frayfin-connector-fabric-graphql` docs to generate only the entities\nthe app needs and replace the placeholder aggregate `schema.ts`.\nDo not recreate those package-owned contracts from memory.\n\nThe CLI-generated `packages\u002Ffrontend\u002Fsrc\u002Flib\u002Fconnectors.ts` carries this\nownership marker:\n\n```ts\n\u002F\u002F @generated by `rayfin connector add` — do not edit below this line.\n```\n\nAfter the aggregate schema exports `\u003CName>Schema` and `connectorConfig`, take\nownership before editing by deleting that generated-marker line.\nThen add the same connector name in all matching locations:\n\n- import `\u003CName>Schema` and `connectorConfig` from the aggregate `schema.ts`;\n- add `\u003Calias>: \u003CName>Schema` to `AppConnectorsSchema`;\n- add `\u003Calias>: connectorConfig` to `connectorConfigs`.\n\nCategory A needs no `connectorRuntimes` entry.\nDo not rerun `rayfin connector add --yes` after authoring entities: `--yes`\nopts in to replacing the hand-authored aggregate `schema.ts` with a placeholder.\nIf the CLI later reports manual wiring, merge its printed maps into the\nBuilder-owned file instead of restoring the generated marker.\n\n## Sample the source before building UI\n\nList the real entities, then sample one through the read-only inspection path:\n\n```sh\nnpx rayfin connector inspect --name \u003Calias>\nnpx rayfin connector inspect --name \u003Calias> --entity \u003Centity> --rows 1\n```\n\nUse the typed client surface documented by the installed connector package for\napplication reads and writes.\nThat is the generated `client.connectors.\u003Calias>.\u003CEntity>` surface, not a raw\nquery operation invented in application code.\nCategory A SQL connectors do not use `connector invoke` as their authoring\nworkflow.\nThis CLI sample proves source access and shape only.\nIt does not replace deployed browser validation from\n[`app-validation`](..\u002Fapp-validation\u002FSKILL.md).\nTreat connector errors as configuration, permissions, or query errors to fix,\nnot warnings to bypass.\n\nAfter wiring application code, run the normal project gates from the workspace\nroot:\n\n```sh\nnpm run typecheck\nnpm run build\nnpm run lint\nnpm test\n```\n\nBefore browser validation, follow the connector deployment-outcome invariant in\n[`app-deployment`](..\u002Fapp-deployment\u002FSKILL.md).\nDo not treat overall `rayfin up` success as proof that a required connector was\ngenerated and applied.\n",{"name":5,"description":7},"main","0979439a7a0806abd0ee48c2619b37f297ae1324","samples\u002Funiversal-app\u002Ftemplate\u002F.agents\u002Fskills\u002Fconnectors",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":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add microsoft\u002Frayfin --skill connectors",{"tool":53,"command":54},"bunx","bunx skills add microsoft\u002Frayfin --skill connectors",{"tool":56,"command":57},"pnpm","pnpm dlx skills add microsoft\u002Frayfin --skill connectors","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin\u002Fblob\u002Fmain\u002Fsamples\u002Funiversal-app\u002Ftemplate\u002F.agents\u002Fskills\u002Fconnectors\u002FSKILL.md",true,[61,67,71,75],{"path":62,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},"kit\u002Fconnectors.ts","SCRIPT","脚本",738,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin\u002Fblob\u002Fmain\u002Fsamples\u002Funiversal-app\u002Ftemplate\u002F.agents\u002Fskills\u002Fconnectors\u002Fkit\u002Fconnectors.ts",{"path":68,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":69,"sourceHtmlUrl":70},"kit\u002Frayfin-client.ts",2268,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin\u002Fblob\u002Fmain\u002Fsamples\u002Funiversal-app\u002Ftemplate\u002F.agents\u002Fskills\u002Fconnectors\u002Fkit\u002Frayfin-client.ts",{"path":72,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":73,"sourceHtmlUrl":74},"kit\u002Frayfin-client.with-functions.ts",2344,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin\u002Fblob\u002Fmain\u002Fsamples\u002Funiversal-app\u002Ftemplate\u002F.agents\u002Fskills\u002Fconnectors\u002Fkit\u002Frayfin-client.with-functions.ts",{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"pack.json","REFERENCE","参考文档",2866,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin\u002Fblob\u002Fmain\u002Fsamples\u002Funiversal-app\u002Ftemplate\u002F.agents\u002Fskills\u002Fconnectors\u002Fpack.json",[82,93,107,116,135,143],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":33},"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",[],[89,32,90,91,9,30,92],"rayfin getting started","scaffold","init","cli",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":103,"publishedAt":33},"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",[99,102],{"categoryNo":100,"categoryName":101,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[95,104,105,106],"components","dashboard","visualize",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":33},"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",[],[114,115],"schema discovery","dax",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":131,"publishedAt":33},"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",[122,125,128],{"categoryNo":123,"categoryName":124,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":126,"categoryName":127,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":129,"categoryName":130,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师",[132,133,115,134],"query design","design","typescript",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":33},"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",[],[142],"functions capability",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":33},"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",[],[150,151,115,152,32,5],"sdk","fabric sdk","rayfin connectors"]