[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PHTP4J3R3169KC3YG8W336":3,"skill-same:01M6PHTP4J3R3169KC3YG8W336":79},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":72},"01M6PHTP4J3R3169KC3YG8W336","playwright-audit-deps",null,"Roll the runtime dependencies that npm audit flags with a moderate or higher advisory to safe versions that are at least 8 days old, and commit them with a table of every package the lock file change touched (old and new version, publish date, weekly downloads). Use when asked to fix audit findings, bump vulnerable or outdated runtime dependencies, or update package-lock.json for an advisory.","microsoft\u002Fplaywright","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M6998NK29WMCQG4W7K65QXNR",99877,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fplaywright\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fplaywright-audit-deps\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"playwright audit deps","playwright","audit","deps","table","flags","safe","at","update","fix audit","change","when","publish","lock","commit","fix","bump","for","downloads","weekly","2026-11-10 10:12:30",false,"---\nname: playwright-audit-deps\ndescription: Roll the runtime dependencies that npm audit flags with a moderate or higher advisory to safe versions that are at least 8 days old, and commit them with a table of every package the lock file change touched (old and new version, publish date, weekly downloads). Use when asked to fix audit findings, bump vulnerable or outdated runtime dependencies, or update package-lock.json for an advisory.\nuser_invocable: true\n---\n\n# Roll runtime dependencies flagged by npm audit\n\n`\u002Fplaywright-audit-deps [issue url]`\n\nA runtime dependency is a package whose code ends up in a published Playwright package: it is\ninlined into a bundle (listed in a `packages\u002F*\u002Flib\u002F**\u002F*.js.txt` sidecar) or named in the\n`dependencies` of a `packages\u002F*\u002Fpackage.json`. Advisories on dev-only packages, such as eslint\nplugins or chromium-bidi, are reported as skipped and left alone.\n\nA version is eligible when it is outside every advisory range, was published at least 8 days\nago, and is accepted by every runtime dependent in `package-lock.json`. The newest eligible\nversion wins. Packages that `npm install` pulls in beyond that age are pinned back the same way.\n\nThe lint `npm run check-dependency-age` (part of `npm run lint` and `npm run flint`, so CI\nruns it on every PR) fails when any version in `package-lock.json` is less than 7 days old.\nThe 8-day default here keeps a one-day margin above that limit.\n\n## Steps\n\n1. Start from a clean checkout of `main` with `npm run build` done, so the bundle sidecars\n   exist. Create the branch: `fix-\u003Cissue number>` when an issue is given, else `bump-runtime-deps`.\n\n2. Plan: `node .claude\u002Fskills\u002Fplaywright-audit-deps\u002Faudit-deps.mjs`. It prints, per runtime\n   advisory, the version it would roll to, or why it cannot (no fixed version, fixed version too\n   new, a runtime dependent rejects it, or a major bump of a package pinned in `package.json`).\n\n3. Apply: `node .claude\u002Fskills\u002Fplaywright-audit-deps\u002Faudit-deps.mjs --apply --report=\u003Cscratchpad>\u002Fdeps-report.md`.\n   Pass `--allow-major` only when the user asked for a major bump; otherwise leave those\n   packages in the \"Not rolled\" list and tell the user. Options: `--max-age-days=N` (default 8),\n   `--severity=low|moderate|high|critical` (default moderate), `--base=\u003Cref>` for the report diff.\n\n4. Verify: `npm run build`, then `npm run itest tests\u002Finstallation\u002Fbundle-licenses.spec.ts tests\u002Finstallation\u002Fbundle-size.spec.ts`\n   and `npm run check-dependency-age`. A new dependency without a `repository` field, a bigger\n   bundle, or a version younger than 7 days fails here. Fix the cause or drop that roll, then\n   rerun the report.\n\n5. Commit `package.json` and `package-lock.json` as one commit:\n\n   ```\n   chore(deps): bump runtime deps\n\n   \u003Cthe markdown table and the \"Not rolled\" list from the report>\n\n   Fixes: \u003Cissue url, when given>\n   ```\n\n6. Report the table and the not-rolled packages to the user. **Never push.** When told to open\n   the PR, use the same title and a body of one bullet naming the packages rolled for an\n   advisory, the table, and the `Fixes` line.\n\n## Notes\n\n- `npm audit` lists a package that only depends on a vulnerable one (chromium-bidi via zod)\n  as its own finding; the script follows the actual advisory, so such entries are not acted on.\n- A root-pinned package is bumped with `npm install \u003Cname>@\u003Cversion> --save-exact`. Any other\n  package is rewritten in place in `package-lock.json` and reconciled with `npm install`. The\n  script fails if `npm ls` reports a problem afterwards.\n- Run the apply step once from the clean base; a second run labels the already rolled packages\n  as plain dependencies in the \"Reason\" column, because the audit no longer flags them.\n","# Roll runtime dependencies flagged by npm audit\n\n`\u002Fplaywright-audit-deps [issue url]`\n\nA runtime dependency is a package whose code ends up in a published Playwright package: it is\ninlined into a bundle (listed in a `packages\u002F*\u002Flib\u002F**\u002F*.js.txt` sidecar) or named in the\n`dependencies` of a `packages\u002F*\u002Fpackage.json`. Advisories on dev-only packages, such as eslint\nplugins or chromium-bidi, are reported as skipped and left alone.\n\nA version is eligible when it is outside every advisory range, was published at least 8 days\nago, and is accepted by every runtime dependent in `package-lock.json`. The newest eligible\nversion wins. Packages that `npm install` pulls in beyond that age are pinned back the same way.\n\nThe lint `npm run check-dependency-age` (part of `npm run lint` and `npm run flint`, so CI\nruns it on every PR) fails when any version in `package-lock.json` is less than 7 days old.\nThe 8-day default here keeps a one-day margin above that limit.\n\n## Steps\n\n1. Start from a clean checkout of `main` with `npm run build` done, so the bundle sidecars\n   exist. Create the branch: `fix-\u003Cissue number>` when an issue is given, else `bump-runtime-deps`.\n\n2. Plan: `node .claude\u002Fskills\u002Fplaywright-audit-deps\u002Faudit-deps.mjs`. It prints, per runtime\n   advisory, the version it would roll to, or why it cannot (no fixed version, fixed version too\n   new, a runtime dependent rejects it, or a major bump of a package pinned in `package.json`).\n\n3. Apply: `node .claude\u002Fskills\u002Fplaywright-audit-deps\u002Faudit-deps.mjs --apply --report=\u003Cscratchpad>\u002Fdeps-report.md`.\n   Pass `--allow-major` only when the user asked for a major bump; otherwise leave those\n   packages in the \"Not rolled\" list and tell the user. Options: `--max-age-days=N` (default 8),\n   `--severity=low|moderate|high|critical` (default moderate), `--base=\u003Cref>` for the report diff.\n\n4. Verify: `npm run build`, then `npm run itest tests\u002Finstallation\u002Fbundle-licenses.spec.ts tests\u002Finstallation\u002Fbundle-size.spec.ts`\n   and `npm run check-dependency-age`. A new dependency without a `repository` field, a bigger\n   bundle, or a version younger than 7 days fails here. Fix the cause or drop that roll, then\n   rerun the report.\n\n5. Commit `package.json` and `package-lock.json` as one commit:\n\n   ```\n   chore(deps): bump runtime deps\n\n   \u003Cthe markdown table and the \"Not rolled\" list from the report>\n\n   Fixes: \u003Cissue url, when given>\n   ```\n\n6. Report the table and the not-rolled packages to the user. **Never push.** When told to open\n   the PR, use the same title and a body of one bullet naming the packages rolled for an\n   advisory, the table, and the `Fixes` line.\n\n## Notes\n\n- `npm audit` lists a package that only depends on a vulnerable one (chromium-bidi via zod)\n  as its own finding; the script follows the actual advisory, so such entries are not acted on.\n- A root-pinned package is bumped with `npm install \u003Cname>@\u003Cversion> --save-exact`. Any other\n  package is rewritten in place in `package-lock.json` and reconciled with `npm install`. The\n  script fails if `npm ls` reports a problem afterwards.\n- Run the apply step once from the clean base; a second run labels the already rolled packages\n  as plain dependencies in the \"Reason\" column, because the audit no longer flags them.\n",{"name":5,"description":7,"user_invocable":49},true,"main","07c7069cdbb1f5c7331d3f4d2abd864dcfde745a",".claude\u002Fskills\u002Fplaywright-audit-deps",6849,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fplaywright","https:\u002F\u002Fplaywright.dev","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-12 03:04:51",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":49},[62,65,68],{"tool":63,"command":64},"npx","npx skills add microsoft\u002Fplaywright --skill playwright-audit-deps",{"tool":66,"command":67},"bunx","bunx skills add microsoft\u002Fplaywright --skill playwright-audit-deps",{"tool":69,"command":70},"pnpm","pnpm dlx skills add microsoft\u002Fplaywright --skill playwright-audit-deps","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fplaywright\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fplaywright-audit-deps\u002FSKILL.md",[73],{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"audit-deps.mjs","SCRIPT","脚本",14528,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fplaywright\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fplaywright-audit-deps\u002Faudit-deps.mjs",[80,104,134,152,177,199],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":87,"publishedAt":44},"01M6999MNG7F462VPA3A3DQT1D","playwright-trace","Inspect Playwright trace files from the command line — list actions, view requests, console, errors, snapshots and screenshots.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fplaywright\u002Fblob\u002Fmain\u002Fpackages\u002Fplaywright-core\u002Fsrc\u002Ftools\u002Fskills\u002Fplaywright-trace\u002FSKILL.md",[86],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[25,88,89,90,91,92,93,94,63,95,96,97,98,99,100,101,102,103],"playwright trace","trace","screenshots","view","inspect","actions","errors","files","snapshots","Bash","requests","command","line","command line","console","list",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":114,"publishedAt":44},"01M6999HEFRKHCK11RJYDBHG5N","playwright-component-testing","Set up component testing with Playwright using a story gallery — scaffold stories and a gallery dev page driven by the built-in mount fixture, no dedicated component-testing runtime. Use when asked to test React or Vue components in isolation with Playwright, or to migrate off @playwright\u002Fexperimental-ct-react \u002F -vue.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fplaywright\u002Fblob\u002Fmain\u002Fpackages\u002Fplaywright-core\u002Fsrc\u002Ftools\u002Fskills\u002Fplaywright-component-testing\u002FSKILL.md",[110,111],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":112,"categoryName":113,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[25,115,116,117,118,119,120,121,35,122,123,124,125,126,127,128,129,130,131,132,133],"playwright component testing","testing","component","test","SET","fixture","up","migrate","components","react","gallery","vue","isolation","runtime","page","dev","use","stories","with",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":141,"publishedAt":44},"01M6999DVV27DR1Q2WMH329ST3","playwright-cli","Automate browser interactions, test web pages and work with Playwright tests.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fplaywright\u002Fblob\u002Fmain\u002Fpackages\u002Fplaywright-core\u002Fsrc\u002Ftools\u002Fskills\u002Fplaywright-cli\u002FSKILL.md",[140],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[25,142,143,118,144,136,97,145,146,147,148,149,150,151,63,133],"cli","playwright cli","web","browser","work","test web","install","automate","pages","tests",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":162,"publishedAt":44},"01M69998DRR0DMSH3N60ZCWVKB","playwright-test-results","Query Playwright CI test results from the aggregated DuckDB database. Answers questions about flaky tests, failure rates, slow tests, and per-run\u002FSHA\u002FPR results without hunting through GitHub artifacts.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fplaywright\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fplaywright-test-results\u002FSKILL.md",[158,159],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":160,"categoryName":161,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[163,25,118,164,165,166,167,168,151,169,170,171,172,173,174,175,176],"playwright test results","results","github","pr","ci","true","database","query","artifacts","hunting","run","questions","about","duckdb",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":184,"publishedAt":44},"01M69995VG17SFSMYC2F5VQTTC","playwright-release-notes","Write the release notes for a Playwright release - the Node.js notes in docs\u002Fsrc\u002Frelease-notes-js.md together with the Python, Java and .NET translations, and the GitHub markdown for each language's release. Use when asked to write, translate or publish release notes.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fplaywright\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fplaywright-release-notes\u002FSKILL.md",[183],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[25,185,186,187,188,189,165,190,191,192,193,41,131,35,194,36,133,195,196,197,198],"playwright release notes","release notes","notes","release","playwright release","translate","python","docs","release-notes","java","markdown","src","write","node",{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":203,"categories":204,"keywords":206,"publishedAt":44},"01M699938PWX7P2KS04997VVZD","playwright-devops","DevOps workflows for Playwright - CI failure analysis, workflow debugging, and release operations.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fplaywright\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fplaywright-devops\u002FSKILL.md",[205],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[25,207,208,209,41,210,167,168,211,212,213,214,188],"playwright devops","devops","workflow","failure analysis","debugging","workflows","analysis","operations"]