[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69AHGQY92XY4NDY7CG4N2AC":3,"skill-same:01M69AHGQY92XY4NDY7CG4N2AC":70},{"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":26,"publishedAt":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":45,"ownerHtmlUrl":46,"ownerBlogUrl":47,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M69AHGQY92XY4NDY7CG4N2AC","webapp-testing",null,"Use this skill to build features or debug anything that uses a webapp frontend.","microsoft\u002FFluidFramework","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69AG0BQKNGBJQ5YNG09HXXW",4949,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.agency\u002Fplugins\u002Fnori\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[27,28,29,30,31,32,33,34],"testing","webapp testing","webapp","frontend","debug","use","build","features","2026-11-10 10:12:30",false,"---\nname: webapp-testing\ndescription: Use this skill to build features or debug anything that uses a webapp frontend.\n---\n\n\u003Crequired>\n*CRITICAL* Add the following steps to your Todo list using TodoWrite:\n\n\u003Csystem-reminder>From this point on, ignore any existing tests until you have a working example validated through a new playwright file.\u003C\u002Fsystem-reminder>\n1. Install playwright. Use the SDK that best matches the codebase. Default to python.\n  - Write a playwright config file. Make sure you use reporter: 'list' mode.\n  - If using python, you *must* use a virtual env.\n2. Check to see if you require authentication. If you do, ask me for credentials.\n\u003Csystem-reminder>Do NOT use mock mode or test harnesses. You should be testing the real thing.\u003C\u002Fsystem-reminder>\n3. Write and run a playwright script that lets you interact with the webapp frontend.\n4. Follow these steps in a loop until the bug is fixed:\n  - Add many logs to the server and to the UI. You *MUST* do this on every loop.\n  - Start the server and the UI.\n  - Run the playwright script and identify what is happening. Take screenshots, read logs, do whatever you need to.\n  - Update the playwright script.\n\u003Csystem-reminder>If you get stuck: did you add logs?\u003C\u002Fsystem-reminder>\n5. Run a final demonstration of the playwright browser NOT in headless mode. This is to show me directly what you accomplished.\n6. Clean up all background jobs and close any browsers.\n7. Make sure other tests pass.\n\u003C\u002Frequired>\n\n# Web Application Testing\n\nTo test local web applications, write native Python Playwright scripts. Your\ntesting should be as close to 'real' as possible.\n\n## Example\n\nIdentify the server\n\n**Single server:**\n\n```bash\nnpm run dev\" --port 5173\n```\n\n**Multiple servers (e.g., backend + frontend):**\n\n```bash\ncd backend && python server.py&\ncd frontend && npm run dev&\n```\n\nTo create an automation script, include only Playwright logic\n\n```python\nfrom playwright.sync_api import sync_playwright\n\nwith sync_playwright() as p:\n    browser = p.chromium.launch(headless=True) # Always launch chromium in headless mode\n    page = browser.new_page()\n    page.goto('http:\u002F\u002Flocalhost:5173') # Server already running and ready\n    page.wait_for_load_state('networkidle') # CRITICAL: Wait for JS to execute\n    # ... your automation logic\n    browser.close()\n```\n\n\u003Csystem-reminder>If Playwright is not available, install it in a virtual env.\u003C\u002Fsystem-reminder>\n\nDo NOT get in a loop where you just keep running tests. In this mode, you should ignore tests entirely until it works.\n","\u003Crequired>\n*CRITICAL* Add the following steps to your Todo list using TodoWrite:\n\n\u003Csystem-reminder>From this point on, ignore any existing tests until you have a working example validated through a new playwright file.\u003C\u002Fsystem-reminder>\n1. Install playwright. Use the SDK that best matches the codebase. Default to python.\n  - Write a playwright config file. Make sure you use reporter: 'list' mode.\n  - If using python, you *must* use a virtual env.\n2. Check to see if you require authentication. If you do, ask me for credentials.\n\u003Csystem-reminder>Do NOT use mock mode or test harnesses. You should be testing the real thing.\u003C\u002Fsystem-reminder>\n3. Write and run a playwright script that lets you interact with the webapp frontend.\n4. Follow these steps in a loop until the bug is fixed:\n  - Add many logs to the server and to the UI. You *MUST* do this on every loop.\n  - Start the server and the UI.\n  - Run the playwright script and identify what is happening. Take screenshots, read logs, do whatever you need to.\n  - Update the playwright script.\n\u003Csystem-reminder>If you get stuck: did you add logs?\u003C\u002Fsystem-reminder>\n5. Run a final demonstration of the playwright browser NOT in headless mode. This is to show me directly what you accomplished.\n6. Clean up all background jobs and close any browsers.\n7. Make sure other tests pass.\n\u003C\u002Frequired>\n\n# Web Application Testing\n\nTo test local web applications, write native Python Playwright scripts. Your\ntesting should be as close to 'real' as possible.\n\n## Example\n\nIdentify the server\n\n**Single server:**\n\n```bash\nnpm run dev\" --port 5173\n```\n\n**Multiple servers (e.g., backend + frontend):**\n\n```bash\ncd backend && python server.py&\ncd frontend && npm run dev&\n```\n\nTo create an automation script, include only Playwright logic\n\n```python\nfrom playwright.sync_api import sync_playwright\n\nwith sync_playwright() as p:\n    browser = p.chromium.launch(headless=True) # Always launch chromium in headless mode\n    page = browser.new_page()\n    page.goto('http:\u002F\u002Flocalhost:5173') # Server already running and ready\n    page.wait_for_load_state('networkidle') # CRITICAL: Wait for JS to execute\n    # ... your automation logic\n    browser.close()\n```\n\n\u003Csystem-reminder>If Playwright is not available, install it in a virtual env.\u003C\u002Fsystem-reminder>\n\nDo NOT get in a loop where you just keep running tests. In this mode, you should ignore tests entirely until it works.\n",{"name":5,"description":7},"main","5e94cbfa27965a98428f7d26b69dd5b0a8abeb0d",".agency\u002Fplugins\u002Fnori\u002Fskills\u002Fwebapp-testing",590,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework","https:\u002F\u002Ffluidframework.com","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-14 08:12:05",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add microsoft\u002FFluidFramework --skill webapp-testing",{"tool":56,"command":57},"bunx","bunx skills add microsoft\u002FFluidFramework --skill webapp-testing",{"tool":59,"command":60},"pnpm","pnpm dlx skills add microsoft\u002FFluidFramework --skill webapp-testing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.agency\u002Fplugins\u002Fnori\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",true,[64],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"assets\u002Ffan-out-pool.md","ASSET","资产文件",1353,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fapm\u002Fblob\u002Fmain\u002Fpackages\u002Fautopilot\u002Fautopilot-issue-delivery-scheduler\u002F.apm\u002Fskills\u002Fautopilot-issue-delivery-scheduler\u002Fassets\u002Ffan-out-pool.md",[71,93,130,154,172,193],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":35},"01M6PJ5SAHYFZFWDG5Y4RW56EP","trigger-pipelines-for-copilot-pr","Trigger ADO pipelines for a Copilot-created PR by posting \u002Fazp run comments. Use when the user asks to trigger CI pipelines for a specific PR.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftrigger-pipelines-for-copilot-pr\u002FSKILL.md",[],[78,79,80,81,82,83,84,85,86,87,32,88,89,90,91,92],"pr","trigger pipelines for copilot pr","for","trigger","copilot","pipelines","ado","posting","run","ci","number","URL","comments","user","when",{"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":110,"publishedAt":35},"01M6PJ5M4ZG7E78C4GM4041HEP","review","Review changes relative to a prior state, such as a diff, pull request, branch, commit, or working-tree changes. Use for change-focused code review and regression analysis. Do not use to assess an existing file, API, design, implementation, or other artifact without a comparison; if the request is ambiguous, ask whether the user wants a change review and what prior state to compare against.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Freview\u002FSKILL.md",[99,102,105],{"categoryNo":100,"categoryName":101,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":103,"categoryName":104,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":106,"categoryName":107,"taxonomyType":108,"taxonomyTypeDesc":109},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[95,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127,80,128,129],"branch","regression","code review","design","ask","analysis","code","commit","api","change","artifact","request","pull","tree","as","do","diff","assess","ambiguous",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":139,"publishedAt":35},"01M6PJ5E3PCBDS319FFMHPFACN","review-pr-local","The authority on pulling a pull request — Azure DevOps or GitHub — into an isolated local worktree so a human can review it in their editor, and on posting human-controlled review comments back to the PR (ADO via the ado PR-thread MCP tools or the Azure DevOps REST API, GitHub via the gh CLI). Auto-detects the platform and all identifiers from the PR URL; not tied to any specific repository. The AI assists an interactive human review and only ever posts comments the human explicitly requests. If you find yourself checking out a PR branch over the user's own working tree, or posting AI-authored review prose the human did not ask for, invoke this skill instead.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Freview-pr-local\u002FSKILL.md",[136],{"categoryNo":137,"categoryName":138,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[140,95,78,141,142,143,111,144,145,146,147,148,149,150,89,151,115,119,152,153],"local","review pr local","review pr","back","posts","only","MCP","authority","auto","invoke","azure devops","you","cli","worktree",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":35},"01M6PJ5AVZAS0AEBPCYJZ9ZMMD","policy-check","This skill should be used when the user asks to \"run policy check\", \"check policy\", \"policy-check\", or needs to validate package compliance. Provides guidance on running policy checks for specific packages or the entire repository.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fpolicy-check\u002FSKILL.md",[],[161,162,163,164,165,80,86,166,167,168,169,91,170,92,171],"policy check","policy","check","packages","compliance","repository","guidance","validate","package","running","entire",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":179,"publishedAt":35},"01M6PJ54H068MZF2WD2JDKCVDC","pipeline-test-triage","Triage test failures in an Azure DevOps pipeline run for Fluid Framework. Use when the user shares an ADO build\u002Fpipeline URL or build ID and wants failures analyzed, when they ask \"why did this pipeline fail\", \"summarize the test failures\", \"is this test flaky or a real bug\", \"compare these runs\", or wants bugs filed for genuine failures. Covers the Real Service End to End Tests pipeline as the worked example but applies to any FF test pipeline.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fpipeline-test-triage\u002FSKILL.md",[178],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[180,181,182,183,184,185,186,187,150,89,115,86,188,189,190,191,84,125,192,80,92],"pipeline","test triage","pipeline test triage","pipeline test","test","triage","end","test pipeline","why","bug","but","framework","bugs",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":199,"publishedAt":35},"01M6PJ4ZJASDV2CGQTG1JWKBFE","fluid-release","Fluid Framework client release group — minor releases, patch releases, and post-release type test updates. Covers release prep, branching, version bumps, changelogs, release notes, and type test baselines. In autonomous mode, auto-detects state from the repo, attempts to execute, and falls back to a GitHub issue on failure. Triggers on \"release\", \"do the release\", \"release status\", version bump, release notes, changelog, release branch, or release engineering.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ffluid-release\u002FSKILL.md",[],[200,201,202,143,111,203,204,205,206,207,148,208,209,210,211,212,213,214,215,216],"release","fluid release","fluid","bump","mode","autonomous","release notes","release status","updates","patch","notes","changelog","release prep","releases","status","issue","branching"]