[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EH5P4HHTWVM7E05DX701QR":3,"skill-same:01M7EH5P4HHTWVM7E05DX701QR":59},{"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":39,"commitSha":40,"skillDirectory":41,"forksCount":14,"repositoryHtmlUrl":42,"repositoryHomepageUrl":42,"ownerHtmlUrl":43,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":44,"install":45,"resources":58},"01M7EH5P4HHTWVM7E05DX701QR","add-webmcp",null,"Analyze an existing web application, identify safe user-visible capabilities across routes, forms, server actions, handlers, and schemas, then implement first-party WebMCP tools and validate discovery and invocation with Stagehand. Use when the user asks to make a codebase agent-ready, expose website features as WebMCP tools, or add WebMCP directly to an app rather than generating a standalone injection script from a URL.","Mr-Nobody-Anonymous\u002FAll-skills","Mr-Nobody-Anonymous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184253119?v=4","01M7AEXFJHKTYQW5R0ZCQQTWFV","anonymous","01M7C00M3GQR4QKP9GZA42GFAK",0,"MIT","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fbrowser-automation\u002Fadd-webmcp\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: add-webmcp\ndescription: \"Analyze an existing web application, identify safe user-visible capabilities across routes, forms, server actions, handlers, and schemas, then implement first-party WebMCP tools and validate discovery and invocation with Stagehand. Use when the user asks to make a codebase agent-ready, expose website features as WebMCP tools, or add WebMCP directly to an app rather than generating a standalone injection script from a URL.\"\ncategory: browser-automation\ndomain: browser-automation\nsubdomain: general\nversion: 1.0.0\nlicense: MIT\nrisk: low\nsource:\n  repository: \"browserbase\u002Fskills\"\n  commit: \"6811ca3116\"\n  imported_at: \"2026-09-20\"\n  license: \"MIT\"\nplatforms:\n  - claude-code\n  - cursor\n  - codex\n  - gemini\n  - antigravity\n  - copilot\n---\n\n\n# Add WebMCP\n\nTurn capabilities already implemented by a web app into maintained, first-party WebMCP tools. Modify the target codebase and its tests; do not introduce a hosted proxy or third-party runtime.\n\nCompatibility: the bundled Stagehand validator requires Node.js 22.18 or newer. Validation needs Chrome\u002FChromium locally or `BROWSERBASE_API_KEY` for a publicly reachable preview.\n\nBe verbose as you work: report what each step found as you go, not only in the final report.\n\nUse `webmcp-gen` instead when the requested output is a standalone init script derived from a live URL. This skill starts from source code and integrates tools into the application.\n\n## 1. Establish the application boundary\n\nRead the target repository's instructions, package manifests, framework configuration, and current git status. Preserve unrelated changes.\n\nSet `ADD_WEBMCP_SKILL_DIR` to the directory containing this file and run the bounded scanner:\n\n```bash\nnode \"$ADD_WEBMCP_SKILL_DIR\u002Fscripts\u002Fscan-codebase.mjs\" \"$TARGET_REPO\"\n```\n\nTreat scanner results as leads, not conclusions. In a monorepo, identify the actual browser app and the server packages it calls before editing.\n\n## 2. Build a capability inventory\n\nTrace each candidate from its user-visible entry point through the client handler, validation schema, server boundary, authorization checks, side effect, and returned state. Look at:\n\n- routes and screens;\n- forms and their submit handlers;\n- server actions, API handlers, RPC procedures, and service clients;\n- Zod, Valibot, Yup, Joi, JSON Schema, or equivalent validators;\n- authentication, authorization, CSRF, idempotency, rate limits, and audit hooks.\n\nPrefer complete user tasks such as `search_catalog` or `save_draft`, not a mechanical tool per endpoint. Exclude internal\u002Fadmin-only operations, authentication bypasses, raw database access, secret-bearing operations, and capabilities the UI does not grant the current user.\n\nFor each selected tool, record its source files, existing validation and authorization boundary, side effects, risk class, confirmation behavior, and a safe fixture input. Read [references\u002Fimplementation-and-validation.md](references\u002Fimplementation-and-validation.md) for the detailed inventory and framework patterns.\n\n## 3. Design the tool contract\n\n- Use a stable verb-noun name and describe the user-visible effect, prerequisites, and important exclusions.\n- Derive JSON Schema from the application's existing validator or domain type. Do not invent a second, looser contract. Close object schemas with `additionalProperties: false` and make the execute-time parser reject unknown fields too; a closed discovery schema backed by a permissive runtime parser is not a closed contract.\n- Return compact JSON-serializable domain results. Do not return DOM nodes, credentials, cookies, tokens, or entire HTML documents.\n- Call the same client\u002Fservice boundary as the UI so existing validation, authorization, observability, and business rules remain authoritative.\n- Validate again inside the handler. Agent-provided input is untrusted.\n- Never echo the request back as the result. Read the outcome from the application's own state, and where that state is updated asynchronously (React and most reactive stores do not reflect a change on the next line), poll until it settles before reading, then report whatever is actually true. Echoing turns a silent no-op into a passing test.\n\nAssign annotations deliberately:\n\n| Risk | Tool design | Annotation and confirmation behavior |\n| --- | --- | --- |\n| Read-only | No state mutation | Register `readOnlyHint: true`; add `untrustedContentHint: true` when output includes page or user-controlled text |\n| Reversible mutation | Drafts, preferences, cart edits | Register `readOnlyHint: false`; preserve auth\u002Fidempotency; test only with disposable state |\n| Consequential or irreversible | Purchase, send, publish, delete, permission changes | Split preview\u002Fprepare from commit where possible; do not add declarative `toolautosubmit`; keep the final action behind the app's real confirmation control |\n\nRegistration uses the current WebMCP hint names `readOnlyHint` and `untrustedContentHint`. Stagehand v4 normalizes discovered annotations to `readOnly`, `untrustedContent`, and, for declarative forms, `autosubmit`. These are hints to the browser or agent, not security enforcement. The application must enforce permissions, validation, confirmation, idempotency, and replay protection.\n\n## 4. Integrate with the application\n\nUse the runtime model context exposed by the browser:\n\n```js\nconst modelContext = navigator.modelContext || document.modelContext;\n```\n\nKeep both accessors: current Chrome exposes `document.modelContext` as a native `ModelContext` while `navigator.modelContext` is `undefined`, so the fallback is load-bearing rather than defensive. The surface is browser-provided and present on any page, so the application ships no polyfill.\n\nRegister imperative tools from a client-only root\u002Fprovider after the application is ready. `registerTool` returns a promise and is idempotent by name — re-registering replaces the previous definition rather than duplicating it, and there is no unregister handle — so remounting and hot reload are safe without teardown. Use declarative form attributes when an existing form already represents the exact task and preserving a visible review step is valuable.\n\nDo not duplicate server business logic in the tool executor. Do not weaken CSRF, same-origin, auth, or confirmation checks to make a smoke test pass. Never embed secrets in browser code.\n\n## 5. Verify the implementation\n\nRun the target's focused tests, typecheck, and production build. Then create a small `webmcp.e2e.json` with every expected tool. Discovery is mandatory; invocation is opt-in per test case and must use synthetic or disposable data.\n\nInstall the validator dependencies once:\n\n```bash\npnpm --dir \"$ADD_WEBMCP_SKILL_DIR\" install --frozen-lockfile\n```\n\nValidate localhost with a Stagehand-launched local browser:\n\n```bash\nnode \"$ADD_WEBMCP_SKILL_DIR\u002Fscripts\u002Fvalidate-stagehand.mjs\" \\\n  --url http:\u002F\u002Flocalhost:3000 \\\n  --config \"$TARGET_REPO\u002Fwebmcp.e2e.json\" \\\n  --local\n```\n\nLocal runs are headed by default so the browser is visible while it validates; pass `--headless` for CI or unattended runs.\n\nIf discovery reports zero tools, check the host before suspecting the code: dev servers commonly bind `localhost` only, so `--url http:\u002F\u002F127.0.0.1:PORT` finds nothing while `http:\u002F\u002Flocalhost:PORT` works. The failure looks identical to tools never registering.\n\nUse `--browserbase` only for a publicly reachable deployed preview. The validator uses Stagehand v4's real `page.tools()`, `tool.invoke()`, and `invocation.result()` path. It refuses consequential invocations unless `--allow-consequential` is explicitly supplied.\n\nAn injected init script is useful for testing the validator itself, but it is not proof that the target app ships its own tools. Final application proof must run without `--init-script`.\n\n## 6. Adversarially verify the tools actually worked\n\nStep 5 proves each tool is discoverable and that its executor ran. It does not prove the tool did what it claimed, and a passing config is not evidence of a sound contract. Run this step last, after step 5 is green, and drive it yourself against the live page rather than encoding it in `webmcp.e2e.json` — the point is to probe inputs the author did not anticipate.\n\nDrive the page with a persistent browser session so probes accumulate against real state. The browse CLI is the lightest option — one global install, and the session survives between commands:\n\n```bash\nbrowse open http:\u002F\u002Flocalhost:3000 --session probe --local --headed\nbrowse eval --session probe '(async()=>{const mc=document.modelContext;const t=(await mc.getTools()).find(x=>x.name===\"my_tool\");try{return \"ACCEPTED \"+JSON.stringify(await mc.executeTool(t,JSON.stringify({\u002F* probe input *\u002F})));}catch(e){return \"REJECTED\";}})()'\nbrowse screenshot --session probe --path \u002Ftmp\u002Feffect.png\n```\n\nThree things will cost time otherwise: `browse open` defaults to a **cloud** browser that cannot reach localhost, so `--local` is required; `browse eval` reliably accepts only single-line scripts, so run one probe per command; and `executeTool` takes the tool **object** plus arguments as a **JSON string** — a plain object fails with \"Failed to parse input arguments\".\n\nAssert on rejected-versus-accepted, not on error text. The WebMCP layer replaces a handler's message with a generic invocation-failed string, so a precise reason never reaches the caller.\n\nUse the discovered `tool.inputSchema` as the thing under test, not as the source of truth. For each tool, probe:\n\n- **Schema closure.** Invoke with an extra field the schema does not declare. A tool honoring §3 rejects it. Acceptance means the closed contract is decorative.\n- **Required fields.** Omit a `required` property. The invocation must fail; a `Completed` status carrying a null or partial result is worse than an error, because the agent believes it succeeded.\n- **Types and constraints.** Send a string where the schema says `number`, an out-of-range value against `minimum`\u002F`maximum`, and a value outside an `enum`. Silent coercion or echo-back means the handler never validated.\n- **Error honesty.** Confirm a tool that should fail reports a non-`Completed` status rather than returning a success-shaped body.\n- **Annotation honesty.** Compare each tool's real `annotations` against the risk you assigned in step 3. A pure lookup advertising `readOnly: false`, or a mutating tool advertising `readOnly: true`, is a defect even though discovery passes.\n- **Clean rejection.** After the malformed probes above, re-read the application's state. A rejected call must leave nothing behind; partial state from a half-applied invocation is a defect the accept\u002Freject result alone will not surface.\n- **Consequential gating.** Never invoke these. Verify the tool declares its risk, that no declarative `toolautosubmit` is present, and that the app's own confirmation control still stands between the agent and the effect.\n\nThen verify the **effect**, not the return value. Invoke the tool, then inspect the application independently — DOM assertions for rendered state, a screenshot when the surface is a canvas or chart. A handler that returns `{saved: true}` without changing anything passes step 5 and fails here. When the surface has no readable DOM, have the tool read back from the application's real store so the returned value is grounded in actual state rather than composed by the executor.\n\nTreat every discrepancy as a defect in the application or the tool contract, and fix it there. Do not loosen a schema, downgrade an annotation, or delete a probe to make this step pass.\n\n## 7. Report the result\n\nList the capabilities considered and explain exclusions. For each implemented tool, report its contract, backing code path, risk\u002Fconfirmation treatment, actual Stagehand discovery\u002Finvocation result, and the step 6 adversarial probes it survived. State any environment or browser support not tested.\n\nFor a comparative benchmark, quality audit, or scored evaluation, read [references\u002Fquality-rubric.md](references\u002Fquality-rubric.md). Apply its qualification gates before reporting numerical scores; do not let a high diagnostic score hide fabricated behavior, an unsafe consequence boundary, or missing production discovery.\n","# Add WebMCP\n\nTurn capabilities already implemented by a web app into maintained, first-party WebMCP tools. Modify the target codebase and its tests; do not introduce a hosted proxy or third-party runtime.\n\nCompatibility: the bundled Stagehand validator requires Node.js 22.18 or newer. Validation needs Chrome\u002FChromium locally or `BROWSERBASE_API_KEY` for a publicly reachable preview.\n\nBe verbose as you work: report what each step found as you go, not only in the final report.\n\nUse `webmcp-gen` instead when the requested output is a standalone init script derived from a live URL. This skill starts from source code and integrates tools into the application.\n\n## 1. Establish the application boundary\n\nRead the target repository's instructions, package manifests, framework configuration, and current git status. Preserve unrelated changes.\n\nSet `ADD_WEBMCP_SKILL_DIR` to the directory containing this file and run the bounded scanner:\n\n```bash\nnode \"$ADD_WEBMCP_SKILL_DIR\u002Fscripts\u002Fscan-codebase.mjs\" \"$TARGET_REPO\"\n```\n\nTreat scanner results as leads, not conclusions. In a monorepo, identify the actual browser app and the server packages it calls before editing.\n\n## 2. Build a capability inventory\n\nTrace each candidate from its user-visible entry point through the client handler, validation schema, server boundary, authorization checks, side effect, and returned state. Look at:\n\n- routes and screens;\n- forms and their submit handlers;\n- server actions, API handlers, RPC procedures, and service clients;\n- Zod, Valibot, Yup, Joi, JSON Schema, or equivalent validators;\n- authentication, authorization, CSRF, idempotency, rate limits, and audit hooks.\n\nPrefer complete user tasks such as `search_catalog` or `save_draft`, not a mechanical tool per endpoint. Exclude internal\u002Fadmin-only operations, authentication bypasses, raw database access, secret-bearing operations, and capabilities the UI does not grant the current user.\n\nFor each selected tool, record its source files, existing validation and authorization boundary, side effects, risk class, confirmation behavior, and a safe fixture input. Read [references\u002Fimplementation-and-validation.md](references\u002Fimplementation-and-validation.md) for the detailed inventory and framework patterns.\n\n## 3. Design the tool contract\n\n- Use a stable verb-noun name and describe the user-visible effect, prerequisites, and important exclusions.\n- Derive JSON Schema from the application's existing validator or domain type. Do not invent a second, looser contract. Close object schemas with `additionalProperties: false` and make the execute-time parser reject unknown fields too; a closed discovery schema backed by a permissive runtime parser is not a closed contract.\n- Return compact JSON-serializable domain results. Do not return DOM nodes, credentials, cookies, tokens, or entire HTML documents.\n- Call the same client\u002Fservice boundary as the UI so existing validation, authorization, observability, and business rules remain authoritative.\n- Validate again inside the handler. Agent-provided input is untrusted.\n- Never echo the request back as the result. Read the outcome from the application's own state, and where that state is updated asynchronously (React and most reactive stores do not reflect a change on the next line), poll until it settles before reading, then report whatever is actually true. Echoing turns a silent no-op into a passing test.\n\nAssign annotations deliberately:\n\n| Risk | Tool design | Annotation and confirmation behavior |\n| --- | --- | --- |\n| Read-only | No state mutation | Register `readOnlyHint: true`; add `untrustedContentHint: true` when output includes page or user-controlled text |\n| Reversible mutation | Drafts, preferences, cart edits | Register `readOnlyHint: false`; preserve auth\u002Fidempotency; test only with disposable state |\n| Consequential or irreversible | Purchase, send, publish, delete, permission changes | Split preview\u002Fprepare from commit where possible; do not add declarative `toolautosubmit`; keep the final action behind the app's real confirmation control |\n\nRegistration uses the current WebMCP hint names `readOnlyHint` and `untrustedContentHint`. Stagehand v4 normalizes discovered annotations to `readOnly`, `untrustedContent`, and, for declarative forms, `autosubmit`. These are hints to the browser or agent, not security enforcement. The application must enforce permissions, validation, confirmation, idempotency, and replay protection.\n\n## 4. Integrate with the application\n\nUse the runtime model context exposed by the browser:\n\n```js\nconst modelContext = navigator.modelContext || document.modelContext;\n```\n\nKeep both accessors: current Chrome exposes `document.modelContext` as a native `ModelContext` while `navigator.modelContext` is `undefined`, so the fallback is load-bearing rather than defensive. The surface is browser-provided and present on any page, so the application ships no polyfill.\n\nRegister imperative tools from a client-only root\u002Fprovider after the application is ready. `registerTool` returns a promise and is idempotent by name — re-registering replaces the previous definition rather than duplicating it, and there is no unregister handle — so remounting and hot reload are safe without teardown. Use declarative form attributes when an existing form already represents the exact task and preserving a visible review step is valuable.\n\nDo not duplicate server business logic in the tool executor. Do not weaken CSRF, same-origin, auth, or confirmation checks to make a smoke test pass. Never embed secrets in browser code.\n\n## 5. Verify the implementation\n\nRun the target's focused tests, typecheck, and production build. Then create a small `webmcp.e2e.json` with every expected tool. Discovery is mandatory; invocation is opt-in per test case and must use synthetic or disposable data.\n\nInstall the validator dependencies once:\n\n```bash\npnpm --dir \"$ADD_WEBMCP_SKILL_DIR\" install --frozen-lockfile\n```\n\nValidate localhost with a Stagehand-launched local browser:\n\n```bash\nnode \"$ADD_WEBMCP_SKILL_DIR\u002Fscripts\u002Fvalidate-stagehand.mjs\" \\\n  --url http:\u002F\u002Flocalhost:3000 \\\n  --config \"$TARGET_REPO\u002Fwebmcp.e2e.json\" \\\n  --local\n```\n\nLocal runs are headed by default so the browser is visible while it validates; pass `--headless` for CI or unattended runs.\n\nIf discovery reports zero tools, check the host before suspecting the code: dev servers commonly bind `localhost` only, so `--url http:\u002F\u002F127.0.0.1:PORT` finds nothing while `http:\u002F\u002Flocalhost:PORT` works. The failure looks identical to tools never registering.\n\nUse `--browserbase` only for a publicly reachable deployed preview. The validator uses Stagehand v4's real `page.tools()`, `tool.invoke()`, and `invocation.result()` path. It refuses consequential invocations unless `--allow-consequential` is explicitly supplied.\n\nAn injected init script is useful for testing the validator itself, but it is not proof that the target app ships its own tools. Final application proof must run without `--init-script`.\n\n## 6. Adversarially verify the tools actually worked\n\nStep 5 proves each tool is discoverable and that its executor ran. It does not prove the tool did what it claimed, and a passing config is not evidence of a sound contract. Run this step last, after step 5 is green, and drive it yourself against the live page rather than encoding it in `webmcp.e2e.json` — the point is to probe inputs the author did not anticipate.\n\nDrive the page with a persistent browser session so probes accumulate against real state. The browse CLI is the lightest option — one global install, and the session survives between commands:\n\n```bash\nbrowse open http:\u002F\u002Flocalhost:3000 --session probe --local --headed\nbrowse eval --session probe '(async()=>{const mc=document.modelContext;const t=(await mc.getTools()).find(x=>x.name===\"my_tool\");try{return \"ACCEPTED \"+JSON.stringify(await mc.executeTool(t,JSON.stringify({\u002F* probe input *\u002F})));}catch(e){return \"REJECTED\";}})()'\nbrowse screenshot --session probe --path \u002Ftmp\u002Feffect.png\n```\n\nThree things will cost time otherwise: `browse open` defaults to a **cloud** browser that cannot reach localhost, so `--local` is required; `browse eval` reliably accepts only single-line scripts, so run one probe per command; and `executeTool` takes the tool **object** plus arguments as a **JSON string** — a plain object fails with \"Failed to parse input arguments\".\n\nAssert on rejected-versus-accepted, not on error text. The WebMCP layer replaces a handler's message with a generic invocation-failed string, so a precise reason never reaches the caller.\n\nUse the discovered `tool.inputSchema` as the thing under test, not as the source of truth. For each tool, probe:\n\n- **Schema closure.** Invoke with an extra field the schema does not declare. A tool honoring §3 rejects it. Acceptance means the closed contract is decorative.\n- **Required fields.** Omit a `required` property. The invocation must fail; a `Completed` status carrying a null or partial result is worse than an error, because the agent believes it succeeded.\n- **Types and constraints.** Send a string where the schema says `number`, an out-of-range value against `minimum`\u002F`maximum`, and a value outside an `enum`. Silent coercion or echo-back means the handler never validated.\n- **Error honesty.** Confirm a tool that should fail reports a non-`Completed` status rather than returning a success-shaped body.\n- **Annotation honesty.** Compare each tool's real `annotations` against the risk you assigned in step 3. A pure lookup advertising `readOnly: false`, or a mutating tool advertising `readOnly: true`, is a defect even though discovery passes.\n- **Clean rejection.** After the malformed probes above, re-read the application's state. A rejected call must leave nothing behind; partial state from a half-applied invocation is a defect the accept\u002Freject result alone will not surface.\n- **Consequential gating.** Never invoke these. Verify the tool declares its risk, that no declarative `toolautosubmit` is present, and that the app's own confirmation control still stands between the agent and the effect.\n\nThen verify the **effect**, not the return value. Invoke the tool, then inspect the application independently — DOM assertions for rendered state, a screenshot when the surface is a canvas or chart. A handler that returns `{saved: true}` without changing anything passes step 5 and fails here. When the surface has no readable DOM, have the tool read back from the application's real store so the returned value is grounded in actual state rather than composed by the executor.\n\nTreat every discrepancy as a defect in the application or the tool contract, and fix it there. Do not loosen a schema, downgrade an annotation, or delete a probe to make this step pass.\n\n## 7. Report the result\n\nList the capabilities considered and explain exclusions. For each implemented tool, report its contract, backing code path, risk\u002Fconfirmation treatment, actual Stagehand discovery\u002Finvocation result, and the step 6 adversarial probes it survived. State any environment or browser support not tested.\n\nFor a comparative benchmark, quality audit, or scored evaluation, read [references\u002Fquality-rubric.md](references\u002Fquality-rubric.md). Apply its qualification gates before reporting numerical scores; do not let a high diagnostic score hide fabricated behavior, an unsafe consequence boundary, or missing production discovery.\n",{"name":5,"risk":24,"domain":25,"source":26,"license":15,"version":30,"category":25,"platforms":31,"subdomain":38,"description":7},"low","browser-automation",{"commit":27,"license":15,"repository":28,"imported_at":29},"6811ca3116","browserbase\u002Fskills","2026-09-20","1.0.0",[32,33,34,35,36,37],"claude-code","cursor","codex","gemini","antigravity","copilot","general","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Fbrowser-automation\u002Fadd-webmcp","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous","2026-11-09 11:45:36",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill add-webmcp",{"tool":51,"command":52},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill add-webmcp",{"tool":54,"command":55},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill add-webmcp","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fbrowser-automation\u002Fadd-webmcp\u002FSKILL.md",true,[],[60,68,75,82,89,96],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":67},"01M7FFFZPC2025JQQHPHDX154J","dei-assessment","Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-assessment\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":67},"01M7FFFWN8H4WA7A6Y398QKB6J","dei-action-plan","Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-action-plan\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":67},"01M7FFFSHTM0QZRVZ2NRJTJ0PY","culture-fit-assessment","Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fculture-fit-assessment\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":67},"01M7FFFMA12RKEQA38KHJSXXPS","cowork-to-code-bridge","Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcowork-to-code-bridge\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":67},"01M7FFFH1F6M8YRGW5V487GH1K","counter-offer-response","Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcounter-offer-response\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":67},"01M7FFFDGEHV8Y7J9N40HZXW52","continuous-feedback-system","Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcontinuous-feedback-system\u002FSKILL.md",[],[]]