[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PEZP3YP0P38WJAQBJ0RS6M":3,"skill-same:01M6PEZP3YP0P38WJAQBJ0RS6M":96},{"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":57,"commitSha":58,"skillDirectory":59,"forksCount":60,"repositoryHtmlUrl":61,"repositoryHomepageUrl":6,"ownerHtmlUrl":62,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":63,"install":64,"resources":77},"01M6PEZP3YP0P38WJAQBJ0RS6M","overnight-development",null,"Automates software development overnight using Git hooks to enforce test-driven development (TDD).\nThis skill should be used when Claude needs to build new features, refactor existing code, or fix bugs autonomously,\nensuring all changes are fully tested and meet specified quality standards. Use when the user mentions \"overnight development\",\n\"autonomous coding\", or asks about TDD workflows and Git hooks. This skill leverages Git hooks to block commits until all tests pass,\nenforcing a rigorous TDD process and ensuring high-quality, production-ready code.","sandraschi\u002Fdocumentation-mcp","sandraschi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F34750307?v=4","01M6C42H9WE5EC9CK3N5RGZP8S","Sandra Schipal","01M6PE1X2FZP8KR5GANPPFTHA8",2,"MIT","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fnot-mcp-related\u002Fclaude-skills\u002Ftemp\u002Fcode-plugins\u002Fplugins\u002Fproductivity\u002Fovernight-dev\u002Fskills\u002Fovernight-dev\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"development","overnight","overnight development","intent","test-driven","Meet","workflows","features","production-ready","software","io","software development","Bash","code","hooks","ready","fix","autonomous","write","read","2026-11-10 10:12:30",false,"---\nname: overnight-development\ndescription: |\n  Automates software development overnight using Git hooks to enforce test-driven development (TDD).\n  This skill should be used when Claude needs to build new features, refactor existing code, or fix bugs autonomously,\n  ensuring all changes are fully tested and meet specified quality standards. Use when the user mentions \"overnight development\",\n  \"autonomous coding\", or asks about TDD workflows and Git hooks. This skill leverages Git hooks to block commits until all tests pass,\n  enforcing a rigorous TDD process and ensuring high-quality, production-ready code.\nlicense: \"MIT\"\nmetadata:\n  author: \"Intent Solutions IO\"\n  version: \"1.0.0\"\n  category: \"productivity\"\nallowed-tools:\n  - Read\n  - Write\n  - Bash\n---\n\n# Overnight Development\n\n## Overview\n\nThis skill automates software development overnight by leveraging Git hooks to enforce test-driven development (TDD). It ensures that all code changes are fully tested and meet specified quality standards before being committed. This approach allows Claude to work autonomously, building new features, refactoring existing code, or fixing bugs while adhering to a rigorous TDD process.\n\n## Core Capabilities\n\n-   Enforces test-driven development (TDD) using Git hooks.\n-   Automates debugging and code fixing until all tests pass.\n-   Tracks progress and logs activities during overnight sessions.\n-   Supports flexible configuration for various testing frameworks and languages.\n-   Provides guidance and support through the `overnight-dev-coach` agent.\n\n## Workflow\n\n### Phase 1: Project Setup and Configuration\n\nTo prepare the project for overnight development:\n\n1.  **Verify Prerequisites:** Ensure the project is a Git repository, has a configured test framework, and includes at least one passing test.\n    ```bash\n    git init\n    npm install --save-dev jest # Example for Node.js\n    ```\n\n2.  **Install the Plugin:** Add the Claude Code Plugin marketplace and install the `overnight-dev` plugin.\n    ```bash\n    \u002Fplugin marketplace add jeremylongshore\u002Fclaude-code-plugins\n    \u002Fplugin install overnight-dev@claude-code-plugins-plus\n    ```\n\n3.  **Run Setup Command:** Execute the `\u002Fovernight-setup` command to create necessary Git hooks and configuration files.\n    ```bash\n    \u002Fovernight-setup\n    ```\n\n### Phase 2: Task Definition and Planning\n\nTo define the task for the overnight session:\n\n1.  **Define a Clear Goal:** Specify a clear and testable goal for the overnight session, such as \"Build user authentication with JWT (90% coverage).\"\n    ```text\n    Task: Build user authentication with JWT (90% coverage)\n    Success: All tests pass, 90%+ coverage, fully documented\n    ```\n\n2.  **Start Coding:** Begin implementing the feature by writing tests first, following the TDD approach.\n    ```javascript\n    \u002F\u002F Example test case (Node.js with Jest)\n    it('should authenticate a user with valid credentials', async () => {\n      \u002F\u002F Test implementation\n    });\n    ```\n\n3.  **Attempt to Commit:** Try to commit the changes, which will trigger the Git hooks and run the tests.\n    ```bash\n    git commit -m \"feat: implement user authentication\"\n    ```\n\n### Phase 3: Autonomous Development and Debugging\n\nTo allow Claude to work autonomously:\n\n1.  **Git Hooks Enforcement:** The Git hooks will block the commit if any tests fail, providing Claude with the error messages.\n    ```text\n    Overnight Dev: Running pre-commit checks...\n    Running linting...\n    Linting passed\n    Running tests...\n    12 tests failing\n    Commit blocked!\n    ```\n\n2.  **Automated Debugging:** Claude analyzes the error messages, identifies the issues, and attempts to fix the code.\n    ```text\n    Claude: Fixing test failures in user authentication module.\n    ```\n\n3.  **Retry Commits:** Claude retries the commit after making the necessary fixes, repeating the process until all tests pass.\n    ```bash\n    git commit -m \"fix: address test failures in user authentication\"\n    ```\n\n### Phase 4: Progress Tracking and Completion\n\nTo monitor the progress and finalize the session:\n\n1.  **Monitor Progress:** Track the progress of the overnight session by viewing the log file.\n    ```bash\n    cat .overnight-dev-log.txt\n    ```\n\n2.  **Review Results:** Wake up to fully tested code, complete features, and a clean Git history.\n    ```text\n    7 AM: You wake up to:\n    - 47 passing tests (0 failing)\n    - 94% test coverage\n    - Clean conventional commit history\n    - Fully documented JWT authentication\n    - Production-ready code\n    ```\n\n3.  **Session Completion:** The session completes when all tests pass, the code meets the specified quality standards, and the changes are committed.\n\n## Using Bundled Resources\n\n### Scripts\n\nTo automate the setup process, use the `overnight-setup.sh` script:\n\n```bash\n.\u002Fscripts\u002Fovernight-setup.sh\n```\n\nTo track the progress of the overnight session, use the `progress-tracker.py` script:\n\n```bash\n.\u002Fscripts\u002Fprogress-tracker.py --log .overnight-dev-log.txt\n```\n\n### References\n\nFor detailed configuration options, load:\n\n-   [Configuration Reference](.\u002Freferences\u002Fconfiguration_reference.md)\n\nFor best practices on writing effective tests, load:\n\n-   [Testing Best Practices](.\u002Freferences\u002Ftesting_best_practices.md)\n\n### Assets\n\nAvailable templates:\n\n-   `assets\u002Fcommit-template.txt` - Template for generating commit messages.\n-   `assets\u002Freadme-template.md` - Template for generating README files.\n\n## Examples\n\n### Example 1: Building JWT Authentication\n\nUser request: \"Implement JWT authentication with 90% test coverage overnight.\"\n\nWorkflow:\n\n1.  Claude writes failing authentication tests (TDD).\n2.  Claude implements JWT signing (tests still failing).\n3.  Claude debugs token generation (commit blocked, keeps trying).\n4.  Tests pass! Commit succeeds.\n5.  Claude adds middleware (writes tests first).\n6.  Integration tests (debugging edge cases).\n7.  All tests green (Coverage: 94%).\n8.  Claude adds docs, refactors, still green.\n9.  Session complete.\n\n### Example 2: Refactoring Database Layer\n\nUser request: \"Refactor the database layer to use the repository pattern overnight.\"\n\nWorkflow:\n\n1.  Claude analyzes existing tests to ensure no regression.\n2.  Claude implements the repository pattern.\n3.  Tests are run; some fail due to changes in data access.\n4.  Claude updates tests to align with the new repository pattern.\n5.  All tests pass; commit succeeds.\n6.  Claude documents the refactored database layer.\n7.  Session complete.\n\n### Example 3: Fixing a Bug in Payment Processing\n\nUser request: \"Fix the bug in payment processing that causes incorrect amounts to be charged overnight.\"\n\nWorkflow:\n\n1.  Claude reproduces the bug and writes a failing test case.\n2.  Claude analyzes the code and identifies the root cause of the bug.\n3.  Claude fixes the bug and runs the tests.\n4.  The failing test case now passes; all other tests also pass.\n5.  Commit succeeds.\n6.  Claude adds a comment to the code explaining the fix.\n7.  Session complete.\n\n## Best Practices\n\n-   Ensure that the task is well-defined and testable.\n-   Follow the TDD approach by writing tests before implementing features.\n-   Monitor the progress of the overnight session by viewing the log file.\n-   Configure the Git hooks and settings appropriately for the project.\n-   Use the `overnight-dev-coach` agent for guidance and support.\n\n## Troubleshooting\n\n**Issue:** Hooks are not running.\n\n**Solution:** Make sure the hooks are executable:\n\n```bash\nchmod +x .git\u002Fhooks\u002Fpre-commit\nchmod +x .git\u002Fhooks\u002Fcommit-msg\n```\n\n**Issue:** Tests are failing immediately.\n\n**Solution:** Ensure you have at least one passing test:\n\n```bash\nnpm test # Should see: Tests passed\n```\n\n**Issue:** Lint errors are blocking everything.\n\n**Solution:** Enable auto-fix:\n\n```json\n{\n  \"autoFix\": true\n}\n```\n\nOr fix manually:\n\n```bash\nnpm run lint -- --fix\n```\n\n## Integration\n\nThis skill integrates with Git repositories and various testing frameworks. It uses Git hooks to enforce TDD and ensure that all code changes are fully tested. The `overnight-dev-coach` agent provides guidance and support throughout the process.\n\n```bash\n# Example integration with Jest (Node.js)\n{\n  \"testCommand\": \"npm test -- --coverage --watchAll=false\",\n  \"lintCommand\": \"npm run lint\",\n  \"autoFix\": true\n}\n```\n\n```bash\n# Example integration with pytest (Python)\n{\n  \"testCommand\": \"pytest --cov=. --cov-report=term-missing\",\n  \"lintCommand\": \"flake8 . && black --check .\",\n  \"autoFix\": false\n}\n```\n```\n","# Overnight Development\n\n## Overview\n\nThis skill automates software development overnight by leveraging Git hooks to enforce test-driven development (TDD). It ensures that all code changes are fully tested and meet specified quality standards before being committed. This approach allows Claude to work autonomously, building new features, refactoring existing code, or fixing bugs while adhering to a rigorous TDD process.\n\n## Core Capabilities\n\n-   Enforces test-driven development (TDD) using Git hooks.\n-   Automates debugging and code fixing until all tests pass.\n-   Tracks progress and logs activities during overnight sessions.\n-   Supports flexible configuration for various testing frameworks and languages.\n-   Provides guidance and support through the `overnight-dev-coach` agent.\n\n## Workflow\n\n### Phase 1: Project Setup and Configuration\n\nTo prepare the project for overnight development:\n\n1.  **Verify Prerequisites:** Ensure the project is a Git repository, has a configured test framework, and includes at least one passing test.\n    ```bash\n    git init\n    npm install --save-dev jest # Example for Node.js\n    ```\n\n2.  **Install the Plugin:** Add the Claude Code Plugin marketplace and install the `overnight-dev` plugin.\n    ```bash\n    \u002Fplugin marketplace add jeremylongshore\u002Fclaude-code-plugins\n    \u002Fplugin install overnight-dev@claude-code-plugins-plus\n    ```\n\n3.  **Run Setup Command:** Execute the `\u002Fovernight-setup` command to create necessary Git hooks and configuration files.\n    ```bash\n    \u002Fovernight-setup\n    ```\n\n### Phase 2: Task Definition and Planning\n\nTo define the task for the overnight session:\n\n1.  **Define a Clear Goal:** Specify a clear and testable goal for the overnight session, such as \"Build user authentication with JWT (90% coverage).\"\n    ```text\n    Task: Build user authentication with JWT (90% coverage)\n    Success: All tests pass, 90%+ coverage, fully documented\n    ```\n\n2.  **Start Coding:** Begin implementing the feature by writing tests first, following the TDD approach.\n    ```javascript\n    \u002F\u002F Example test case (Node.js with Jest)\n    it('should authenticate a user with valid credentials', async () => {\n      \u002F\u002F Test implementation\n    });\n    ```\n\n3.  **Attempt to Commit:** Try to commit the changes, which will trigger the Git hooks and run the tests.\n    ```bash\n    git commit -m \"feat: implement user authentication\"\n    ```\n\n### Phase 3: Autonomous Development and Debugging\n\nTo allow Claude to work autonomously:\n\n1.  **Git Hooks Enforcement:** The Git hooks will block the commit if any tests fail, providing Claude with the error messages.\n    ```text\n    Overnight Dev: Running pre-commit checks...\n    Running linting...\n    Linting passed\n    Running tests...\n    12 tests failing\n    Commit blocked!\n    ```\n\n2.  **Automated Debugging:** Claude analyzes the error messages, identifies the issues, and attempts to fix the code.\n    ```text\n    Claude: Fixing test failures in user authentication module.\n    ```\n\n3.  **Retry Commits:** Claude retries the commit after making the necessary fixes, repeating the process until all tests pass.\n    ```bash\n    git commit -m \"fix: address test failures in user authentication\"\n    ```\n\n### Phase 4: Progress Tracking and Completion\n\nTo monitor the progress and finalize the session:\n\n1.  **Monitor Progress:** Track the progress of the overnight session by viewing the log file.\n    ```bash\n    cat .overnight-dev-log.txt\n    ```\n\n2.  **Review Results:** Wake up to fully tested code, complete features, and a clean Git history.\n    ```text\n    7 AM: You wake up to:\n    - 47 passing tests (0 failing)\n    - 94% test coverage\n    - Clean conventional commit history\n    - Fully documented JWT authentication\n    - Production-ready code\n    ```\n\n3.  **Session Completion:** The session completes when all tests pass, the code meets the specified quality standards, and the changes are committed.\n\n## Using Bundled Resources\n\n### Scripts\n\nTo automate the setup process, use the `overnight-setup.sh` script:\n\n```bash\n.\u002Fscripts\u002Fovernight-setup.sh\n```\n\nTo track the progress of the overnight session, use the `progress-tracker.py` script:\n\n```bash\n.\u002Fscripts\u002Fprogress-tracker.py --log .overnight-dev-log.txt\n```\n\n### References\n\nFor detailed configuration options, load:\n\n-   [Configuration Reference](.\u002Freferences\u002Fconfiguration_reference.md)\n\nFor best practices on writing effective tests, load:\n\n-   [Testing Best Practices](.\u002Freferences\u002Ftesting_best_practices.md)\n\n### Assets\n\nAvailable templates:\n\n-   `assets\u002Fcommit-template.txt` - Template for generating commit messages.\n-   `assets\u002Freadme-template.md` - Template for generating README files.\n\n## Examples\n\n### Example 1: Building JWT Authentication\n\nUser request: \"Implement JWT authentication with 90% test coverage overnight.\"\n\nWorkflow:\n\n1.  Claude writes failing authentication tests (TDD).\n2.  Claude implements JWT signing (tests still failing).\n3.  Claude debugs token generation (commit blocked, keeps trying).\n4.  Tests pass! Commit succeeds.\n5.  Claude adds middleware (writes tests first).\n6.  Integration tests (debugging edge cases).\n7.  All tests green (Coverage: 94%).\n8.  Claude adds docs, refactors, still green.\n9.  Session complete.\n\n### Example 2: Refactoring Database Layer\n\nUser request: \"Refactor the database layer to use the repository pattern overnight.\"\n\nWorkflow:\n\n1.  Claude analyzes existing tests to ensure no regression.\n2.  Claude implements the repository pattern.\n3.  Tests are run; some fail due to changes in data access.\n4.  Claude updates tests to align with the new repository pattern.\n5.  All tests pass; commit succeeds.\n6.  Claude documents the refactored database layer.\n7.  Session complete.\n\n### Example 3: Fixing a Bug in Payment Processing\n\nUser request: \"Fix the bug in payment processing that causes incorrect amounts to be charged overnight.\"\n\nWorkflow:\n\n1.  Claude reproduces the bug and writes a failing test case.\n2.  Claude analyzes the code and identifies the root cause of the bug.\n3.  Claude fixes the bug and runs the tests.\n4.  The failing test case now passes; all other tests also pass.\n5.  Commit succeeds.\n6.  Claude adds a comment to the code explaining the fix.\n7.  Session complete.\n\n## Best Practices\n\n-   Ensure that the task is well-defined and testable.\n-   Follow the TDD approach by writing tests before implementing features.\n-   Monitor the progress of the overnight session by viewing the log file.\n-   Configure the Git hooks and settings appropriately for the project.\n-   Use the `overnight-dev-coach` agent for guidance and support.\n\n## Troubleshooting\n\n**Issue:** Hooks are not running.\n\n**Solution:** Make sure the hooks are executable:\n\n```bash\nchmod +x .git\u002Fhooks\u002Fpre-commit\nchmod +x .git\u002Fhooks\u002Fcommit-msg\n```\n\n**Issue:** Tests are failing immediately.\n\n**Solution:** Ensure you have at least one passing test:\n\n```bash\nnpm test # Should see: Tests passed\n```\n\n**Issue:** Lint errors are blocking everything.\n\n**Solution:** Enable auto-fix:\n\n```json\n{\n  \"autoFix\": true\n}\n```\n\nOr fix manually:\n\n```bash\nnpm run lint -- --fix\n```\n\n## Integration\n\nThis skill integrates with Git repositories and various testing frameworks. It uses Git hooks to enforce TDD and ensure that all code changes are fully tested. The `overnight-dev-coach` agent provides guidance and support throughout the process.\n\n```bash\n# Example integration with Jest (Node.js)\n{\n  \"testCommand\": \"npm test -- --coverage --watchAll=false\",\n  \"lintCommand\": \"npm run lint\",\n  \"autoFix\": true\n}\n```\n\n```bash\n# Example integration with pytest (Python)\n{\n  \"testCommand\": \"pytest --cov=. --cov-report=term-missing\",\n  \"lintCommand\": \"flake8 . && black --check .\",\n  \"autoFix\": false\n}\n```\n```\n",{"name":5,"license":15,"metadata":49,"description":53,"allowed-tools":54},{"author":50,"version":51,"category":52},"Intent Solutions IO","1.0.0","productivity","Automates software development overnight using Git hooks to enforce test-driven development (TDD).\nThis skill should be used when Claude needs to build new features, refactor existing code, or fix bugs autonomously,\nensuring all changes are fully tested and meet specified quality standards. Use when the user mentions \"overnight development\",\n\"autonomous coding\", or asks about TDD workflows and Git hooks. This skill leverages Git hooks to block commits until all tests pass,\nenforcing a rigorous TDD process and ensuring high-quality, production-ready code.\n",[55,56,36],"Read","Write","master","be156301b65e301887f327d08190ed4f17ba08d2","docs\u002Fnot-mcp-related\u002Fclaude-skills\u002Ftemp\u002Fcode-plugins\u002Fplugins\u002Fproductivity\u002Fovernight-dev\u002Fskills\u002Fovernight-dev",0,"https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp","https:\u002F\u002Fgithub.com\u002Fsandraschi","2026-11-14 11:02:49",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add sandraschi\u002Fdocumentation-mcp --skill overnight-development",{"tool":70,"command":71},"bunx","bunx skills add sandraschi\u002Fdocumentation-mcp --skill overnight-development",{"tool":73,"command":74},"pnpm","pnpm dlx skills add sandraschi\u002Fdocumentation-mcp --skill overnight-development","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fnot-mcp-related\u002Fclaude-skills\u002Ftemp\u002Fcode-plugins\u002Fplugins\u002Fproductivity\u002Fovernight-dev\u002Fskills\u002Fovernight-dev\u002FSKILL.md",true,[78,84,90],{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"assets\u002FREADME.md","ASSET","资产文件",27,"https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fnot-mcp-related\u002Fclaude-skills\u002Ftemp\u002Fcode-plugins\u002Fplugins\u002Fproductivity\u002Fovernight-dev\u002Fskills\u002Fovernight-dev\u002Fassets\u002FREADME.md",{"path":85,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002FREADME.md","REFERENCE","参考文档",31,"https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fnot-mcp-related\u002Fclaude-skills\u002Ftemp\u002Fcode-plugins\u002Fplugins\u002Fproductivity\u002Fovernight-dev\u002Fskills\u002Fovernight-dev\u002Freferences\u002FREADME.md",{"path":91,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":94,"sourceHtmlUrl":95},"scripts\u002FREADME.md","SCRIPT","脚本",28,"https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fnot-mcp-related\u002Fclaude-skills\u002Ftemp\u002Fcode-plugins\u002Fplugins\u002Fproductivity\u002Fovernight-dev\u002Fskills\u002Fovernight-dev\u002Fscripts\u002FREADME.md",[97,120,144,154,179,205],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":107,"publishedAt":44},"01M6PFAWAHEJJCKKVNXEWNK87W","Docs Research","Use MCP Central Docs server to search, ask, and retrieve documentation (FastMCP, standards, packaging).","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fsrc\u002Fdocs_mcp\u002Fskills\u002Fdocs-research\u002FSKILL.md",[103,106],{"categoryNo":104,"categoryName":105,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[108,109,110,111,112,113,114,115,116,117,118,119],"docs research","docs","research","standards","use","packaging","ask","server","search","fastmcp","documentation","MCP",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":44},"01M6PFAN4DAENMY574Q7Q3CB3H","wrappee-drift","Read-only, single-repo audit of a repo's tool coverage against the software it wraps (its current real API\u002Fdocs, not training-data memory) and against comparable\u002Fcompeting wrappers. Trigger when the user says \"wrappee drift\" followed by a repo name, \"capability audit\" followed by a repo name, or asks whether a repo is missing features the wrapped software or a competitor now has. Always scoped to one named repo per invocation -- never trigger this fleet-wide or unprompted; that is explicitly against the SOP. Do NOT trigger for internal fleet-standard compliance (that is drift-scan) or strategic worth\u002Farchive decisions (that is quality-check) -- this is specifically about the gap between the repo's tool list and the wrapped software's\u002Fcompetitors' actual current capabilities.","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fskills\u002Fwrappee-drift\u002FSKILL.md",[],[127,128,129,130,131,132,133,134,31,135,136,137,138,33,139,140,141,142,143,43],"drift","wrappee drift","api","data","audit","capabilities","training","memory","repo audit","competitors","fleet","now","tool list","only","never","coverage","list",{"skillNo":145,"name":146,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":153,"publishedAt":44},"01M6PFADA3X031SK3W3T6X0N6H","modules","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fskills\u002Fwindsurf-mcp-standards\u002Fmodules\u002FSKILL.md",[149,152],{"categoryNo":150,"categoryName":151,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[146],{"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":164,"publishedAt":44},"01M6PFA8YA029N68TW0X31FB1W","mcp-standards","Use when developing MCP servers to access comprehensive standards for scaffolding, packaging, sampling, documentation, testing, error handling, monitoring, and CI\u002FCD workflows.","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fskills\u002Fwindsurf-mcp-standards\u002FSKILL.md",[160,163],{"categoryNo":161,"categoryName":162,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[165,119,111,112,166,167,168,169,170,171,172,173,174,175,176,177,118,30,178,113],"mcp standards","monitoring","sampling","scaffolding","servers","cd","error","for","CI\u002FCD","access","ci","mcp servers","error handling","testing",{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":187,"publishedAt":44},"01M6PFA1XX344WX57B0DJZY94Q","webapp-cua-test","Run the pre-Tauri CUA click-through test (real browser, dev stack, OCR \"Connected\" wait, sidebar nav walk) for a fleet MCP server repo under D:\\Dev\\repos. Trigger when the user says \"cua webapp test\" or \"webapp clickthrough\" followed by a repo name, asks for an e2e click-through of a webapp, or asks whether a webapp boots and connects in a real browser. Not for the installed NSIS app (that is the nsis-build skill \u002F cua-nsis-test) and not for DOM assertions (Playwright), and not for hunting fake data or dead buttons (fakefind).","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fskills\u002Fwebapp-cua-test\u002FSKILL.md",[185,186],{"categoryNo":161,"categoryName":162,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[188,189,190,191,192,119,193,194,195,172,196,197,198,199,200,201,202,203,115,204],"webapp","test","webapp cua test","playwright","mcp server","dev","dom","assertions","trigger","click","app","tauri","repo","stack","e2e","ocr","browser",{"skillNo":206,"name":207,"nameZh":6,"description":208,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":209,"categories":210,"keywords":212,"publishedAt":44},"01M6PF9WYF6NWJR7WVN38TT0WH","ship","Final release gate for a fleet MCP server repo under D:\\Dev\\repos -- run all quality gates, build the release artifact, verify it, commit, push, and cut a GitHub release. Trigger this whenever the user says \"ship it\", \"ship\" followed by a repo name, \"release\" followed by a repo name, or asks to finalize and publish work that's already been done in a repo. This is the terminal step after assfix\u002Fnsis-build, not a substitute for them -- if the repo hasn't been assessed recently, say so before shipping rather than shipping blind.","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fskills\u002Fship\u002FSKILL.md",[211],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[207,200,172,196,213,214,215,216,217,218,219,115,220,193,221,222,223,192,224,119],"gates","ship it","artifact","done","say","work","publish","push","shipping","quality gates","commit","github"]