[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699X10T2D1S4BZYNF1SRPYC":3,"skill-same:01M699X10T2D1S4BZYNF1SRPYC":54},{"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":24,"linkOnly":25,"markdownContent":26,"markdownBody":27,"frontMatter":28,"refName":31,"commitSha":32,"skillDirectory":33,"forksCount":34,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":37,"ownerDescription":38,"updatedAt":39,"install":40,"resources":53},"01M699X10T2D1S4BZYNF1SRPYC","rayfin-getting-started",null,"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","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\u002Fplugin\u002Fskills\u002Frayfin-getting-started\u002FSKILL.md",[],[19,20,21,9,22,23],"rayfin getting started","cli","docs","init","scaffold","2026-11-10 10:12:30",false,"---\nname: rayfin-getting-started\ndescription: \"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\"\nmetadata:\n  author: microsoft\n  version: \"0.4.0\"\n---\n\n# Rayfin (Getting Started)\n\nRayfin is a Backend-as-a-Service: define your data model with TypeScript decorators and\nRayfin provides auth, a typed data API, storage, and Fabric hosting.\n\nThis skill only handles *getting started* — getting you from zero into a working Rayfin\nproject, then handing off. The moment you're in a project, the authoritative, version-locked\nskill at `.agents\u002Fskills\u002Frayfin\u002FSKILL.md` — alongside the package docs in `node_modules` and\nthe `rayfin docs` CLI — owns everything else: schema, auth, storage, querying, deployment.\nLoad it and stop using this one.\n\n## Route, don't improvise\n\nRayfin's specifics are version-locked per project — schema\u002Fdecorator syntax, the typed data\nAPI and client queries, auth, storage, and deployment all live in the project's own skill and\n`rayfin docs`. Never answer them from memory; remembered Rayfin APIs are routinely\nwrong against the installed version. Get into a project, read `.agents\u002Fskills\u002Frayfin\u002FSKILL.md`,\nthen follow it for version-matched signatures. The in-project skill **file** and the\n`rayfin docs` CLI are available the moment a project exists — including right after you\nscaffold one, in the same session. The `rayfin` MCP server is an optional extra that most\nprojects do not install; if it happens to be available it is a convenience, never a\nprerequisite. Lean on the in-project skill file plus `rayfin docs`.\n\nBeing blocked does not unlock memory. Only treat yourself as blocked if you can reach **none**\nof the version-matched sources — you can't read `.agents\u002Fskills\u002Frayfin\u002FSKILL.md` *and* can't\nrun `rayfin docs` (e.g. tool permissions denied). The `rayfin` MCP server not being installed\nor loaded is **not** a blocker. When genuinely blocked, say you need those sources to answer\naccurately and stop there — don't offer a \"general approach\" or example code \"in the\nmeantime\"; that stopgap is exactly the fabrication this skill exists to prevent.\n\n## Already in a Rayfin project?\n\nCheck this first — before scaffolding anything, even when the user says \"build\" or \"set up a\nnew app\". A directory is a Rayfin project if it has `rayfin\u002Frayfin.yml` or a `package.json`\ndepending on `@microsoft\u002Frayfin-*`. Environment signals alone are enough: if the workspace\ncontext shows either — even when you can't open the files yet — treat it as an existing\nproject and continue in place. Never stand up a nested or sibling project.\n\n- **Already in one →** load `.agents\u002Fskills\u002Frayfin\u002FSKILL.md` and use `rayfin docs` (or the\n  `rayfin` MCP, if already installed). Stop using this skill.\n- **Existing non-Rayfin app here →** add Rayfin in place with `npx rayfin init` (don't\n  scaffold a separate project), then load the in-project skill.\n- **Empty directory →** scaffold (below), then load the in-project skill from the project root.\n\n## Scaffold a new project\n\n`npm create @microsoft\u002Frayfin@latest` is a thin wrapper around `rayfin init`. As an agent you\nrun non-interactively (stdin isn't a TTY), so use the `npx -y` form — `npm create` can\nmishandle piped stdin and strip flags, and `--project-name` is **required** non-interactively.\n\n```bash\n# Create non-interactively. --project-name is required; the template is pinned.\nnpx -y @microsoft\u002Fcreate-rayfin@latest --project-name \u003Capp-name> --template universal-app\n\n# Or add Rayfin into an existing\u002Fempty directory\nnpx rayfin init [directory]\n```\n\n**Always scaffold `universal-app`.** Don't browse the gallery and don't pick a domain-specific\ntemplate. The Universal App is a deliberately small React + Vite base with a built-in\ncapability router that pulls in the right Rayfin services, npm modules, and skills on demand,\nso the domain shape (analytics, CRUD, storage, functions) gets decided *inside* the project\nrather than at scaffold time. The project's own `.agents\u002Fskills\u002F` own that decision, and they\nare version-matched in a way a scaffold-time template choice is not.\n\nMind the project root before loading the in-project skill: `create-rayfin` creates a child\nproject directory (named from `--project-name`, slugified), so `cd` into it; an in-place\n`rayfin init` scaffolds in the current directory, so you're already there. Once at the project\nroot, load its `.agents\u002Fskills\u002Frayfin\u002FSKILL.md` and let its capability router take over.\n","# Rayfin (Getting Started)\n\nRayfin is a Backend-as-a-Service: define your data model with TypeScript decorators and\nRayfin provides auth, a typed data API, storage, and Fabric hosting.\n\nThis skill only handles *getting started* — getting you from zero into a working Rayfin\nproject, then handing off. The moment you're in a project, the authoritative, version-locked\nskill at `.agents\u002Fskills\u002Frayfin\u002FSKILL.md` — alongside the package docs in `node_modules` and\nthe `rayfin docs` CLI — owns everything else: schema, auth, storage, querying, deployment.\nLoad it and stop using this one.\n\n## Route, don't improvise\n\nRayfin's specifics are version-locked per project — schema\u002Fdecorator syntax, the typed data\nAPI and client queries, auth, storage, and deployment all live in the project's own skill and\n`rayfin docs`. Never answer them from memory; remembered Rayfin APIs are routinely\nwrong against the installed version. Get into a project, read `.agents\u002Fskills\u002Frayfin\u002FSKILL.md`,\nthen follow it for version-matched signatures. The in-project skill **file** and the\n`rayfin docs` CLI are available the moment a project exists — including right after you\nscaffold one, in the same session. The `rayfin` MCP server is an optional extra that most\nprojects do not install; if it happens to be available it is a convenience, never a\nprerequisite. Lean on the in-project skill file plus `rayfin docs`.\n\nBeing blocked does not unlock memory. Only treat yourself as blocked if you can reach **none**\nof the version-matched sources — you can't read `.agents\u002Fskills\u002Frayfin\u002FSKILL.md` *and* can't\nrun `rayfin docs` (e.g. tool permissions denied). The `rayfin` MCP server not being installed\nor loaded is **not** a blocker. When genuinely blocked, say you need those sources to answer\naccurately and stop there — don't offer a \"general approach\" or example code \"in the\nmeantime\"; that stopgap is exactly the fabrication this skill exists to prevent.\n\n## Already in a Rayfin project?\n\nCheck this first — before scaffolding anything, even when the user says \"build\" or \"set up a\nnew app\". A directory is a Rayfin project if it has `rayfin\u002Frayfin.yml` or a `package.json`\ndepending on `@microsoft\u002Frayfin-*`. Environment signals alone are enough: if the workspace\ncontext shows either — even when you can't open the files yet — treat it as an existing\nproject and continue in place. Never stand up a nested or sibling project.\n\n- **Already in one →** load `.agents\u002Fskills\u002Frayfin\u002FSKILL.md` and use `rayfin docs` (or the\n  `rayfin` MCP, if already installed). Stop using this skill.\n- **Existing non-Rayfin app here →** add Rayfin in place with `npx rayfin init` (don't\n  scaffold a separate project), then load the in-project skill.\n- **Empty directory →** scaffold (below), then load the in-project skill from the project root.\n\n## Scaffold a new project\n\n`npm create @microsoft\u002Frayfin@latest` is a thin wrapper around `rayfin init`. As an agent you\nrun non-interactively (stdin isn't a TTY), so use the `npx -y` form — `npm create` can\nmishandle piped stdin and strip flags, and `--project-name` is **required** non-interactively.\n\n```bash\n# Create non-interactively. --project-name is required; the template is pinned.\nnpx -y @microsoft\u002Fcreate-rayfin@latest --project-name \u003Capp-name> --template universal-app\n\n# Or add Rayfin into an existing\u002Fempty directory\nnpx rayfin init [directory]\n```\n\n**Always scaffold `universal-app`.** Don't browse the gallery and don't pick a domain-specific\ntemplate. The Universal App is a deliberately small React + Vite base with a built-in\ncapability router that pulls in the right Rayfin services, npm modules, and skills on demand,\nso the domain shape (analytics, CRUD, storage, functions) gets decided *inside* the project\nrather than at scaffold time. The project's own `.agents\u002Fskills\u002F` own that decision, and they\nare version-matched in a way a scaffold-time template choice is not.\n\nMind the project root before loading the in-project skill: `create-rayfin` creates a child\nproject directory (named from `--project-name`, slugified), so `cd` into it; an in-place\n`rayfin init` scaffolds in the current directory, so you're already there. Once at the project\nroot, load its `.agents\u002Fskills\u002Frayfin\u002FSKILL.md` and let its capability router take over.\n",{"name":5,"metadata":29,"description":7},{"author":9,"version":30},"0.4.0","main","0979439a7a0806abd0ee48c2619b37f297ae1324","plugin\u002Fskills\u002Frayfin-getting-started",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":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add microsoft\u002Frayfin --skill rayfin-getting-started",{"tool":46,"command":47},"bunx","bunx skills add microsoft\u002Frayfin --skill rayfin-getting-started",{"tool":49,"command":50},"pnpm","pnpm dlx skills add microsoft\u002Frayfin --skill rayfin-getting-started","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Frayfin-getting-started\u002FSKILL.md",true,[],[55,61,81,90,109,117],{"skillNo":56,"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":57,"categories":58,"keywords":59,"publishedAt":24},"01M699YEY2QDVPKTZS3HR9AX84","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin\u002Fblob\u002Fmain\u002Fskills\u002Frayfin-getting-started\u002FSKILL.md",[],[19,60,23,22,9,21,20],"rayfin",{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":77,"publishedAt":24},"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",[67,72],{"categoryNo":68,"categoryName":69,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000013","分析与可视化","SCENARIO","使用场景",{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[63,78,79,80],"components","dashboard","visualize",{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":24},"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",[],[88,89],"schema discovery","dax",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":105,"publishedAt":24},"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",[96,99,102],{"categoryNo":97,"categoryName":98,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":100,"categoryName":101,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":103,"categoryName":104,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000032","设计师",[106,107,89,108],"query design","design","typescript",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":24},"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",[],[116],"functions capability",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":24},"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",[],[124,125,89,126,60,127],"sdk","fabric sdk","rayfin connectors","connectors"]