[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699VNPWPQX69RW937TN5WJ3":3,"skill-same:01M699VNPWPQX69RW937TN5WJ3":51},{"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":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M699VNPWPQX69RW937TN5WJ3","hotfix-release",null,"Create a hotfix release branch, cherry-pick commits, bump the version, and open a draft PR. Use when: hotfix, patch release, cherry-pick to release, hotfix nuget, hotfix npm, release branch fix, backport fix.","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\u002F.github\u002Fskills\u002Fhotfix-release\u002FSKILL.md",[],[19],"hotfix release","2026-11-10 10:12:30",false,"---\nname: hotfix-release\ndescription: >-\n  Create a hotfix release branch, cherry-pick commits, bump the version, and\n  open a draft PR. Use when: hotfix, patch release, cherry-pick to release,\n  hotfix nuget, hotfix npm, release branch fix, backport fix.\nlicense: MIT\nmetadata:\n  author: rayfin\n  version: \"1.0\"\n---\n\nCreate a hotfix release for a previously published NuGet or npm package.\n\n**Input**: The user provides:\n\n- **Package type**: `nuget` or `npm`\n- **Version to patch**: The published version to hotfix (e.g., `0.0.45` for NuGet, `1.31.0` for npm)\n- **Commits to cherry-pick**: One or more commit SHAs, PR numbers, or branch names containing the fix\n\nIf any input is missing, use the **AskUserQuestion tool** to collect it:\n\n- If package type is unclear, ask: `nuget` or `npm`?\n- If version is missing, list recent tags with `git tag -l \"nuget\u002Fv*\" --sort=-version:refname | head -10` (or `npm\u002Fv*`) and let the user pick\n- If commits are missing, ask for the commit SHAs or PR numbers to cherry-pick\n\n## Steps\n\n### 1. Validate the tag exists\n\n```bash\ngit fetch origin --tags\ngit rev-parse \"{{type}}\u002Fv{{version}}\" >\u002Fdev\u002Fnull 2>&1\n```\n\nIf the tag doesn't exist, stop and tell the user. List available tags for that package type to help them.\n\n### 2. Determine the hotfix version\n\n**NuGet**: Use 4-part versioning. Check for existing hotfix tags:\n\n```bash\ngit tag -l \"nuget\u002Fv{{version}}.*\" --sort=-version:refname\n```\n\n- If no prior hotfix: new version is `{{version}}.1`\n- If `{{version}}.N` exists: new version is `{{version}}.N+1`\n\n**npm**: Use semver patch bump. Parse the version parts and increment patch:\n\n- `1.31.0` → `1.31.1`\n- If `npm\u002Fv1.31.1` exists, use `1.31.2`, etc.\n\nAnnounce the computed hotfix version to the user before proceeding.\n\n### 3. Create the release branch\n\n```bash\ngit checkout -b release\u002F{{type}}-v{{version}} {{type}}\u002Fv{{version}}\ngit push origin release\u002F{{type}}-v{{version}}\n```\n\n### 4. Create the fix branch and cherry-pick\n\n```bash\ngit checkout -b fix\u002Fhotfix-{{type}}-v{{hotfix_version}} release\u002F{{type}}-v{{version}}\n```\n\nCherry-pick each provided commit:\n\n```bash\ngit cherry-pick {{commit_sha}}\n```\n\nIf a cherry-pick conflicts:\n\n1. Show the conflicting files to the user\n2. Ask them to resolve\n3. After resolution, run `git cherry-pick --continue`\n\n### 5. Bump the version\n\n**NuGet**: Edit `packages\u002Fhost\u002FVersion.props` — set `\u003CVersionPrefix>` to the hotfix version:\n\n```xml\n\u003CVersionPrefix>{{hotfix_version}}\u003C\u002FVersionPrefix>\n```\n\n**npm**: Edit `packages\u002Ftypescript-sdk\u002Fcore\u002Fpackage.json` and any other affected packages — set `\"version\"` to the hotfix version. Rush version policies apply to all packages in the `typescript-sdk` policy, so update each affected package.\n\n### 6. Commit the version bump\n\n```bash\ngit add -A\ngit commit -m \"chore(host): bump {{type}} version to {{hotfix_version}} for hotfix\" --no-verify\n```\n\n### 7. Push and create a draft PR\n\n```bash\ngit push origin fix\u002Fhotfix-{{type}}-v{{hotfix_version}}\n```\n\nCreate a **draft PR** targeting `release\u002F{{type}}-v{{version}}` (not `main`):\n\n- **Title**: `fix({{type}}): hotfix v{{hotfix_version}}`\n- **Body**: List the cherry-picked commits and the version bump\n- **Draft**: true\n\n### 8. Summary\n\nAfter creating the PR, print a summary:\n\n```\n✅ Hotfix prepared\n\n  Package type:    {{type}}\n  Base version:    {{version}}\n  Hotfix version:  {{hotfix_version}}\n  Release branch:  release\u002F{{type}}-v{{version}}\n  Fix branch:      fix\u002Fhotfix-{{type}}-v{{hotfix_version}}\n  PR:              {{pr_url}}\n\nNext steps:\n  1. Review and merge the PR\n  2. Queue the rayfin.official pipeline on release\u002F{{type}}-v{{version}}\n     - Set Publish{{Type}}: true\n  3. Pipeline will publish and tag {{type}}\u002Fv{{hotfix_version}}\n```\n\n## Error Handling\n\n- **Tag not found**: List available tags and ask the user to pick the correct version\n- **Cherry-pick conflict**: Show conflicting files, let the user resolve, then continue\n- **Branch already exists**: Ask the user if they want to use the existing branch or create a new one\n- **Version already tagged**: Increment to the next available revision and confirm with the user\n","Create a hotfix release for a previously published NuGet or npm package.\n\n**Input**: The user provides:\n\n- **Package type**: `nuget` or `npm`\n- **Version to patch**: The published version to hotfix (e.g., `0.0.45` for NuGet, `1.31.0` for npm)\n- **Commits to cherry-pick**: One or more commit SHAs, PR numbers, or branch names containing the fix\n\nIf any input is missing, use the **AskUserQuestion tool** to collect it:\n\n- If package type is unclear, ask: `nuget` or `npm`?\n- If version is missing, list recent tags with `git tag -l \"nuget\u002Fv*\" --sort=-version:refname | head -10` (or `npm\u002Fv*`) and let the user pick\n- If commits are missing, ask for the commit SHAs or PR numbers to cherry-pick\n\n## Steps\n\n### 1. Validate the tag exists\n\n```bash\ngit fetch origin --tags\ngit rev-parse \"{{type}}\u002Fv{{version}}\" >\u002Fdev\u002Fnull 2>&1\n```\n\nIf the tag doesn't exist, stop and tell the user. List available tags for that package type to help them.\n\n### 2. Determine the hotfix version\n\n**NuGet**: Use 4-part versioning. Check for existing hotfix tags:\n\n```bash\ngit tag -l \"nuget\u002Fv{{version}}.*\" --sort=-version:refname\n```\n\n- If no prior hotfix: new version is `{{version}}.1`\n- If `{{version}}.N` exists: new version is `{{version}}.N+1`\n\n**npm**: Use semver patch bump. Parse the version parts and increment patch:\n\n- `1.31.0` → `1.31.1`\n- If `npm\u002Fv1.31.1` exists, use `1.31.2`, etc.\n\nAnnounce the computed hotfix version to the user before proceeding.\n\n### 3. Create the release branch\n\n```bash\ngit checkout -b release\u002F{{type}}-v{{version}} {{type}}\u002Fv{{version}}\ngit push origin release\u002F{{type}}-v{{version}}\n```\n\n### 4. Create the fix branch and cherry-pick\n\n```bash\ngit checkout -b fix\u002Fhotfix-{{type}}-v{{hotfix_version}} release\u002F{{type}}-v{{version}}\n```\n\nCherry-pick each provided commit:\n\n```bash\ngit cherry-pick {{commit_sha}}\n```\n\nIf a cherry-pick conflicts:\n\n1. Show the conflicting files to the user\n2. Ask them to resolve\n3. After resolution, run `git cherry-pick --continue`\n\n### 5. Bump the version\n\n**NuGet**: Edit `packages\u002Fhost\u002FVersion.props` — set `\u003CVersionPrefix>` to the hotfix version:\n\n```xml\n\u003CVersionPrefix>{{hotfix_version}}\u003C\u002FVersionPrefix>\n```\n\n**npm**: Edit `packages\u002Ftypescript-sdk\u002Fcore\u002Fpackage.json` and any other affected packages — set `\"version\"` to the hotfix version. Rush version policies apply to all packages in the `typescript-sdk` policy, so update each affected package.\n\n### 6. Commit the version bump\n\n```bash\ngit add -A\ngit commit -m \"chore(host): bump {{type}} version to {{hotfix_version}} for hotfix\" --no-verify\n```\n\n### 7. Push and create a draft PR\n\n```bash\ngit push origin fix\u002Fhotfix-{{type}}-v{{hotfix_version}}\n```\n\nCreate a **draft PR** targeting `release\u002F{{type}}-v{{version}}` (not `main`):\n\n- **Title**: `fix({{type}}): hotfix v{{hotfix_version}}`\n- **Body**: List the cherry-picked commits and the version bump\n- **Draft**: true\n\n### 8. Summary\n\nAfter creating the PR, print a summary:\n\n```\n✅ Hotfix prepared\n\n  Package type:    {{type}}\n  Base version:    {{version}}\n  Hotfix version:  {{hotfix_version}}\n  Release branch:  release\u002F{{type}}-v{{version}}\n  Fix branch:      fix\u002Fhotfix-{{type}}-v{{hotfix_version}}\n  PR:              {{pr_url}}\n\nNext steps:\n  1. Review and merge the PR\n  2. Queue the rayfin.official pipeline on release\u002F{{type}}-v{{version}}\n     - Set Publish{{Type}}: true\n  3. Pipeline will publish and tag {{type}}\u002Fv{{hotfix_version}}\n```\n\n## Error Handling\n\n- **Tag not found**: List available tags and ask the user to pick the correct version\n- **Cherry-pick conflict**: Show conflicting files, let the user resolve, then continue\n- **Branch already exists**: Ask the user if they want to use the existing branch or create a new one\n- **Version already tagged**: Increment to the next available revision and confirm with the user\n",{"name":5,"license":15,"metadata":25,"description":7},{"author":26,"version":27},"rayfin","1.0","main","0979439a7a0806abd0ee48c2619b37f297ae1324",".github\u002Fskills\u002Fhotfix-release",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":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add microsoft\u002Frayfin --skill hotfix-release",{"tool":43,"command":44},"bunx","bunx skills add microsoft\u002Frayfin --skill hotfix-release",{"tool":46,"command":47},"pnpm","pnpm dlx skills add microsoft\u002Frayfin --skill hotfix-release","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fhotfix-release\u002FSKILL.md",true,[],[52,64,84,93,112,120],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":20},"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",[],[59,26,60,61,9,62,63],"rayfin getting started","scaffold","init","docs","cli",{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":80,"publishedAt":20},"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",[70,75],{"categoryNo":71,"categoryName":72,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000013","分析与可视化","SCENARIO","使用场景",{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[66,81,82,83],"components","dashboard","visualize",{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":20},"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",[],[91,92],"schema discovery","dax",{"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":108,"publishedAt":20},"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",[99,102,105],{"categoryNo":100,"categoryName":101,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":103,"categoryName":104,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":106,"categoryName":107,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000032","设计师",[109,110,92,111],"query design","design","typescript",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":20},"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",[],[119],"functions capability",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":20},"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",[],[127,128,92,129,26,130],"sdk","fabric sdk","rayfin connectors","connectors"]