[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PF7DWDWTA83G4THV3FTBCG":3,"skill-same:01M6PF7DWDWTA83G4THV3FTBCG":94},{"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":29,"publishedAt":50,"linkOnly":51,"markdownContent":52,"markdownBody":53,"frontMatter":54,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":6,"ownerHtmlUrl":60,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":61,"install":62,"resources":75},"01M6PF7DWDWTA83G4THV3FTBCG","orchestrating-test-workflows",null,"This skill enables Claude to orchestrate complex test workflows using the test-orchestrator plugin. It allows Claude to define test execution graphs with dependencies, execute tests in parallel, and intelligently select tests to run based on code changes. Use this skill when a user requests test orchestration, dependency management for tests, parallel test execution, smart test selection, or CI\u002FCD integration for testing. Trigger terms include \"orchestrate tests\", \"test workflow\", \"parallel testing\", \"smart test selection\", \"test dependencies\", and \"\u002Forchestrate\".","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\u002Ftesting\u002Ftest-orchestrator\u002Fskills\u002Ftest-orchestrator\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49],"test","workflows","Orchestrating Test Workflows","select","for","CI\u002FCD","test execution","trigger","selection","dependency","orchestrator","dependency management","testing","parallel","ci","orchestrate","code","run","workflow","orchestration","2026-11-10 10:12:30",false,"---\nname: orchestrating-test-workflows\ndescription: |\n  This skill enables Claude to orchestrate complex test workflows using the test-orchestrator plugin. It allows Claude to define test execution graphs with dependencies, execute tests in parallel, and intelligently select tests to run based on code changes. Use this skill when a user requests test orchestration, dependency management for tests, parallel test execution, smart test selection, or CI\u002FCD integration for testing. Trigger terms include \"orchestrate tests\", \"test workflow\", \"parallel testing\", \"smart test selection\", \"test dependencies\", and \"\u002Forchestrate\".\n---\n\n## Overview\n\nThis skill empowers Claude to manage and execute complex test suites efficiently. It leverages the test-orchestrator plugin to handle test dependencies, parallel execution, and intelligent test selection, resulting in faster and more reliable testing processes.\n\n## How It Works\n\n1. **Workflow Definition**: Claude uses the plugin to define the test workflow, specifying dependencies between tests.\n2. **Parallelization**: The plugin identifies independent tests and executes them in parallel to reduce overall execution time.\n3. **Smart Selection**: Based on code changes, the plugin selects only the affected tests to run, minimizing unnecessary execution.\n\n## When to Use This Skill\n\nThis skill activates when you need to:\n- Optimize test execution time.\n- Manage dependencies between tests.\n- Run only relevant tests after code changes.\n\n## Examples\n\n### Example 1: Optimizing Regression Testing\n\nUser request: \"Orchestrate the regression tests for the user authentication module after the recent code changes.\"\n\nThe skill will:\n1. Use the test-orchestrator plugin to identify the tests affected by the changes in the user authentication module.\n2. Execute those tests in parallel, respecting any dependencies.\n\n### Example 2: Setting up a CI\u002FCD Pipeline\n\nUser request: \"Set up a test workflow for the CI\u002FCD pipeline that runs unit tests, integration tests, and end-to-end tests with appropriate dependencies.\"\n\nThe skill will:\n1. Define a test workflow using the test-orchestrator plugin, specifying the order and dependencies between the different test suites (unit, integration, end-to-end).\n2. Configure the pipeline to trigger the orchestrated test execution upon code commits.\n\n## Best Practices\n\n- **Dependency Mapping**: Clearly define dependencies between tests to ensure correct execution order.\n- **Granularity**: Break down large test suites into smaller, more manageable units for better parallelization.\n- **Change Tracking**: Integrate the test-orchestrator with version control to accurately identify affected tests.\n\n## Integration\n\nThis skill integrates with the test-orchestrator plugin and can be incorporated into CI\u002FCD pipelines. It can also be used in conjunction with other code analysis tools to further refine test selection.\n","## Overview\n\nThis skill empowers Claude to manage and execute complex test suites efficiently. It leverages the test-orchestrator plugin to handle test dependencies, parallel execution, and intelligent test selection, resulting in faster and more reliable testing processes.\n\n## How It Works\n\n1. **Workflow Definition**: Claude uses the plugin to define the test workflow, specifying dependencies between tests.\n2. **Parallelization**: The plugin identifies independent tests and executes them in parallel to reduce overall execution time.\n3. **Smart Selection**: Based on code changes, the plugin selects only the affected tests to run, minimizing unnecessary execution.\n\n## When to Use This Skill\n\nThis skill activates when you need to:\n- Optimize test execution time.\n- Manage dependencies between tests.\n- Run only relevant tests after code changes.\n\n## Examples\n\n### Example 1: Optimizing Regression Testing\n\nUser request: \"Orchestrate the regression tests for the user authentication module after the recent code changes.\"\n\nThe skill will:\n1. Use the test-orchestrator plugin to identify the tests affected by the changes in the user authentication module.\n2. Execute those tests in parallel, respecting any dependencies.\n\n### Example 2: Setting up a CI\u002FCD Pipeline\n\nUser request: \"Set up a test workflow for the CI\u002FCD pipeline that runs unit tests, integration tests, and end-to-end tests with appropriate dependencies.\"\n\nThe skill will:\n1. Define a test workflow using the test-orchestrator plugin, specifying the order and dependencies between the different test suites (unit, integration, end-to-end).\n2. Configure the pipeline to trigger the orchestrated test execution upon code commits.\n\n## Best Practices\n\n- **Dependency Mapping**: Clearly define dependencies between tests to ensure correct execution order.\n- **Granularity**: Break down large test suites into smaller, more manageable units for better parallelization.\n- **Change Tracking**: Integrate the test-orchestrator with version control to accurately identify affected tests.\n\n## Integration\n\nThis skill integrates with the test-orchestrator plugin and can be incorporated into CI\u002FCD pipelines. It can also be used in conjunction with other code analysis tools to further refine test selection.\n",{"name":5,"description":7},"master","be156301b65e301887f327d08190ed4f17ba08d2","docs\u002Fnot-mcp-related\u002Fclaude-skills\u002Ftemp\u002Fcode-plugins\u002Fplugins\u002Ftesting\u002Ftest-orchestrator\u002Fskills\u002Ftest-orchestrator",0,"https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp","https:\u002F\u002Fgithub.com\u002Fsandraschi","2026-11-12 11:03:54",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add sandraschi\u002Fdocumentation-mcp --skill orchestrating-test-workflows",{"tool":68,"command":69},"bunx","bunx skills add sandraschi\u002Fdocumentation-mcp --skill orchestrating-test-workflows",{"tool":71,"command":72},"pnpm","pnpm dlx skills add sandraschi\u002Fdocumentation-mcp --skill orchestrating-test-workflows","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fnot-mcp-related\u002Fclaude-skills\u002Ftemp\u002Fcode-plugins\u002Fplugins\u002Ftesting\u002Ftest-orchestrator\u002Fskills\u002Ftest-orchestrator\u002FSKILL.md",true,[76,82,88],{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"assets\u002FREADME.md","ASSET","资产文件",324,"https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fnot-mcp-related\u002Fclaude-skills\u002Ftemp\u002Fcode-plugins\u002Fplugins\u002Ftesting\u002Ftest-orchestrator\u002Fskills\u002Ftest-orchestrator\u002Fassets\u002FREADME.md",{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002FREADME.md","REFERENCE","参考文档",368,"https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fnot-mcp-related\u002Fclaude-skills\u002Ftemp\u002Fcode-plugins\u002Fplugins\u002Ftesting\u002Ftest-orchestrator\u002Fskills\u002Ftest-orchestrator\u002Freferences\u002FREADME.md",{"path":89,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":92,"sourceHtmlUrl":93},"scripts\u002FREADME.md","SCRIPT","脚本",384,"https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fnot-mcp-related\u002Fclaude-skills\u002Ftemp\u002Fcode-plugins\u002Fplugins\u002Ftesting\u002Ftest-orchestrator\u002Fskills\u002Ftest-orchestrator\u002Fscripts\u002FREADME.md",[95,118,145,153,172,196],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":105,"publishedAt":50},"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",[101,104],{"categoryNo":102,"categoryName":103,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[106,107,108,109,110,111,112,113,114,115,116,117],"docs research","docs","research","standards","use","packaging","ask","server","search","fastmcp","documentation","MCP",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":50},"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",[],[125,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140,141,142,143,144],"drift","wrappee drift","api","data","audit","capabilities","training","memory","features","repo audit","competitors","fleet","now","software","tool list","only","never","coverage","list","read",{"skillNo":146,"name":147,"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":148,"categories":149,"keywords":152,"publishedAt":50},"01M6PFADA3X031SK3W3T6X0N6H","modules","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fskills\u002Fwindsurf-mcp-standards\u002Fmodules\u002FSKILL.md",[150,151],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[147],{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":161,"publishedAt":50},"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",[159,160],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[162,117,109,110,163,164,165,166,167,168,34,35,169,44,170,171,116,31,42,111],"mcp standards","monitoring","sampling","scaffolding","servers","cd","error","access","mcp servers","error handling",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":180,"publishedAt":50},"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",[178,179],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[181,30,182,183,184,117,185,186,187,34,37,188,189,190,191,192,193,194,113,195],"webapp","webapp cua test","playwright","mcp server","dev","dom","assertions","click","app","tauri","repo","stack","e2e","ocr","browser",{"skillNo":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":200,"categories":201,"keywords":203,"publishedAt":50},"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",[202],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[198,191,34,37,204,205,206,207,208,209,210,113,211,185,212,213,214,184,215,117],"gates","ship it","artifact","done","say","work","publish","push","shipping","quality gates","commit","github"]