[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KB2AP5ZJSDSZX1GTR3XBMC":3,"skill-same:01M6KB2AP5ZJSDSZX1GTR3XBMC":68},{"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":26,"publishedAt":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":6,"updatedAt":53,"install":54,"resources":67},"01M6KB2AP5ZJSDSZX1GTR3XBMC","testrail",null,"Sync tests with TestRail. Use when user mentions \"testrail\", \"test management\", \"test cases\", \"test run\", \"sync test cases\", \"push results to testrail\", or \"import from testrail\".","afaizalam2003\u002FMaster-claude-skill","afaizalam2003","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F222019359?v=4","01M6K8F2XNT0HKBPF00JQ78SV3","Faiz Alam","01M6K8F31EBXAPER0EG8R9HTR5",3,"MIT","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering-team\u002Fplaywright-pro\u002Fskills\u002Ftestrail\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[5,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"test","sync","run","push","test run","results","management","user","use","tests","import","with","test management","test cases","2026-11-10 10:12:30",false,"---\nname: \"testrail\"\ndescription: >-\n  Sync tests with TestRail. Use when user mentions \"testrail\", \"test management\",\n  \"test cases\", \"test run\", \"sync test cases\", \"push results to testrail\",\n  or \"import from testrail\".\n---\n\n# TestRail Integration\n\nBidirectional sync between Playwright tests and TestRail test management.\n\n## Prerequisites\n\nEnvironment variables must be set:\n- `TESTRAIL_URL` — e.g., `https:\u002F\u002Fyour-instance.testrail.io`\n- `TESTRAIL_USER` — your email\n- `TESTRAIL_API_KEY` — API key from TestRail\n\nIf not set, inform the user how to configure them and stop.\n\n## Capabilities\n\n### 1. Import Test Cases → Generate Playwright Tests\n\n```\n\u002Fpw:testrail import --project \u003Cid> --suite \u003Cid>\n```\n\nSteps:\n1. Call `testrail_get_cases` MCP tool to fetch test cases\n2. For each test case:\n   - Read title, preconditions, steps, expected results\n   - Map to a Playwright test using appropriate template\n   - Include TestRail case ID as test annotation: `test.info().annotations.push({ type: 'testrail', description: 'C12345' })`\n3. Generate test files grouped by section\n4. Report: X cases imported, Y tests generated\n\n### 2. Push Test Results → TestRail\n\n```\n\u002Fpw:testrail push --run \u003Cid>\n```\n\nSteps:\n1. Run Playwright tests with JSON reporter:\n   ```bash\n   npx playwright test --reporter=json > test-results.json\n   ```\n2. Parse results: map each test to its TestRail case ID (from annotations)\n3. Call `testrail_add_result` MCP tool for each test:\n   - Pass → status_id: 1\n   - Fail → status_id: 5, include error message\n   - Skip → status_id: 2\n4. Report: X results pushed, Y passed, Z failed\n\n### 3. Create Test Run\n\n```\n\u002Fpw:testrail run --project \u003Cid> --name \"Sprint 42 Regression\"\n```\n\nSteps:\n1. Call `testrail_add_run` MCP tool\n2. Include all test case IDs found in Playwright test annotations\n3. Return run ID for result pushing\n\n### 4. Sync Status\n\n```\n\u002Fpw:testrail status --project \u003Cid>\n```\n\nSteps:\n1. Fetch test cases from TestRail\n2. Scan local Playwright tests for TestRail annotations\n3. Report coverage:\n   ```\n   TestRail cases: 150\n   Playwright tests with TestRail IDs: 120\n   Unlinked TestRail cases: 30\n   Playwright tests without TestRail IDs: 15\n   ```\n\n### 5. Update Test Cases in TestRail\n\n```\n\u002Fpw:testrail update --case \u003Cid>\n```\n\nSteps:\n1. Read the Playwright test for this case ID\n2. Extract steps and expected results from test code\n3. Call `testrail_update_case` MCP tool to update steps\n\n## MCP Tools Used\n\n| Tool | When |\n|---|---|\n| `testrail_get_projects` | List available projects |\n| `testrail_get_suites` | List suites in project |\n| `testrail_get_cases` | Read test cases |\n| `testrail_add_case` | Create new test case |\n| `testrail_update_case` | Update existing case |\n| `testrail_add_run` | Create test run |\n| `testrail_add_result` | Push individual result |\n| `testrail_get_results` | Read historical results |\n\n## Test Annotation Format\n\nAll Playwright tests linked to TestRail include:\n\n```typescript\ntest('should login successfully', async ({ page }) => {\n  test.info().annotations.push({\n    type: 'testrail',\n    description: 'C12345',\n  });\n  \u002F\u002F ... test code\n});\n```\n\nThis annotation is the bridge between Playwright and TestRail.\n\n## Output\n\n- Operation summary with counts\n- Any errors or unmatched cases\n- Link to TestRail run\u002Fresults\n","# TestRail Integration\n\nBidirectional sync between Playwright tests and TestRail test management.\n\n## Prerequisites\n\nEnvironment variables must be set:\n- `TESTRAIL_URL` — e.g., `https:\u002F\u002Fyour-instance.testrail.io`\n- `TESTRAIL_USER` — your email\n- `TESTRAIL_API_KEY` — API key from TestRail\n\nIf not set, inform the user how to configure them and stop.\n\n## Capabilities\n\n### 1. Import Test Cases → Generate Playwright Tests\n\n```\n\u002Fpw:testrail import --project \u003Cid> --suite \u003Cid>\n```\n\nSteps:\n1. Call `testrail_get_cases` MCP tool to fetch test cases\n2. For each test case:\n   - Read title, preconditions, steps, expected results\n   - Map to a Playwright test using appropriate template\n   - Include TestRail case ID as test annotation: `test.info().annotations.push({ type: 'testrail', description: 'C12345' })`\n3. Generate test files grouped by section\n4. Report: X cases imported, Y tests generated\n\n### 2. Push Test Results → TestRail\n\n```\n\u002Fpw:testrail push --run \u003Cid>\n```\n\nSteps:\n1. Run Playwright tests with JSON reporter:\n   ```bash\n   npx playwright test --reporter=json > test-results.json\n   ```\n2. Parse results: map each test to its TestRail case ID (from annotations)\n3. Call `testrail_add_result` MCP tool for each test:\n   - Pass → status_id: 1\n   - Fail → status_id: 5, include error message\n   - Skip → status_id: 2\n4. Report: X results pushed, Y passed, Z failed\n\n### 3. Create Test Run\n\n```\n\u002Fpw:testrail run --project \u003Cid> --name \"Sprint 42 Regression\"\n```\n\nSteps:\n1. Call `testrail_add_run` MCP tool\n2. Include all test case IDs found in Playwright test annotations\n3. Return run ID for result pushing\n\n### 4. Sync Status\n\n```\n\u002Fpw:testrail status --project \u003Cid>\n```\n\nSteps:\n1. Fetch test cases from TestRail\n2. Scan local Playwright tests for TestRail annotations\n3. Report coverage:\n   ```\n   TestRail cases: 150\n   Playwright tests with TestRail IDs: 120\n   Unlinked TestRail cases: 30\n   Playwright tests without TestRail IDs: 15\n   ```\n\n### 5. Update Test Cases in TestRail\n\n```\n\u002Fpw:testrail update --case \u003Cid>\n```\n\nSteps:\n1. Read the Playwright test for this case ID\n2. Extract steps and expected results from test code\n3. Call `testrail_update_case` MCP tool to update steps\n\n## MCP Tools Used\n\n| Tool | When |\n|---|---|\n| `testrail_get_projects` | List available projects |\n| `testrail_get_suites` | List suites in project |\n| `testrail_get_cases` | Read test cases |\n| `testrail_add_case` | Create new test case |\n| `testrail_update_case` | Update existing case |\n| `testrail_add_run` | Create test run |\n| `testrail_add_result` | Push individual result |\n| `testrail_get_results` | Read historical results |\n\n## Test Annotation Format\n\nAll Playwright tests linked to TestRail include:\n\n```typescript\ntest('should login successfully', async ({ page }) => {\n  test.info().annotations.push({\n    type: 'testrail',\n    description: 'C12345',\n  });\n  \u002F\u002F ... test code\n});\n```\n\nThis annotation is the bridge between Playwright and TestRail.\n\n## Output\n\n- Operation summary with counts\n- Any errors or unmatched cases\n- Link to TestRail run\u002Fresults\n",{"name":5,"description":7},"main","0b48cbb0e6d5be6ff68c0f6b28bc0c65ee21c4a1","engineering-team\u002Fplaywright-pro\u002Fskills\u002Ftestrail",2,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill","https:\u002F\u002Fgithub.com\u002Fafaizalam2003","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fmdfaizalam2003\u002F","2026-04-01 04:35:43",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add afaizalam2003\u002FMaster-claude-skill --skill testrail",{"tool":60,"command":61},"bunx","bunx skills add afaizalam2003\u002FMaster-claude-skill --skill testrail",{"tool":63,"command":64},"pnpm","pnpm dlx skills add afaizalam2003\u002FMaster-claude-skill --skill testrail","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering-team\u002Fplaywright-pro\u002Fskills\u002Ftestrail\u002FSKILL.md",true,[],[69,100,124,149,179,199],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":80,"publishedAt":41},"01M6KC4E8MYR9DBAZTAXHKYMMH","soc2-compliance","Use when the user asks to prepare for SOC 2 audits, map Trust Service Criteria, build control matrices, collect audit evidence, perform gap analysis, or assess SOC 2 Type I vs Type II readiness.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fsoc2-compliance\u002FSKILL.md",[75],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[81,82,83,84,85,86,87,88,35,89,90,91,92,93,94,95,96,97,98,99],"compliance","soc2","soc2 compliance","audit evidence","audit","collect","soc","analysis","evidence","trust","build","map","control","type","gap","readiness","gap analysis","assess","for",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":41},"01M6KC461R3GKGZ1TAYHVR1MW9","risk-management-specialist","Medical device risk management specialist implementing ISO 14971 throughout product lifecycle. Provides risk analysis, risk evaluation, risk control, and post-production information analysis. Use when user mentions risk management, ISO 14971, risk analysis, FMEA, fault tree analysis, hazard identification, risk control, risk matrix, benefit-risk analysis, residual risk, risk acceptability, or post-market risk.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Frisk-management-specialist\u002FSKILL.md",[],[107,108,33,109,110,111,112,113,88,35,114,115,116,117,118,119,120,121,122,123],"risk","risk management specialist","risk management","risk evaluation","product","Evaluation","lifecycle","risk matrix","iso","medical","iso 14971","identification","information","post-production","tree","matrix","implementing",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":41},"01M6KC3HF5ZFSSP2NZF68PEPFB","regulatory-affairs-head","Senior Regulatory Affairs Manager for HealthTech and MedTech companies. Prepares FDA 510(k), De Novo, and PMA submission packages; analyzes regulatory pathways for new medical devices; drafts responses to FDA deficiency letters and Notified Body queries; develops CE marking technical documentation under EU MDR 2017\u002F745; coordinates multi-market approval strategies across FDA, EU, Health Canada, PMDA, and NMPA; and maintains regulatory intelligence on evolving standards. Use when users need to plan or execute FDA submissions, navigate 510(k) or PMA approval processes, achieve CE marking, prepare pre-submission meeting materials, write regulatory strategy documents, respond to agency queries, or manage compliance documentation for medical device market access.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fregulatory-affairs-head\u002FSKILL.md",[],[131,132,133,134,135,136,137,138,139,35,140,141,142,143,144,145,146,147,148,99],"regulatory affairs head","regulatory","head","documents","devices","health","plan","write","strategy","standards","queries","manage","strategies","de","users","respond","medical devices","manager",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":161,"publishedAt":41},"01M6KC34Z8M1559EY1CXYBJB1A","quality-manager-qms-iso13485","ISO 13485 Quality Management System implementation and maintenance for medical device organizations. Provides QMS design, documentation control, internal auditing, CAPA management, and certification support. Use when working with medical device quality systems, preparing for ISO 13485 audits, managing regulatory compliance documentation, setting up corrective actions, or building audit preparation programs. Useful for quality management, audit preparation, regulatory compliance, medical device documentation, and corrective action workflows.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qms-iso13485\u002FSKILL.md",[155,158],{"categoryNo":156,"categoryName":157,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":159,"categoryName":160,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000032","设计师",[162,163,148,164,165,166,167,168,169,35,170,171,172,173,174,175,176,177,99,178],"quality manager qms iso13485","quality","design","workflows","validation","actions","certification","system","maintenance","document","systems","records","ISO 13485","organizations","corrective action","internal audit","preparation",{"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":186,"publishedAt":41},"01M6KC2FXHBHXYX2ZZ17Y3GDB4","quality-manager-qmr","Senior Quality Manager Responsible Person (QMR) for HealthTech and MedTech companies. Provides quality system governance, management review leadership, regulatory compliance oversight, and quality performance monitoring per ISO 13485 Clause 5.5.2.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qmr\u002FSKILL.md",[185],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},[187,163,148,188,189,190,191,192,81,193,169,194,132,195,196,197,115,174,99,198],"quality manager qmr","review","policy","performance","governance","monitoring","regulatory compliance","oversight","cost","culture","leadership","person",{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":203,"categories":204,"keywords":210,"publishedAt":41},"01M6KC1VRR5JTDBNZANHPS6VR6","quality-documentation-manager","Document control system management for medical device QMS. Covers document numbering, version control, change management, and 21 CFR Part 11 compliance. Use for document control procedures, change control workflow, document numbering, version management, electronic signature compliance, or regulatory documentation review.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-documentation-manager\u002FSKILL.md",[205,208,209],{"categoryNo":206,"categoryName":207,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},[211,212,163,148,188,213,214,85,169,215,216,217,218,219,116,220,221,222,223,99],"documentation","quality documentation manager","workflow","change","change management","list","master","system management","documentation review","cfr","21 cfr part 11","change control","retention"]