[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699XNA7XWQJCF240QDV9S14":3,"skill-same:01M699XNA7XWQJCF240QDV9S14":53},{"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},"01M699XNA7XWQJCF240QDV9S14","app-deployment",null,"Validate and remotely deploy a Universal App through the installed, version-matched Rayfin CLI. Use before deploying to run local checks, confirm the target workspace, preview the operation, deploy, and validate the live app. This skill orchestrates existing executables; it does not implement deployment.","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\u002Fapp-deployment\u002FSKILL.md",[],[19,20,21,22,23,24],"app deployment","cli","implement","validate","deploy","rayfin","2026-11-10 10:12:30",false,"---\nname: app-deployment\ndescription: >\n  Validate and remotely deploy a Universal App through the installed,\n  version-matched Rayfin CLI. Use before deploying to run local checks, confirm\n  the target workspace, preview the operation, deploy, and validate the live\n  app. This skill orchestrates existing executables; it does not implement\n  deployment.\n---\n\n# App Deployment\n\nThis skill orchestrates the installed Rayfin CLI lifecycle. It does not\nrecreate the validation or deployment implementation.\n\n## Before a remote write\n\n1. Apply every capability pack the app needs.\n2. Read `app-validation` and complete its static gates: typecheck, build, lint,\n   tests, and pack-provided validators.\n   Run pre-deploy browser or persistence checks only when the installed guide\n   and current environment already support a local or deployed runtime.\n3. Obtain the user's confirmation for the target Fabric workspace and remote\n   deployment. Do not select or create a workspace the user did not approve.\n\n## Rayfin CLI deployment\n\n1. Read the installed package metadata for `@microsoft\u002Frayfin-guide`, then read\n   its version-matched deployment guide. The current guide location is\n   `node_modules\u002F@microsoft\u002Frayfin-guide\u002Fassets\u002Fdocs\u002Fapp-backend\u002Fdeploy.md`; if\n   package metadata points elsewhere, follow that installed location.\n2. Follow that guide's authentication and deployment workflow. For the current\n   version, preview the remote operation with `npx rayfin up -n`, verify the\n   confirmed target, and then run `npx rayfin up --json`.\n   JSON mode is non-interactive.\n   On a first deployment with no recorded target, pass the confirmed target\n   explicitly with `--workspace-id \u003Cid>`, `--workspace \u003Cname>`, or\n   `--workspace-uri \u003Curi>`.\n3. Read the machine-readable deployment result before continuing.\n   Overall `status: \"success\"` is not enough for a source-backed request.\n   Inspect `generate` status first.\n   For every connector declared in `rayfin.yml`, require one matching\n   `generate[]` result.\n   A missing result or a result with `status: \"error\"` is blocking.\n   Only when a result has `status: \"skipped\"` should you inspect its\n   `skipReason`.\n   Every connector required by the requested deployed experience must complete\n   the generation\u002Fapply path its installed type contract requires.\n   A Category B `non-graphql-connector` skip is acceptable only when the\n   installed type contract documents that path and the connector's deployed\n   behavior was validated separately.\n   Any other skip for a required connector is blocking.\n   `skippedConnectors` summarizes skipped results only; it excludes errors and\n   cannot reveal a missing `generate[]` result.\n   Do not use `skippedConnectors` or warning wording to decide whether a\n   connector succeeded.\n   If a required connector is missing, errors, or has a blocking skip, report\n   the blocker and stop.\n   Do not continue to browser validation or claim the source-backed request\n   succeeded.\n4. Do not claim the CLI has validation guarantees that its installed guide does\n   not document.\n5. Use the direct static-hosting link emitted by the CLI for standalone browser validation.\n   Use the actual Fabric or external host when validating embedded capabilities.\n6. Determine `services.staticHosting.assetAccess` before choosing the browser\n   checks. Local `autoLogin` does not prove the deployed public signed-out\n   experience.\n\nDo not publish automatically.\nDo not add `--force` unless the user explicitly requests it and the installed\nguide documents the consequence for the exact operation.\n\nNever put access tokens, credentials, or secret values in command arguments,\nchat, source, or logs. Use interactive authentication and masked secret prompts\nwhen the installed guide requires them.\n\n## Prove the deployed result\n\nAfter deployment succeeds, read `app-validation` and validate the deployed app\nat its direct hosting URL, confirming that signed-out users must authenticate before app content renders.\nRun the browser checks and, for app-owned records, the persistence create,\nreload, update, and delete checks against the deployed result.\nFor public hosting, also open the standalone hosting URL in a clean browser\nsession and verify signed-out then signed-in behavior. For protected hosting,\nverify session restoration and stale-session replacement. For embedded apps,\nvalidate through the actual Fabric or external host.\nDo not report deployment complete from a build, dry run, hosting URL, or CLI\nsuccess alone.\nReport the Fabric app link only after the deployed runtime checks pass, unless\nthe user explicitly defers runtime validation.\n","# App Deployment\n\nThis skill orchestrates the installed Rayfin CLI lifecycle. It does not\nrecreate the validation or deployment implementation.\n\n## Before a remote write\n\n1. Apply every capability pack the app needs.\n2. Read `app-validation` and complete its static gates: typecheck, build, lint,\n   tests, and pack-provided validators.\n   Run pre-deploy browser or persistence checks only when the installed guide\n   and current environment already support a local or deployed runtime.\n3. Obtain the user's confirmation for the target Fabric workspace and remote\n   deployment. Do not select or create a workspace the user did not approve.\n\n## Rayfin CLI deployment\n\n1. Read the installed package metadata for `@microsoft\u002Frayfin-guide`, then read\n   its version-matched deployment guide. The current guide location is\n   `node_modules\u002F@microsoft\u002Frayfin-guide\u002Fassets\u002Fdocs\u002Fapp-backend\u002Fdeploy.md`; if\n   package metadata points elsewhere, follow that installed location.\n2. Follow that guide's authentication and deployment workflow. For the current\n   version, preview the remote operation with `npx rayfin up -n`, verify the\n   confirmed target, and then run `npx rayfin up --json`.\n   JSON mode is non-interactive.\n   On a first deployment with no recorded target, pass the confirmed target\n   explicitly with `--workspace-id \u003Cid>`, `--workspace \u003Cname>`, or\n   `--workspace-uri \u003Curi>`.\n3. Read the machine-readable deployment result before continuing.\n   Overall `status: \"success\"` is not enough for a source-backed request.\n   Inspect `generate` status first.\n   For every connector declared in `rayfin.yml`, require one matching\n   `generate[]` result.\n   A missing result or a result with `status: \"error\"` is blocking.\n   Only when a result has `status: \"skipped\"` should you inspect its\n   `skipReason`.\n   Every connector required by the requested deployed experience must complete\n   the generation\u002Fapply path its installed type contract requires.\n   A Category B `non-graphql-connector` skip is acceptable only when the\n   installed type contract documents that path and the connector's deployed\n   behavior was validated separately.\n   Any other skip for a required connector is blocking.\n   `skippedConnectors` summarizes skipped results only; it excludes errors and\n   cannot reveal a missing `generate[]` result.\n   Do not use `skippedConnectors` or warning wording to decide whether a\n   connector succeeded.\n   If a required connector is missing, errors, or has a blocking skip, report\n   the blocker and stop.\n   Do not continue to browser validation or claim the source-backed request\n   succeeded.\n4. Do not claim the CLI has validation guarantees that its installed guide does\n   not document.\n5. Use the direct static-hosting link emitted by the CLI for standalone browser validation.\n   Use the actual Fabric or external host when validating embedded capabilities.\n6. Determine `services.staticHosting.assetAccess` before choosing the browser\n   checks. Local `autoLogin` does not prove the deployed public signed-out\n   experience.\n\nDo not publish automatically.\nDo not add `--force` unless the user explicitly requests it and the installed\nguide documents the consequence for the exact operation.\n\nNever put access tokens, credentials, or secret values in command arguments,\nchat, source, or logs. Use interactive authentication and masked secret prompts\nwhen the installed guide requires them.\n\n## Prove the deployed result\n\nAfter deployment succeeds, read `app-validation` and validate the deployed app\nat its direct hosting URL, confirming that signed-out users must authenticate before app content renders.\nRun the browser checks and, for app-owned records, the persistence create,\nreload, update, and delete checks against the deployed result.\nFor public hosting, also open the standalone hosting URL in a clean browser\nsession and verify signed-out then signed-in behavior. For protected hosting,\nverify session restoration and stale-session replacement. For embedded apps,\nvalidate through the actual Fabric or external host.\nDo not report deployment complete from a build, dry run, hosting URL, or CLI\nsuccess alone.\nReport the Fabric app link only after the deployed runtime checks pass, unless\nthe user explicitly defers runtime validation.\n",{"name":5,"description":7},"main","0979439a7a0806abd0ee48c2619b37f297ae1324","samples\u002Funiversal-app\u002Ftemplate\u002F.agents\u002Fskills\u002Fapp-deployment",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 app-deployment",{"tool":45,"command":46},"bunx","bunx skills add microsoft\u002Frayfin --skill app-deployment",{"tool":48,"command":49},"pnpm","pnpm dlx skills add microsoft\u002Frayfin --skill app-deployment","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin\u002Fblob\u002Fmain\u002Fsamples\u002Funiversal-app\u002Ftemplate\u002F.agents\u002Fskills\u002Fapp-deployment\u002FSKILL.md",true,[],[54,65,85,94,113,121],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"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",[],[61,24,62,63,9,64,20],"rayfin getting started","scaffold","init","docs",{"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":81,"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",[71,76],{"categoryNo":72,"categoryName":73,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000013","分析与可视化","SCENARIO","使用场景",{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[67,82,83,84],"components","dashboard","visualize",{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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",[],[92,93],"schema discovery","dax",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":109,"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",[100,103,106],{"categoryNo":101,"categoryName":102,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":104,"categoryName":105,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":107,"categoryName":108,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000032","设计师",[110,111,93,112],"query design","design","typescript",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"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",[],[120],"functions capability",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":25},"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",[],[128,129,93,130,24,131],"sdk","fabric sdk","rayfin connectors","connectors"]