[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72SPPBQ2WHE3WS0P806ZG4A":3,"skill-same:01M72SPPBQ2WHE3WS0P806ZG4A":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":13,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M72SPPBQ2WHE3WS0P806ZG4A","node-compat",null,"Run a Node.js compatibility test, diagnose failures, and either fix the implementation, skip, or ignore the test. Use when asked to work on node compat tests.","nimbus\u002Fdeno","nimbus","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F14984268?v=4","01M72SP53QDF5F25NWSQZM8EZT","01M72SP54V2Q98GYY2K0V32MP7",0,"MIT","https:\u002F\u002Fgithub.com\u002Fnimbus\u002Fdeno\u002Fblob\u002Fnimbus\u002Fv2.9.7\u002F.claude\u002Fskills\u002Fnode-compat\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: node-compat\ndescription: Run a Node.js compatibility test, diagnose failures, and either fix the implementation, skip, or ignore the test. Use when asked to work on node compat tests.\nargument-hint: \u003Ctest-name>\nallowed-tools: Bash Read Write Edit Glob Grep Agent\n---\n\n# Node Compat Test\n\nWork on Node.js compatibility test `$ARGUMENTS`.\n\n## Step 1: Build and run the test\n\n```sh\n.\u002Fx build\n.\u002Fx test-compat $ARGUMENTS\n```\n\nIf the test passes, report success and ensure test is specified in\n`tests\u002Fnode_compat\u002Fconfig.jsonc`.\n\n## Step 2: Diagnose the failure\n\nRead the test file to understand what it tests:\n\n```sh\n# Tests live under tests\u002Fnode_compat\u002Ftest\u002F\n```\n\nUse `Grep` and `Read` to find the test source, then analyze:\n\n1. **What Node.js API or behavior is being tested?**\n2. **What is the actual error or assertion failure?**\n3. **Where is the relevant Deno implementation?** Check `ext\u002Fnode\u002F` (polyfills,\n   ops, internal bindings), `runtime\u002F`, or `cli\u002F`.\n\nRead the corresponding Node.js docs and\u002For source code to understand the\nexpected behavior.\n\n## Step 3: Classify the failure\n\nDetermine which category this failure falls into:\n\n### A. Fixable bug\n\nThe Deno implementation is wrong or incomplete, but can be corrected. This\nincludes:\n\n- Missing method\u002Fproperty on a polyfill\n- Wrong return value or error type\n- Missing event emission\n- Incorrect argument handling\n- Hard-to-fix but still fundamentally implementable behaviors\n\n**Action:** Fix the implementation (Step 4).\n\n### B. Inherent incompatibility\n\nThe test relies on Node.js internals or architecture that Deno fundamentally\ncannot or will not support:\n\n- `internalBinding()` calls to Node's C++ layer\n- Node.js-specific CLI flags (`--inspect`, `--prof`, etc.)\n- V8 internals exposed through Node-specific APIs\n- Node.js-specific build\u002Faddon tooling (node-gyp internals)\n- Tests for Node.js's own test infrastructure\n\n**Action:** Ignore the test with a reason (Step 5).\n\n### C. Not worth fixing\n\nThe test exercises an edge case or behavior that is technically possible but\nprovides negligible value:\n\n- Extremely obscure error message wording differences\n- Node.js-specific deprecation warnings\n- Behavior that no real-world code depends on\n\n**Action:** Ignore or skip the test with a reason (Step 5).\n\n## Step 4: Fix the implementation\n\nIf the failure is fixable:\n\n1. Locate the relevant code in `ext\u002Fnode\u002F` (or elsewhere).\n2. Implement the fix. Match Node.js behavior - check Node.js docs and\u002For source\n   code, not just what \"seems right.\"\n3. Use lazy-loaded imports where possible.\n4. Use primordials for internal JS code to avoid prototype pollution.\n5. Rebuild the source code with `.\u002Fx build` - this is paramount, changes won't\n   take effect until you do.\n6. Re-run the test to verify the fix:\n\n```sh\n.\u002Fx test-compat $ARGUMENTS\n```\n\n6. Once the test passes, make sure the test is listed in\n   `tests\u002Fnode_compat\u002Fconfig.jsonc` with an empty config:\n\n```jsonc\n\"category\u002Ftest-name.js\": {}\n```\n\nThe entries in `config.jsonc` are sorted alphabetically within their category.\nPlace the new entry in the correct position.\n\n## Step 5: Skip or ignore the test\n\nIf the test cannot or should not be fixed, update\n`tests\u002Fnode_compat\u002Fconfig.jsonc`.\n\n### Ignore (test should never run — inherent incompatibility)\n\n```jsonc\n\"category\u002Ftest-name.js\": {\n  \"ignore\": true,\n  \"reason\": \"Brief, specific explanation of why this can't work in Deno\"\n}\n```\n\n`\"reason\"` must be specified otherwise the lint step will fail!\n\n### Platform-specific skip\n\nIf the test only fails on certain platforms:\n\n```jsonc\n\"category\u002Ftest-name.js\": {\n  \"windows\": false\n}\n```\n\n### Expected failure (test runs but fails with known output)\n\nIf you want the test to run but expect a specific failure:\n\n```jsonc\n\"category\u002Ftest-name.js\": {\n  \"exitCode\": 1,\n  \"output\": \"[WILDCARD]specific error message[WILDCARD]\",\n  \"reason\": \"Brief explanation of why this fails\"\n}\n```\n\nThis is a good middle ground for tests that are generally compatible but have a\nspecific known issue. If a fix is ever done this assertion will notify the\nimplementer to update the config.\n\n### Writing good reasons\n\nReasons should be specific and actionable. Good examples:\n\n- \"Tests Node.js internal C++ binding (internalBinding('zlib').Zlib) which is\n  not implemented in Deno\"\n- \"requires `deno --interactive` flag (not yet implemented)\"\n- \"URL.createObjectURL does not throw ERR_INVALID_ARG_TYPE for non-Blob\n  arguments\"\n\nBad examples:\n\n- \"Not supported\" (too vague)\n- \"Doesn't work\" (says nothing)\n- \"Node-specific\" (which part?)\n\n## Step 6: Verify\n\nRe-run the test one final time to confirm the outcome matches expectations:\n\n```sh\n.\u002Fx test-compat $ARGUMENTS\n```\n\n## Config reference\n\nThe full schema for `config.jsonc` entries is in\n`tests\u002Fnode_compat\u002Fschema.json`.\n\n## PR title conventions\n\nWhen opening a PR for node-compat work, use the appropriate prefix:\n\n- `test:` — when the PR only updates `tests\u002Fnode_compat\u002Fconfig.jsonc` to skip,\n  ignore, or otherwise reclassify tests without changing implementation code.\n- `fix(ext\u002Fnode):` — when the PR actually fixes the implementation so a\n  previously failing test now passes (typically changes under `ext\u002Fnode\u002F` plus\n  enabling the test in `config.jsonc`).\n","# Node Compat Test\n\nWork on Node.js compatibility test `$ARGUMENTS`.\n\n## Step 1: Build and run the test\n\n```sh\n.\u002Fx build\n.\u002Fx test-compat $ARGUMENTS\n```\n\nIf the test passes, report success and ensure test is specified in\n`tests\u002Fnode_compat\u002Fconfig.jsonc`.\n\n## Step 2: Diagnose the failure\n\nRead the test file to understand what it tests:\n\n```sh\n# Tests live under tests\u002Fnode_compat\u002Ftest\u002F\n```\n\nUse `Grep` and `Read` to find the test source, then analyze:\n\n1. **What Node.js API or behavior is being tested?**\n2. **What is the actual error or assertion failure?**\n3. **Where is the relevant Deno implementation?** Check `ext\u002Fnode\u002F` (polyfills,\n   ops, internal bindings), `runtime\u002F`, or `cli\u002F`.\n\nRead the corresponding Node.js docs and\u002For source code to understand the\nexpected behavior.\n\n## Step 3: Classify the failure\n\nDetermine which category this failure falls into:\n\n### A. Fixable bug\n\nThe Deno implementation is wrong or incomplete, but can be corrected. This\nincludes:\n\n- Missing method\u002Fproperty on a polyfill\n- Wrong return value or error type\n- Missing event emission\n- Incorrect argument handling\n- Hard-to-fix but still fundamentally implementable behaviors\n\n**Action:** Fix the implementation (Step 4).\n\n### B. Inherent incompatibility\n\nThe test relies on Node.js internals or architecture that Deno fundamentally\ncannot or will not support:\n\n- `internalBinding()` calls to Node's C++ layer\n- Node.js-specific CLI flags (`--inspect`, `--prof`, etc.)\n- V8 internals exposed through Node-specific APIs\n- Node.js-specific build\u002Faddon tooling (node-gyp internals)\n- Tests for Node.js's own test infrastructure\n\n**Action:** Ignore the test with a reason (Step 5).\n\n### C. Not worth fixing\n\nThe test exercises an edge case or behavior that is technically possible but\nprovides negligible value:\n\n- Extremely obscure error message wording differences\n- Node.js-specific deprecation warnings\n- Behavior that no real-world code depends on\n\n**Action:** Ignore or skip the test with a reason (Step 5).\n\n## Step 4: Fix the implementation\n\nIf the failure is fixable:\n\n1. Locate the relevant code in `ext\u002Fnode\u002F` (or elsewhere).\n2. Implement the fix. Match Node.js behavior - check Node.js docs and\u002For source\n   code, not just what \"seems right.\"\n3. Use lazy-loaded imports where possible.\n4. Use primordials for internal JS code to avoid prototype pollution.\n5. Rebuild the source code with `.\u002Fx build` - this is paramount, changes won't\n   take effect until you do.\n6. Re-run the test to verify the fix:\n\n```sh\n.\u002Fx test-compat $ARGUMENTS\n```\n\n6. Once the test passes, make sure the test is listed in\n   `tests\u002Fnode_compat\u002Fconfig.jsonc` with an empty config:\n\n```jsonc\n\"category\u002Ftest-name.js\": {}\n```\n\nThe entries in `config.jsonc` are sorted alphabetically within their category.\nPlace the new entry in the correct position.\n\n## Step 5: Skip or ignore the test\n\nIf the test cannot or should not be fixed, update\n`tests\u002Fnode_compat\u002Fconfig.jsonc`.\n\n### Ignore (test should never run — inherent incompatibility)\n\n```jsonc\n\"category\u002Ftest-name.js\": {\n  \"ignore\": true,\n  \"reason\": \"Brief, specific explanation of why this can't work in Deno\"\n}\n```\n\n`\"reason\"` must be specified otherwise the lint step will fail!\n\n### Platform-specific skip\n\nIf the test only fails on certain platforms:\n\n```jsonc\n\"category\u002Ftest-name.js\": {\n  \"windows\": false\n}\n```\n\n### Expected failure (test runs but fails with known output)\n\nIf you want the test to run but expect a specific failure:\n\n```jsonc\n\"category\u002Ftest-name.js\": {\n  \"exitCode\": 1,\n  \"output\": \"[WILDCARD]specific error message[WILDCARD]\",\n  \"reason\": \"Brief explanation of why this fails\"\n}\n```\n\nThis is a good middle ground for tests that are generally compatible but have a\nspecific known issue. If a fix is ever done this assertion will notify the\nimplementer to update the config.\n\n### Writing good reasons\n\nReasons should be specific and actionable. Good examples:\n\n- \"Tests Node.js internal C++ binding (internalBinding('zlib').Zlib) which is\n  not implemented in Deno\"\n- \"requires `deno --interactive` flag (not yet implemented)\"\n- \"URL.createObjectURL does not throw ERR_INVALID_ARG_TYPE for non-Blob\n  arguments\"\n\nBad examples:\n\n- \"Not supported\" (too vague)\n- \"Doesn't work\" (says nothing)\n- \"Node-specific\" (which part?)\n\n## Step 6: Verify\n\nRe-run the test one final time to confirm the outcome matches expectations:\n\n```sh\n.\u002Fx test-compat $ARGUMENTS\n```\n\n## Config reference\n\nThe full schema for `config.jsonc` entries is in\n`tests\u002Fnode_compat\u002Fschema.json`.\n\n## PR title conventions\n\nWhen opening a PR for node-compat work, use the appropriate prefix:\n\n- `test:` — when the PR only updates `tests\u002Fnode_compat\u002Fconfig.jsonc` to skip,\n  ignore, or otherwise reclassify tests without changing implementation code.\n- `fix(ext\u002Fnode):` — when the PR actually fixes the implementation so a\n  previously failing test now passes (typically changes under `ext\u002Fnode\u002F` plus\n  enabling the test in `config.jsonc`).\n",{"name":5,"description":7,"allowed-tools":23,"argument-hint":24},"Bash Read Write Edit Glob Grep Agent","\u003Ctest-name>","nimbus\u002Fv2.9.7","1abfdad63da77afe1517efc0190063e49f479748",".claude\u002Fskills\u002Fnode-compat","https:\u002F\u002Fgithub.com\u002Fnimbus\u002Fdeno","https:\u002F\u002Fgithub.com\u002Fnimbus","2026-10-02 00:53:17",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add nimbus\u002Fdeno --skill node-compat",{"tool":37,"command":38},"bunx","bunx skills add nimbus\u002Fdeno --skill node-compat",{"tool":40,"command":41},"pnpm","pnpm dlx skills add nimbus\u002Fdeno --skill node-compat","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnimbus\u002Fdeno\u002Fblob\u002Fnimbus\u002Fv2.9.7\u002F.claude\u002Fskills\u002Fnode-compat\u002FSKILL.md",true,[],[46,53,60,67,74],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M72SPTFW41HMSPDTBSTNNKNB","review-pr","Review a Deno runtime pull request for correctness, tests, security, and conventions. Use when asked to review a PR or when a PR number\u002FURL is provided for review.","https:\u002F\u002Fgithub.com\u002Fnimbus\u002Fdeno\u002Fblob\u002Fnimbus\u002Fv2.9.7\u002F.claude\u002Fskills\u002Freview-pr\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M72SPMSNW1GA7J1GQN6FYFK2","lint-js","Lint JS\u002FTS code only. Use before opening a PR when only JavaScript or TypeScript files were changed (no Rust).","https:\u002F\u002Fgithub.com\u002Fnimbus\u002Fdeno\u002Fblob\u002Fnimbus\u002Fv2.9.7\u002F.claude\u002Fskills\u002Flint-js\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M72SPKK1VMJQE7592P3E83W6","lint-all","Lint all code (Rust + JS\u002FTS). Use before opening a PR when Rust code was changed.","https:\u002F\u002Fgithub.com\u002Fnimbus\u002Fdeno\u002Fblob\u002Fnimbus\u002Fv2.9.7\u002F.claude\u002Fskills\u002Flint-all\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M72SPFBZ0117NFHBTNG2WGAS","issue-triage","Triage a Deno GitHub issue — reproduce bugs, classify, label, and comment with findings. Use when asked to triage an issue or when an issue number\u002FURL is provided for triage.","https:\u002F\u002Fgithub.com\u002Fnimbus\u002Fdeno\u002Fblob\u002Fnimbus\u002Fv2.9.7\u002F.claude\u002Fskills\u002Fissue-triage\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M72SPDSPTKS7VBV45KEJAX6H","fmt","Format all code in the repository. Run before opening a PR or committing changes.","https:\u002F\u002Fgithub.com\u002Fnimbus\u002Fdeno\u002Fblob\u002Fnimbus\u002Fv2.9.7\u002F.claude\u002Fskills\u002Ffmt\u002FSKILL.md",[],[]]