[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699X4DFG738655HE21MQDWE":3,"skill-same:01M699X4DFG738655HE21MQDWE":64},{"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":23,"publishedAt":30,"linkOnly":31,"markdownContent":32,"markdownBody":33,"frontMatter":34,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":41,"ownerDescription":42,"updatedAt":43,"install":44,"resources":57},"01M699X4DFG738655HE21MQDWE","app-validation",null,"What to validate and how to drive Playwright for this template's app.  Use alongside the playwright-cli skill — playwright-cli covers the tool's  commands; this skill covers performance rules, the required validation checklist,  the Fabric portal embed flow, and spec file guidance.","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\u002Fdata-app\u002F.agents\u002Fskills\u002Fapp-validation\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[24,25,26,27,28,29],"app validation","cli","spec","performance","playwright","validate","2026-11-10 10:12:30",false,"---\nname: app-validation\ndescription: >\n  What to validate and how to drive Playwright for this template's app. \n  Use alongside the playwright-cli skill — playwright-cli covers the tool's \n  commands; this skill covers performance rules, the required validation checklist, \n  the Fabric portal embed flow, and spec file guidance.\n---\n\n# App Validation\n\nUse this skill **together with** the [playwright-cli](..\u002Fplaywright-cli\u002FSKILL.md) skill when validating the running app in a browser. The playwright-cli skill is upstream-managed and only covers the tool itself; this skill captures everything specific to this template. This app can **only** be tested and validated with the Fabric portal embed flow. See [Testing inside the Fabric portal embed](#testing-inside-the-fabric-portal-embed).\n**NEVER** test directly against `localhost` - the app will not work correctly.\n\n## Performance Rules\n\n### Use minimal initial_wait\n\n**Always use `initial_wait: 1`** for all playwright-cli tool calls to avoid unnecessary delays. Do not increase it unless explicitly required.\n\n> **Carve-out:** the **first** `open` against the Fabric portal embed (`*.fabric.microsoft.com\u002F...?devUri=...`) takes 20–40s to render the appbackend chrome. Use `initial_wait: 30` once for that call, then `1` afterward. See [Testing inside the Fabric portal embed](#testing-inside-the-fabric-portal-embed).\n\n### Skip auth — always\n\n**NEVER interact with or validate the token\u002Fauth prompt page.** Inside your `run-code` call, inject the auth token via `sessionStorage.setItem` (or `localStorage.setItem`) and mock API responses with `page.route()` **before** calling `page.reload()`. The app must skip the auth prompt and render actual content immediately.\n\n> **Carve-out:** this rule applies to apps that gate themselves behind a token check the agent controls. For real AAD redirects (e.g. the Fabric portal sign-in flow at `login.microsoftonline.com`), do **not** click sign-in buttons or fill credentials, and do **not** mock `sessionStorage` — use a `--persistent` profile instead so the user signs in once and cookies replay on subsequent runs. See [Testing inside the Fabric portal embed](#testing-inside-the-fabric-portal-embed).\n\n### Skip screenshots unless asked\n\nOnly take a screenshot if the user explicitly requests one. Use `snapshot` (YAML accessibility tree) for validation.\n\n## Required Checks\n\n- UI elements render correctly and are visible.\n- Text meets accessibility standards.\n- No console errors from the app. Ignore Fabric portal noise - see [console-error-filter](#console-error-filter).\n\n## Visual Consistency Checks\n\n- Verify key layout containers have non-zero computed padding and gap values. Zero spacing usually indicates an invalid token class mapping.\n- Verify chart background matches parent card background color.\n- Verify bar and arc stroke colors match card background (not primary text color).\n- Verify axis label and data-label colors are consistent across charts using shared foreground-secondary semantics.\n- Verify grouped\u002Fmulti-series bar charts do not show auto-injected data labels unless explicitly requested by design.\n- Verify chart render height is healthy for each chart canvas\u002FSVG. Treat charts rendering below ~100px as suspicious and below ~50px as likely squished.\n- Verify standalone (non-grid) chart sections use definite `height` instead of only `minHeight` when chart wrappers use `h-full`.\n- Compare computed `fontSize`, `fontFamily`, and `color` across related `input`, `select`, and `button` controls in the same toolbar\u002Ffilter row.\n- Include a `page.evaluate` style check in validation runs that reports spacing\u002Ftoken and form typography mismatches as structured failures.\n- Include a `page.evaluate` chart-height check that inspects chart canvas\u002FSVG client heights and reports squished-chart mismatches.\n\n## Testing inside the Fabric portal embed\n\nThe URL under test should be `*.fabric.microsoft.com` and contain `devUri=`, so the app is being rendered **inside the Fabric portal as a deeply-nested iframe** (`portal → *pbiabd.powerbi.com\u002Fappbackend → http:\u002F\u002Flocalhost:5173`). Use the template's wired-up flow instead of the generic `open` recipe.\n\n### One-liner\n\n```bash\nnpm run test:fabric\n```\n\nThis runs `scripts\u002Fopen-fabric-portal.mjs` which composes the embed URL from the `VITE_FABRIC_*` env vars (written into `.env.local` \u002F `.env.fabric` by `npx rayfin up`) and launches a named persistent session with the right Chromium flags:\n\n```bash\nplaywright-cli -s=fabric open --persistent --config=.playwright-config.json \"\u003Cembed-url>\"\n```\n\n### Why three pieces are required\n\n| Piece | Reason |\n| --- | --- |\n| `--persistent` profile | Real AAD sign-in cannot be mocked. The user signs in once; cookies persist for subsequent `playwright-cli -s=fabric open` calls. |\n| `.playwright-config.json` Chromium flag | Disables `BlockInsecurePrivateNetworkRequests` \u002F `LocalNetworkAccessChecks` so the HTTPS Fabric portal can iframe `http:\u002F\u002Flocalhost:5173`. Header-based opt-in does **not** work for top-level iframe navigations. |\n| Vite `localNetworkAccessPlugin` | Sends `Access-Control-Allow-Private-Network: true` and answers LNA preflights, so fetch\u002FXHR subresources from the embedded app pass. Belt-and-suspenders with the browser flag. |\n\n### Frame discovery snippet\n\nThe app loads three frames deep. Use this single `run-code` to locate it:\n\n```js\nasync page => {\n  await page.waitForFunction(\n    () => Array.from(document.querySelectorAll('iframe')).some(i => i.src.includes('localhost:5173')),\n    { timeout: 30000 }\n  );\n  await page.waitForTimeout(3000);\n  const f = page.frames().find(x => x.url().startsWith('http:\u002F\u002Flocalhost:5173'));\n  const errFrame = page.frames().find(x => x.url().startsWith('chrome-error'));\n  return {\n    loaded: !!f,\n    blockedByLNA: !!errFrame,\n    title: f ? await f.title() : null,\n  };\n}\n```\n\nIf `blockedByLNA: true`, the Chromium flag isn't taking effect — confirm `--config=.playwright-config.json` was passed.\n\n### Console error filter\n\nThe Fabric portal emits its own errors that are **not app bugs**. Treat as portal noise (ignore) - only errors where the source URL starts with `http:\u002F\u002Flocalhost:5173` count as app errors.\n\nSee [`references\u002Ffabric-embed.md`](references\u002Ffabric-embed.md) for the full frame walker, `classifyConsoleMessages` helper, and troubleshooting matrix.\n\n## Spec Files\n\nAdd spec files alongside source files as needed — for components, hooks, utilities, and query factory functions. Co-locate each spec file with the file it tests.\n\n**When to add spec files:**\n- **Always** for pure utility functions in `src\u002Flib\u002F` — these are easiest to unit-test and most likely to have edge cases.\n- **Always** for query factory functions in `src\u002Fqueries\u002F` — verify that parameter combinations produce the correct query string, column metadata, and spec modifications.\n- **As needed** — for hooks, test state transitions, returned values, and side effects using a React hooks testing library.\n- **As needed** — for components, add spec files when the component contains non-trivial logic (e.g., conditional rendering, derived state, error states). Simple presentational components with no logic do not need a spec file.\n\n**Key rules:**\n- Never create a spec file just to satisfy coverage targets. Write tests only when they document expected behavior or guard against regressions.\n- Tests must not use mock or hardcoded data to stand in for real query results — use representative fixture data that matches the real column shape.\n- Keep each spec focused on one unit; do not write integration tests that span multiple layers.\n","# App Validation\n\nUse this skill **together with** the [playwright-cli](..\u002Fplaywright-cli\u002FSKILL.md) skill when validating the running app in a browser. The playwright-cli skill is upstream-managed and only covers the tool itself; this skill captures everything specific to this template. This app can **only** be tested and validated with the Fabric portal embed flow. See [Testing inside the Fabric portal embed](#testing-inside-the-fabric-portal-embed).\n**NEVER** test directly against `localhost` - the app will not work correctly.\n\n## Performance Rules\n\n### Use minimal initial_wait\n\n**Always use `initial_wait: 1`** for all playwright-cli tool calls to avoid unnecessary delays. Do not increase it unless explicitly required.\n\n> **Carve-out:** the **first** `open` against the Fabric portal embed (`*.fabric.microsoft.com\u002F...?devUri=...`) takes 20–40s to render the appbackend chrome. Use `initial_wait: 30` once for that call, then `1` afterward. See [Testing inside the Fabric portal embed](#testing-inside-the-fabric-portal-embed).\n\n### Skip auth — always\n\n**NEVER interact with or validate the token\u002Fauth prompt page.** Inside your `run-code` call, inject the auth token via `sessionStorage.setItem` (or `localStorage.setItem`) and mock API responses with `page.route()` **before** calling `page.reload()`. The app must skip the auth prompt and render actual content immediately.\n\n> **Carve-out:** this rule applies to apps that gate themselves behind a token check the agent controls. For real AAD redirects (e.g. the Fabric portal sign-in flow at `login.microsoftonline.com`), do **not** click sign-in buttons or fill credentials, and do **not** mock `sessionStorage` — use a `--persistent` profile instead so the user signs in once and cookies replay on subsequent runs. See [Testing inside the Fabric portal embed](#testing-inside-the-fabric-portal-embed).\n\n### Skip screenshots unless asked\n\nOnly take a screenshot if the user explicitly requests one. Use `snapshot` (YAML accessibility tree) for validation.\n\n## Required Checks\n\n- UI elements render correctly and are visible.\n- Text meets accessibility standards.\n- No console errors from the app. Ignore Fabric portal noise - see [console-error-filter](#console-error-filter).\n\n## Visual Consistency Checks\n\n- Verify key layout containers have non-zero computed padding and gap values. Zero spacing usually indicates an invalid token class mapping.\n- Verify chart background matches parent card background color.\n- Verify bar and arc stroke colors match card background (not primary text color).\n- Verify axis label and data-label colors are consistent across charts using shared foreground-secondary semantics.\n- Verify grouped\u002Fmulti-series bar charts do not show auto-injected data labels unless explicitly requested by design.\n- Verify chart render height is healthy for each chart canvas\u002FSVG. Treat charts rendering below ~100px as suspicious and below ~50px as likely squished.\n- Verify standalone (non-grid) chart sections use definite `height` instead of only `minHeight` when chart wrappers use `h-full`.\n- Compare computed `fontSize`, `fontFamily`, and `color` across related `input`, `select`, and `button` controls in the same toolbar\u002Ffilter row.\n- Include a `page.evaluate` style check in validation runs that reports spacing\u002Ftoken and form typography mismatches as structured failures.\n- Include a `page.evaluate` chart-height check that inspects chart canvas\u002FSVG client heights and reports squished-chart mismatches.\n\n## Testing inside the Fabric portal embed\n\nThe URL under test should be `*.fabric.microsoft.com` and contain `devUri=`, so the app is being rendered **inside the Fabric portal as a deeply-nested iframe** (`portal → *pbiabd.powerbi.com\u002Fappbackend → http:\u002F\u002Flocalhost:5173`). Use the template's wired-up flow instead of the generic `open` recipe.\n\n### One-liner\n\n```bash\nnpm run test:fabric\n```\n\nThis runs `scripts\u002Fopen-fabric-portal.mjs` which composes the embed URL from the `VITE_FABRIC_*` env vars (written into `.env.local` \u002F `.env.fabric` by `npx rayfin up`) and launches a named persistent session with the right Chromium flags:\n\n```bash\nplaywright-cli -s=fabric open --persistent --config=.playwright-config.json \"\u003Cembed-url>\"\n```\n\n### Why three pieces are required\n\n| Piece | Reason |\n| --- | --- |\n| `--persistent` profile | Real AAD sign-in cannot be mocked. The user signs in once; cookies persist for subsequent `playwright-cli -s=fabric open` calls. |\n| `.playwright-config.json` Chromium flag | Disables `BlockInsecurePrivateNetworkRequests` \u002F `LocalNetworkAccessChecks` so the HTTPS Fabric portal can iframe `http:\u002F\u002Flocalhost:5173`. Header-based opt-in does **not** work for top-level iframe navigations. |\n| Vite `localNetworkAccessPlugin` | Sends `Access-Control-Allow-Private-Network: true` and answers LNA preflights, so fetch\u002FXHR subresources from the embedded app pass. Belt-and-suspenders with the browser flag. |\n\n### Frame discovery snippet\n\nThe app loads three frames deep. Use this single `run-code` to locate it:\n\n```js\nasync page => {\n  await page.waitForFunction(\n    () => Array.from(document.querySelectorAll('iframe')).some(i => i.src.includes('localhost:5173')),\n    { timeout: 30000 }\n  );\n  await page.waitForTimeout(3000);\n  const f = page.frames().find(x => x.url().startsWith('http:\u002F\u002Flocalhost:5173'));\n  const errFrame = page.frames().find(x => x.url().startsWith('chrome-error'));\n  return {\n    loaded: !!f,\n    blockedByLNA: !!errFrame,\n    title: f ? await f.title() : null,\n  };\n}\n```\n\nIf `blockedByLNA: true`, the Chromium flag isn't taking effect — confirm `--config=.playwright-config.json` was passed.\n\n### Console error filter\n\nThe Fabric portal emits its own errors that are **not app bugs**. Treat as portal noise (ignore) - only errors where the source URL starts with `http:\u002F\u002Flocalhost:5173` count as app errors.\n\nSee [`references\u002Ffabric-embed.md`](references\u002Ffabric-embed.md) for the full frame walker, `classifyConsoleMessages` helper, and troubleshooting matrix.\n\n## Spec Files\n\nAdd spec files alongside source files as needed — for components, hooks, utilities, and query factory functions. Co-locate each spec file with the file it tests.\n\n**When to add spec files:**\n- **Always** for pure utility functions in `src\u002Flib\u002F` — these are easiest to unit-test and most likely to have edge cases.\n- **Always** for query factory functions in `src\u002Fqueries\u002F` — verify that parameter combinations produce the correct query string, column metadata, and spec modifications.\n- **As needed** — for hooks, test state transitions, returned values, and side effects using a React hooks testing library.\n- **As needed** — for components, add spec files when the component contains non-trivial logic (e.g., conditional rendering, derived state, error states). Simple presentational components with no logic do not need a spec file.\n\n**Key rules:**\n- Never create a spec file just to satisfy coverage targets. Write tests only when they document expected behavior or guard against regressions.\n- Tests must not use mock or hardcoded data to stand in for real query results — use representative fixture data that matches the real column shape.\n- Keep each spec focused on one unit; do not write integration tests that span multiple layers.\n",{"name":5,"description":7},"main","0979439a7a0806abd0ee48c2619b37f297ae1324","samples\u002Fdata-app\u002F.agents\u002Fskills\u002Fapp-validation",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":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add microsoft\u002Frayfin --skill app-validation",{"tool":50,"command":51},"bunx","bunx skills add microsoft\u002Frayfin --skill app-validation",{"tool":53,"command":54},"pnpm","pnpm dlx skills add microsoft\u002Frayfin --skill app-validation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin\u002Fblob\u002Fmain\u002Fsamples\u002Fdata-app\u002F.agents\u002Fskills\u002Fapp-validation\u002FSKILL.md",true,[58],{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Ffabric-embed.md","REFERENCE","参考文档",5056,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin\u002Fblob\u002Fmain\u002Fsamples\u002Fdata-app\u002F.agents\u002Fskills\u002Fapp-validation\u002Freferences\u002Ffabric-embed.md",[65,77,95,104,123,131],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":30},"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",[],[72,73,74,75,9,76,25],"rayfin getting started","rayfin","scaffold","init","docs",{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":91,"publishedAt":30},"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",[83,86],{"categoryNo":84,"categoryName":85,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":87,"categoryName":88,"taxonomyType":89,"taxonomyTypeDesc":90},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[79,92,93,94],"components","dashboard","visualize",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":30},"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",[],[102,103],"schema discovery","dax",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":119,"publishedAt":30},"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",[110,113,116],{"categoryNo":111,"categoryName":112,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":114,"categoryName":115,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":117,"categoryName":118,"taxonomyType":89,"taxonomyTypeDesc":90},"01JBSEEDCAT000000000000032","设计师",[120,121,103,122],"query design","design","typescript",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":30},"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",[],[130],"functions capability",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":30},"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",[],[138,139,103,140,73,141],"sdk","fabric sdk","rayfin connectors","connectors"]