{"owner":"nodejs","repo":"node","hasSkills":true,"totalSkillsCount":5,"totalTokensCount":1743,"categories":["root-instruction","mcp-config","marketplace","plugin-manifest","cursor-rule"],"hasMcp":true,"mcpConfig":{"mcpServers":{"node":{"command":"npx","args":["-y","@modelcontextprotocol/server-node"]}}},"found":["AGENTS.md",".cursor/mcp.json",".claude-plugin/marketplace.json",".claude-plugin/plugin.json",".cursorrules (es-module-nodejs-guidelines-cursorrules-prompt-fil.mdc)"],"skills":{"AGENTS.md":"# Agents and Automated Tools\n\nThis document outlines rules and requirements for AI automation agents and automated\ntooling that interact with the Node.js project.\n\nExisting Node.js collaborators (as listed in the README.md) may use AI agents to\ncontribute but must do so responsibly.\n\nNew Node.js contributors should avoid using AI agents to interact with the project.\n\n## Code Contributions\n\n* **No unreviewed automation**: Automated pull requests must not be created without\n  ongoing human oversight. The pull request must be actively maintained by a human\n  contributor who responds to feedback. The AI agent is not permitted to create pull\n  requests, open issues, post comments, respond to reviews, or push commits without\n  ongoing human oversight.\n\n* **Commit responsibility**: Commits created with agent assistance must follow all\n  Node.js [commit message guidelines](./doc/contributing/pull-requests.md#commit-message-guidelines).\n  The human contributor opening the PR takes full responsibility for the changes.\n\n* **Testing and verification**: All changes must pass the Node.js continuous integration.\n  Human judgment must verify that existing tests are not removed or modified inappropriately,\n  and that new tests correctly validate the intended behavior.\n\n### Requirements\n\n* All commits must be signed off by the human user using `Signed-off-by: Your Name <your@email.example>`\n  as an attestation to the [Developer Certificate of Origin](https://developercertificate.org/).\n* AI-assistance must be acknowledged using the `Assisted-by: <agent name>` annotation.\n* AI-authored code contributions must be compatible with the project's licensing and\n  contribution guidelines.\n\n## Prohibited Activities\n\nAI agents **must not**:\n\n* Push to any branch or tag in nodejs/node.\n* Create unsupervised pull requests or issues without active human engagement.\n* Make claims about code without human verification against actual source code.\n* Remove or modify existing tests without human judgment.\n* Interact with the repository through means other than those explicitly authorized.\n* Use commit messages to promote for-profit AI tools or commercial brands. A single\n  `Assisted-by: <agent-name>` annotation is required disclosure, not promotion, and is\n  permitted.\n* Post AI-generated messages directly into pull requests, issues, or project communication\n  channels without direct human review and editing to ensure clarity, accuracy, and respect\n  for collaborator time.\n* Sign off commits using `Signed-off-by: <agent name>` or `Co-authored-by: <agent name>`.\n\n## Violations\n\nAutomated interactions that violate these rules may result in:\n\n* Immediate closure of pull requests without review.\n* Blocking of the automation tool from further interaction with the project.\n* Blocking of the tool's account or its owner from contributing.\n* Reports to relevant platforms or organizations operating the automation.\n\n***\n\nFor more information on AI use in general contributions (not specific to agents),\nsee [AI use policy and guidelines](./doc/contributing/ai-guidelines.md).\n",".cursor/mcp.json":"# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/nodejs/node/HEAD/.cursor/mcp.json)",".claude-plugin/marketplace.json":"# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/nodejs/node/HEAD/.claude-plugin/marketplace.json)",".claude-plugin/plugin.json":"# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/nodejs/node/HEAD/.claude-plugin/plugin.json)",".cursorrules (es-module-nodejs-guidelines-cursorrules-prompt-fil.mdc)":"---\ndescription: \"Cursor rules for ES Module development with Node.js guidelines.\"\nglobs: **/*\nalwaysApply: false\n---\n## General\n\n- Follow best practices, lean towards agile methodologies\n- Prioritize modularity, DRY, performance, and security\n- First break tasks into distinct prioritized steps, then follow the steps\n- Prioritize tasks/steps you’ll address in each response\n- Don't repeat yourself\n- Keep responses very short, unless I include a Vx value:\n  - V0 default, code golf\n  - V1 concise\n  - V2 simple\n  - V3 verbose, DRY with extracted functions\n\n## Code\n\n- Use ES module syntax\n- Where appropriate suggest refactorings and code improvements\n- Favor using the latest ES and nodejs features\n- Don’t apologize for errors: fix them\n  * If you can’t finish code, add TODO: comments\n\n## Comments\n\n- Comments should be created where the operation isn't clear from the code, or where uncommon libraries are used\n- Code must start with path/filename as a one-line comment\n- Comments should describe purpose, not effect\n"},"files":{"AGENTS.md":"# Agents and Automated Tools\n\nThis document outlines rules and requirements for AI automation agents and automated\ntooling that interact with the Node.js project.\n\nExisting Node.js collaborators (as listed in the README.md) may use AI agents to\ncontribute but must do so responsibly.\n\nNew Node.js contributors should avoid using AI agents to interact with the project.\n\n## Code Contributions\n\n* **No unreviewed automation**: Automated pull requests must not be created without\n  ongoing human oversight. The pull request must be actively maintained by a human\n  contributor who responds to feedback. The AI agent is not permitted to create pull\n  requests, open issues, post comments, respond to reviews, or push commits without\n  ongoing human oversight.\n\n* **Commit responsibility**: Commits created with agent assistance must follow all\n  Node.js [commit message guidelines](./doc/contributing/pull-requests.md#commit-message-guidelines).\n  The human contributor opening the PR takes full responsibility for the changes.\n\n* **Testing and verification**: All changes must pass the Node.js continuous integration.\n  Human judgment must verify that existing tests are not removed or modified inappropriately,\n  and that new tests correctly validate the intended behavior.\n\n### Requirements\n\n* All commits must be signed off by the human user using `Signed-off-by: Your Name <your@email.example>`\n  as an attestation to the [Developer Certificate of Origin](https://developercertificate.org/).\n* AI-assistance must be acknowledged using the `Assisted-by: <agent name>` annotation.\n* AI-authored code contributions must be compatible with the project's licensing and\n  contribution guidelines.\n\n## Prohibited Activities\n\nAI agents **must not**:\n\n* Push to any branch or tag in nodejs/node.\n* Create unsupervised pull requests or issues without active human engagement.\n* Make claims about code without human verification against actual source code.\n* Remove or modify existing tests without human judgment.\n* Interact with the repository through means other than those explicitly authorized.\n* Use commit messages to promote for-profit AI tools or commercial brands. A single\n  `Assisted-by: <agent-name>` annotation is required disclosure, not promotion, and is\n  permitted.\n* Post AI-generated messages directly into pull requests, issues, or project communication\n  channels without direct human review and editing to ensure clarity, accuracy, and respect\n  for collaborator time.\n* Sign off commits using `Signed-off-by: <agent name>` or `Co-authored-by: <agent name>`.\n\n## Violations\n\nAutomated interactions that violate these rules may result in:\n\n* Immediate closure of pull requests without review.\n* Blocking of the automation tool from further interaction with the project.\n* Blocking of the tool's account or its owner from contributing.\n* Reports to relevant platforms or organizations operating the automation.\n\n***\n\nFor more information on AI use in general contributions (not specific to agents),\nsee [AI use policy and guidelines](./doc/contributing/ai-guidelines.md).\n",".cursor/mcp.json":"# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/nodejs/node/HEAD/.cursor/mcp.json)",".claude-plugin/marketplace.json":"# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/nodejs/node/HEAD/.claude-plugin/marketplace.json)",".claude-plugin/plugin.json":"# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/nodejs/node/HEAD/.claude-plugin/plugin.json)",".cursorrules (es-module-nodejs-guidelines-cursorrules-prompt-fil.mdc)":"---\ndescription: \"Cursor rules for ES Module development with Node.js guidelines.\"\nglobs: **/*\nalwaysApply: false\n---\n## General\n\n- Follow best practices, lean towards agile methodologies\n- Prioritize modularity, DRY, performance, and security\n- First break tasks into distinct prioritized steps, then follow the steps\n- Prioritize tasks/steps you’ll address in each response\n- Don't repeat yourself\n- Keep responses very short, unless I include a Vx value:\n  - V0 default, code golf\n  - V1 concise\n  - V2 simple\n  - V3 verbose, DRY with extracted functions\n\n## Code\n\n- Use ES module syntax\n- Where appropriate suggest refactorings and code improvements\n- Favor using the latest ES and nodejs features\n- Don’t apologize for errors: fix them\n  * If you can’t finish code, add TODO: comments\n\n## Comments\n\n- Comments should be created where the operation isn't clear from the code, or where uncommon libraries are used\n- Code must start with path/filename as a one-line comment\n- Comments should describe purpose, not effect\n"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","rawUrl":"https://raw.githubusercontent.com/nodejs/node/HEAD/AGENTS.md","title":"AI Agent Protocol & Instructions","category":"root-instruction","format":"markdown","content":"# Agents and Automated Tools\n\nThis document outlines rules and requirements for AI automation agents and automated\ntooling that interact with the Node.js project.\n\nExisting Node.js collaborators (as listed in the README.md) may use AI agents to\ncontribute but must do so responsibly.\n\nNew Node.js contributors should avoid using AI agents to interact with the project.\n\n## Code Contributions\n\n* **No unreviewed automation**: Automated pull requests must not be created without\n  ongoing human oversight. The pull request must be actively maintained by a human\n  contributor who responds to feedback. The AI agent is not permitted to create pull\n  requests, open issues, post comments, respond to reviews, or push commits without\n  ongoing human oversight.\n\n* **Commit responsibility**: Commits created with agent assistance must follow all\n  Node.js [commit message guidelines](./doc/contributing/pull-requests.md#commit-message-guidelines).\n  The human contributor opening the PR takes full responsibility for the changes.\n\n* **Testing and verification**: All changes must pass the Node.js continuous integration.\n  Human judgment must verify that existing tests are not removed or modified inappropriately,\n  and that new tests correctly validate the intended behavior.\n\n### Requirements\n\n* All commits must be signed off by the human user using `Signed-off-by: Your Name <your@email.example>`\n  as an attestation to the [Developer Certificate of Origin](https://developercertificate.org/).\n* AI-assistance must be acknowledged using the `Assisted-by: <agent name>` annotation.\n* AI-authored code contributions must be compatible with the project's licensing and\n  contribution guidelines.\n\n## Prohibited Activities\n\nAI agents **must not**:\n\n* Push to any branch or tag in nodejs/node.\n* Create unsupervised pull requests or issues without active human engagement.\n* Make claims about code without human verification against actual source code.\n* Remove or modify existing tests without human judgment.\n* Interact with the repository through means other than those explicitly authorized.\n* Use commit messages to promote for-profit AI tools or commercial brands. A single\n  `Assisted-by: <agent-name>` annotation is required disclosure, not promotion, and is\n  permitted.\n* Post AI-generated messages directly into pull requests, issues, or project communication\n  channels without direct human review and editing to ensure clarity, accuracy, and respect\n  for collaborator time.\n* Sign off commits using `Signed-off-by: <agent name>` or `Co-authored-by: <agent name>`.\n\n## Violations\n\nAutomated interactions that violate these rules may result in:\n\n* Immediate closure of pull requests without review.\n* Blocking of the automation tool from further interaction with the project.\n* Blocking of the tool's account or its owner from contributing.\n* Reports to relevant platforms or organizations operating the automation.\n\n***\n\nFor more information on AI use in general contributions (not specific to agents),\nsee [AI use policy and guidelines](./doc/contributing/ai-guidelines.md).\n","isInternal":false,"tokens":607,"sizeBytes":3083},{"name":"marketplace.json","path":".claude-plugin/marketplace.json","rawUrl":"https://raw.githubusercontent.com/nodejs/node/HEAD/.claude-plugin/marketplace.json","title":"Claude Plugin Marketplace Catalog","category":"marketplace","format":"json","content":"# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/nodejs/node/HEAD/.claude-plugin/marketplace.json)","tokens":300,"sizeBytes":190},{"name":"plugin.json","path":".claude-plugin/plugin.json","rawUrl":"https://raw.githubusercontent.com/nodejs/node/HEAD/.claude-plugin/plugin.json","title":"claude-plugin Plugin Manifest","category":"plugin-manifest","format":"json","content":"# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/nodejs/node/HEAD/.claude-plugin/plugin.json)","tokens":300,"sizeBytes":176},{"name":"mcp.json","path":".cursor/mcp.json","rawUrl":"https://raw.githubusercontent.com/nodejs/node/HEAD/.cursor/mcp.json","title":"Model Context Protocol (MCP) Configuration","category":"mcp-config","format":"json","content":"# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/nodejs/node/HEAD/.cursor/mcp.json)","tokens":300,"sizeBytes":169},{"name":".cursorrules","path":".cursorrules (es-module-nodejs-guidelines-cursorrules-prompt-fil.mdc)","rawUrl":"https://raw.githubusercontent.com/PatrickJS/awesome-cursorrules/main/rules/es-module-nodejs-guidelines-cursorrules-prompt-fil.mdc","title":"Awesome Cursorrules: es module nodejs guidelines cursorrules prompt fil","category":"cursor-rule","format":"markdown","content":"---\ndescription: \"Cursor rules for ES Module development with Node.js guidelines.\"\nglobs: **/*\nalwaysApply: false\n---\n## General\n\n- Follow best practices, lean towards agile methodologies\n- Prioritize modularity, DRY, performance, and security\n- First break tasks into distinct prioritized steps, then follow the steps\n- Prioritize tasks/steps you’ll address in each response\n- Don't repeat yourself\n- Keep responses very short, unless I include a Vx value:\n  - V0 default, code golf\n  - V1 concise\n  - V2 simple\n  - V3 verbose, DRY with extracted functions\n\n## Code\n\n- Use ES module syntax\n- Where appropriate suggest refactorings and code improvements\n- Favor using the latest ES and nodejs features\n- Don’t apologize for errors: fix them\n  * If you can’t finish code, add TODO: comments\n\n## Comments\n\n- Comments should be created where the operation isn't clear from the code, or where uncommon libraries are used\n- Code must start with path/filename as a one-line comment\n- Comments should describe purpose, not effect\n","tokens":236,"sizeBytes":1029}],"systemPromptSnippet":"<yakaai_skills repo=\"nodejs/node\">\n<!-- File: AGENTS.md (Tokens: ~607 | Category: root-instruction) -->\n# Agents and Automated Tools\n\nThis document outlines rules and requirements for AI automation agents and automated\ntooling that interact with the Node.js project.\n\nExisting Node.js collaborators (as listed in the README.md) may use AI agents to\ncontribute but must do so responsibly.\n\nNew Node.js contributors should avoid using AI agents to interact with the project.\n\n## Code Contributions\n\n* **No unreviewed automation**: Automated pull requests must not be created without\n  ongoing human oversight. The pull request must be actively maintained by a human\n  contributor who responds to feedback. The AI agent is not permitted to create pull\n  requests, open issues, post comments, respond to reviews, or push commits without\n  ongoing human oversight.\n\n* **Commit responsibility**: Commits created with agent assistance must follow all\n  Node.js [commit message guidelines](./doc/contributing/pull-requests.md#commit-message-guidelines).\n  The human contributor opening the PR takes full responsibility for the changes.\n\n* **Testing and verification**: All changes must pass the Node.js continuous integration.\n  Human judgment must verify that existing tests are not removed or modified inappropriately,\n  and that new tests correctly validate the intended behavior.\n\n### Requirements\n\n* All commits must be signed off by the human user using `Signed-off-by: Your Name <your@email.example>`\n  as an attestation to the [Developer Certificate of Origin](https://developercertificate.org/).\n* AI-assistance must be acknowledged using the `Assisted-by: <agent name>` annotation.\n* AI-authored code contributions must be compatible with the project's licensing and\n  contribution guidelines.\n\n## Prohibited Activities\n\nAI agents **must not**:\n\n* Push to any branch or tag in nodejs/node.\n* Create unsupervised pull requests or issues without active human engagement.\n* Make claims about code without human verification against actual source code.\n* Remove or modify existing tests without human judgment.\n* Interact with the repository through means other than those explicitly authorized.\n* Use commit messages to promote for-profit AI tools or commercial brands. A single\n  `Assisted-by: <agent-name>` annotation is required disclosure, not promotion, and is\n  permitted.\n* Post AI-generated messages directly into pull requests, issues, or project communication\n  channels without direct human review and editing to ensure clarity, accuracy, and respect\n  for collaborator time.\n* Sign off commits using `Signed-off-by: <agent name>` or `Co-authored-by: <agent name>`.\n\n## Violations\n\nAutomated interactions that violate these rules may result in:\n\n* Immediate closure of pull requests without review.\n* Blocking of the automation tool from further interaction with the project.\n* Blocking of the tool's account or its owner from contributing.\n* Reports to relevant platforms or organizations operating the automation.\n\n***\n\nFor more information on AI use in general contributions (not specific to agents),\nsee [AI use policy and guidelines](./doc/contributing/ai-guidelines.md).\n\n<!-- File: .claude-plugin/marketplace.json (Tokens: ~300 | Category: marketplace) -->\n# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/nodejs/node/HEAD/.claude-plugin/marketplace.json)\n\n<!-- File: .claude-plugin/plugin.json (Tokens: ~300 | Category: plugin-manifest) -->\n# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/nodejs/node/HEAD/.claude-plugin/plugin.json)\n\n<!-- File: .cursor/mcp.json (Tokens: ~300 | Category: mcp-config) -->\n# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/nodejs/node/HEAD/.cursor/mcp.json)\n\n<!-- File: .cursorrules (es-module-nodejs-guidelines-cursorrules-prompt-fil.mdc) (Tokens: ~236 | Category: cursor-rule) -->\n---\ndescription: \"Cursor rules for ES Module development with Node.js guidelines.\"\nglobs: **/*\nalwaysApply: false\n---\n## General\n\n- Follow best practices, lean towards agile methodologies\n- Prioritize modularity, DRY, performance, and security\n- First break tasks into distinct prioritized steps, then follow the steps\n- Prioritize tasks/steps you’ll address in each response\n- Don't repeat yourself\n- Keep responses very short, unless I include a Vx value:\n  - V0 default, code golf\n  - V1 concise\n  - V2 simple\n  - V3 verbose, DRY with extracted functions\n\n## Code\n\n- Use ES module syntax\n- Where appropriate suggest refactorings and code improvements\n- Favor using the latest ES and nodejs features\n- Don’t apologize for errors: fix them\n  * If you can’t finish code, add TODO: comments\n\n## Comments\n\n- Comments should be created where the operation isn't clear from the code, or where uncommon libraries are used\n- Code must start with path/filename as a one-line comment\n- Comments should describe purpose, not effect\n</yakaai_skills>"}