[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CT3SYVWMWTJS0600B5APXW":3,"skill-same:01M7CT3SYVWMWTJS0600B5APXW":47},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7CT3SYVWMWTJS0600B5APXW","run-toolset-tests",null,"Run the razor-toolset-ci pipeline to validate the current branch against large third-party repositories (MudBlazor, OrchardCore, ASP.NET Core, etc.). Use when asked to run toolset tests, ecosystem tests, or third-party validation.","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Tool-开发工具链\u002FYYC3-Tool-开发工具链-dotnet\u002Frazor\u002F.github\u002Fskills\u002Frun-toolset-tests\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: run-toolset-tests\ndescription: >-\n  Run the razor-toolset-ci pipeline to validate the current branch against large\n  third-party repositories (MudBlazor, OrchardCore, ASP.NET Core, etc.).\n  Use when asked to run toolset tests, ecosystem tests, or third-party validation.\n---\n\n# Run Razor Toolset Tests\n\nPushes the current branch to `dotnet\u002Frazor` on GitHub and triggers the\n[`razor-toolset-ci`](https:\u002F\u002Fdev.azure.com\u002Fdnceng\u002Finternal\u002F_build?definitionId=1270)\nAzure DevOps pipeline (definition 1270, project `internal`) to build the Razor\ncompiler toolset and validate it against large third-party projects.\n\n## Background\n\nThe pipeline lives in the [`razor-toolset-tests`](https:\u002F\u002Fdev.azure.com\u002Fdnceng\u002Finternal\u002F_git\u002Frazor-toolset-tests)\nrepo in `dnceng\u002Finternal`. It:\n\n1. Builds `Microsoft.Net.Compilers.Razor.Toolset` from the Razor repo\n2. Injects it (plus the matching Roslyn toolset) into 11 third-party projects\n3. Builds each project to verify compatibility\n\nProjects tested: MudBlazor, Havit.Blazor, Telerik Blazor UI, OrchardCore,\nGrandNode2, Damselfly, Hawaso, dotnet-podcasts, and ASP.NET Core\n(MVC, Razor Pages, Blazor components).\n\n**Important:** When manually triggered, the pipeline checks out from the\n`RazorGitHubRepo` resource (`github.com\u002Fdotnet\u002Frazor`). The commit must be\npushed to `dotnet\u002Frazor` — commits on forks or the internal ADO mirror are\nnot accessible for manual runs.\n\n## Steps\n\n### 1. Verify prerequisites\n\n- Confirm we're in the razor repository (look for `src\u002FCompiler` or check git remotes).\n- Get the current commit SHA: `git rev-parse HEAD`\n- Get the current branch name: `git branch --show-current`\n  (if HEAD is detached, use `git rev-parse --short HEAD` as the name)\n\n### 2. Find or configure a remote for `dotnet\u002Frazor`\n\n- Run `git remote -v` and look for a remote whose URL contains `dotnet\u002Frazor`.\n- Common remote names: `upstream`, `dotnet`.\n- If no such remote exists, add one:\n  ```\n  git remote add dotnet https:\u002F\u002Fgithub.com\u002Fdotnet\u002Frazor.git\n  ```\n- Store the remote name for subsequent steps.\n\n### 3. Push to GitHub\n\nPush current HEAD to a test branch on `dotnet\u002Frazor`:\n\n```\ngit push \u003Cremote> HEAD:refs\u002Fheads\u002Ftoolset-test\u002F\u003Cbranch-name> --force\n```\n\nIf the branch name is empty (detached HEAD), use the short SHA instead.\n\nIf the push fails with a permission error, inform the user they need push access\nto `dotnet\u002Frazor`.\n\n### 4. Trigger the pipeline\n\nUse the `ado-pipelines_run_pipeline` MCP tool:\n\n- `project`: `\"internal\"`\n- `pipelineId`: `1270`\n- `resources`:\n  ```json\n  {\n    \"pipelines\": {},\n    \"repositories\": {\n      \"RazorGitHubRepo\": {\n        \"refName\": \"refs\u002Fheads\u002Ftoolset-test\u002F\u003Cbranch-name>\",\n        \"version\": \"\u003Ccommit-sha>\"\n      }\n    }\n  }\n  ```\n\nIf the MCP tool fails, fall back to the REST API via PowerShell:\n\n```powershell\n$body = @{\n    resources = @{\n        repositories = @{\n            RazorGitHubRepo = @{\n                refName = \"refs\u002Fheads\u002Ftoolset-test\u002F\u003Cbranch-name>\"\n                version = \"\u003Ccommit-sha>\"\n            }\n        }\n    }\n} | ConvertTo-Json -Depth 5\n\naz devops configure --defaults organization=https:\u002F\u002Fdev.azure.com\u002Fdnceng project=internal\n$result = az rest --method post `\n    --uri \"https:\u002F\u002Fdev.azure.com\u002Fdnceng\u002Finternal\u002F_apis\u002Fpipelines\u002F1270\u002Fruns?api-version=7.1\" `\n    --body \"$body\" `\n    --resource \"499b84ac-1321-427f-aa17-267ca6975798\" | ConvertFrom-Json\nWrite-Output \"Run URL: https:\u002F\u002Fdev.azure.com\u002Fdnceng\u002Finternal\u002F_build\u002Fresults?buildId=$($result.id)\"\n```\n\n### 5. Report results\n\nShow the user:\n- The pipeline run URL (from the response, or construct from the build ID)\n- The commit SHA and branch that was pushed\n- A reminder to clean up the remote branch when done:\n  ```\n  git push \u003Cremote> --delete toolset-test\u002F\u003Cbranch-name>\n  ```\n\n## Notes\n\n- All 11 projects run as parallel jobs — individual jobs can fail independently.\n- The pipeline uses the `windows.vs2026.amd64` agent image.\n- Pipeline definition: https:\u002F\u002Fdev.azure.com\u002Fdnceng\u002Finternal\u002F_build?definitionId=1270\n- Pipeline source repo: https:\u002F\u002Fdev.azure.com\u002Fdnceng\u002Finternal\u002F_git\u002Frazor-toolset-tests\n","# Run Razor Toolset Tests\n\nPushes the current branch to `dotnet\u002Frazor` on GitHub and triggers the\n[`razor-toolset-ci`](https:\u002F\u002Fdev.azure.com\u002Fdnceng\u002Finternal\u002F_build?definitionId=1270)\nAzure DevOps pipeline (definition 1270, project `internal`) to build the Razor\ncompiler toolset and validate it against large third-party projects.\n\n## Background\n\nThe pipeline lives in the [`razor-toolset-tests`](https:\u002F\u002Fdev.azure.com\u002Fdnceng\u002Finternal\u002F_git\u002Frazor-toolset-tests)\nrepo in `dnceng\u002Finternal`. It:\n\n1. Builds `Microsoft.Net.Compilers.Razor.Toolset` from the Razor repo\n2. Injects it (plus the matching Roslyn toolset) into 11 third-party projects\n3. Builds each project to verify compatibility\n\nProjects tested: MudBlazor, Havit.Blazor, Telerik Blazor UI, OrchardCore,\nGrandNode2, Damselfly, Hawaso, dotnet-podcasts, and ASP.NET Core\n(MVC, Razor Pages, Blazor components).\n\n**Important:** When manually triggered, the pipeline checks out from the\n`RazorGitHubRepo` resource (`github.com\u002Fdotnet\u002Frazor`). The commit must be\npushed to `dotnet\u002Frazor` — commits on forks or the internal ADO mirror are\nnot accessible for manual runs.\n\n## Steps\n\n### 1. Verify prerequisites\n\n- Confirm we're in the razor repository (look for `src\u002FCompiler` or check git remotes).\n- Get the current commit SHA: `git rev-parse HEAD`\n- Get the current branch name: `git branch --show-current`\n  (if HEAD is detached, use `git rev-parse --short HEAD` as the name)\n\n### 2. Find or configure a remote for `dotnet\u002Frazor`\n\n- Run `git remote -v` and look for a remote whose URL contains `dotnet\u002Frazor`.\n- Common remote names: `upstream`, `dotnet`.\n- If no such remote exists, add one:\n  ```\n  git remote add dotnet https:\u002F\u002Fgithub.com\u002Fdotnet\u002Frazor.git\n  ```\n- Store the remote name for subsequent steps.\n\n### 3. Push to GitHub\n\nPush current HEAD to a test branch on `dotnet\u002Frazor`:\n\n```\ngit push \u003Cremote> HEAD:refs\u002Fheads\u002Ftoolset-test\u002F\u003Cbranch-name> --force\n```\n\nIf the branch name is empty (detached HEAD), use the short SHA instead.\n\nIf the push fails with a permission error, inform the user they need push access\nto `dotnet\u002Frazor`.\n\n### 4. Trigger the pipeline\n\nUse the `ado-pipelines_run_pipeline` MCP tool:\n\n- `project`: `\"internal\"`\n- `pipelineId`: `1270`\n- `resources`:\n  ```json\n  {\n    \"pipelines\": {},\n    \"repositories\": {\n      \"RazorGitHubRepo\": {\n        \"refName\": \"refs\u002Fheads\u002Ftoolset-test\u002F\u003Cbranch-name>\",\n        \"version\": \"\u003Ccommit-sha>\"\n      }\n    }\n  }\n  ```\n\nIf the MCP tool fails, fall back to the REST API via PowerShell:\n\n```powershell\n$body = @{\n    resources = @{\n        repositories = @{\n            RazorGitHubRepo = @{\n                refName = \"refs\u002Fheads\u002Ftoolset-test\u002F\u003Cbranch-name>\"\n                version = \"\u003Ccommit-sha>\"\n            }\n        }\n    }\n} | ConvertTo-Json -Depth 5\n\naz devops configure --defaults organization=https:\u002F\u002Fdev.azure.com\u002Fdnceng project=internal\n$result = az rest --method post `\n    --uri \"https:\u002F\u002Fdev.azure.com\u002Fdnceng\u002Finternal\u002F_apis\u002Fpipelines\u002F1270\u002Fruns?api-version=7.1\" `\n    --body \"$body\" `\n    --resource \"499b84ac-1321-427f-aa17-267ca6975798\" | ConvertFrom-Json\nWrite-Output \"Run URL: https:\u002F\u002Fdev.azure.com\u002Fdnceng\u002Finternal\u002F_build\u002Fresults?buildId=$($result.id)\"\n```\n\n### 5. Report results\n\nShow the user:\n- The pipeline run URL (from the response, or construct from the build ID)\n- The commit SHA and branch that was pushed\n- A reminder to clean up the remote branch when done:\n  ```\n  git push \u003Cremote> --delete toolset-test\u002F\u003Cbranch-name>\n  ```\n\n## Notes\n\n- All 11 projects run as parallel jobs — individual jobs can fail independently.\n- The pipeline uses the `windows.vs2026.amd64` agent image.\n- Pipeline definition: https:\u002F\u002Fdev.azure.com\u002Fdnceng\u002Finternal\u002F_build?definitionId=1270\n- Pipeline source repo: https:\u002F\u002Fdev.azure.com\u002Fdnceng\u002Finternal\u002F_git\u002Frazor-toolset-tests\n",{"name":5,"description":7},"main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Tool-开发工具链\u002FYYC3-Tool-开发工具链-dotnet\u002Frazor\u002F.github\u002Fskills\u002Frun-toolset-tests",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill run-toolset-tests",{"tool":39,"command":40},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill run-toolset-tests",{"tool":42,"command":43},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill run-toolset-tests","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Tool-开发工具链\u002FYYC3-Tool-开发工具链-dotnet\u002Frazor\u002F.github\u002Fskills\u002Frun-toolset-tests\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]