[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KBTSZNBK2819AWQJ36RGAF":3,"skill-same:01M6KBTSZNBK2819AWQJ36RGAF":106},{"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":34,"publishedAt":55,"linkOnly":56,"markdownContent":57,"markdownBody":58,"frontMatter":59,"refName":60,"commitSha":61,"skillDirectory":62,"forksCount":63,"repositoryHtmlUrl":64,"repositoryHomepageUrl":6,"ownerHtmlUrl":65,"ownerBlogUrl":66,"ownerDescription":6,"updatedAt":67,"install":68,"resources":81},"01M6KBTSZNBK2819AWQJ36RGAF","competitive-teardown",null,"Analyzes competitor products and companies by synthesizing data from pricing pages, app store reviews, job postings, SEO signals, and social media into structured competitive intelligence. Produces feature comparison matrices scored across 12 dimensions, SWOT analyses, positioning maps, UX audits, pricing model breakdowns, action item roadmaps, and stakeholder presentation templates. Use when conducting competitor analysis, comparing products against competitors, researching the competitive landscape, building battle cards for sales, preparing for a product strategy or roadmap session, responding to a competitor's new feature or pricing change, or performing a quarterly competitive review.","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\u002Fproduct-team\u002Fcompetitive-teardown\u002FSKILL.md",[18,23,26,31],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000003","演示文稿","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",{"categoryNo":32,"categoryName":33,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000035","市场营销",[35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54],"competitive","competitive teardown","teardown","positioning","app store","pricing model","reviews","app","signals","across","landscape","review","dimensions","social","maps","roadmap","model","Media","analysis","change","2026-11-10 10:12:30",false,"---\nname: \"competitive-teardown\"\ndescription: \"Analyzes competitor products and companies by synthesizing data from pricing pages, app store reviews, job postings, SEO signals, and social media into structured competitive intelligence. Produces feature comparison matrices scored across 12 dimensions, SWOT analyses, positioning maps, UX audits, pricing model breakdowns, action item roadmaps, and stakeholder presentation templates. Use when conducting competitor analysis, comparing products against competitors, researching the competitive landscape, building battle cards for sales, preparing for a product strategy or roadmap session, responding to a competitor's new feature or pricing change, or performing a quarterly competitive review.\"\n---\n\n# Competitive Teardown\n\n**Tier:** POWERFUL  \n**Category:** Product Team  \n**Domain:** Competitive Intelligence, Product Strategy, Market Analysis\n\n---\n\n## When to Use\n\n- Before a product strategy or roadmap session\n- When a competitor launches a major feature or pricing change\n- Quarterly competitive review\n- Before a sales pitch where you need battle card data\n- When entering a new market segment\n\n---\n\n## Teardown Workflow\n\nFollow these steps in sequence to produce a complete teardown:\n\n1. **Define competitors** — List 2–4 competitors to analyze. Confirm which is the primary focus.\n2. **Collect data** — Use `references\u002Fdata-collection-guide.md` to gather raw signals from at least 3 sources per competitor (website, reviews, job postings, SEO, social).  \n   _Validation checkpoint: Before proceeding, confirm you have pricing data, at least 20 reviews, and job posting counts for each competitor._\n3. **Score using rubric** — Apply the 12-dimension rubric below to produce a numeric scorecard for each competitor and your own product.  \n   _Validation checkpoint: Every dimension should have a score and at least one supporting evidence note._\n4. **Generate outputs** — Populate the templates in `references\u002Fanalysis-templates.md` (Feature Matrix, Pricing Analysis, SWOT, Positioning Map, UX Audit).\n5. **Build action plan** — Translate findings into the Action Items template (quick wins \u002F medium-term \u002F strategic).\n6. **Package for stakeholders** — Assemble the Stakeholder Presentation using outputs from steps 3–5.\n\n---\n\n## Data Collection Guide\n\n> Full executable scripts for each source are in `references\u002Fdata-collection-guide.md`. Summaries of what to capture are below.\n\n### 1. Website Analysis\n\nKey things to capture:\n- Pricing tiers and price points\n- Feature lists per tier\n- Primary CTA and messaging\n- Case studies \u002F customer logos (signals ICP)\n- Integration logos\n- Trust signals (certifications, compliance badges)\n\n### 2. App Store Reviews\n\nReview sentiment categories:\n- **Praise** → what users love (defend \u002F strengthen these)\n- **Feature requests** → unmet needs (opportunity gaps)\n- **Bugs** → quality signals\n- **UX complaints** → friction points you can beat them on\n\n**Sample App Store query (iTunes Search API):**\n```\nGET https:\u002F\u002Fitunes.apple.com\u002Fsearch?term=\u003Ccompetitor_name>&entity=software&limit=1\n# Extract trackId, then:\nGET https:\u002F\u002Fitunes.apple.com\u002Frss\u002Fcustomerreviews\u002Fid=\u003CtrackId>\u002FsortBy=mostRecent\u002Fjson?l=en&limit=50\n```\nParse `entry[].content.label` for review text and `entry[].im:rating.label` for star rating.\n\n### 3. Job Postings (Team Size & Tech Stack Signals)\n\nSignals from job postings:\n- **Engineering volume** → scaling vs. consolidating\n- **Specific tech mentions** → stack (React\u002FVue, Postgres\u002FMongo, AWS\u002FGCP)\n- **Sales\u002FCS ratio** → product-led vs. sales-led motion\n- **Data\u002FML roles** → upcoming AI features\n- **Compliance roles** → regulatory expansion\n\n### 4. SEO Analysis\n\nSEO signals to capture:\n- Top 20 organic keywords (intent: informational \u002F navigational \u002F commercial)\n- Domain Authority \u002F backlink count\n- Blog publishing cadence and topics\n- Which pages rank (product pages vs. blog vs. docs)\n\n### 5. Social Media Sentiment\n\nCapture recent mentions via Twitter\u002FX API v2, Reddit, or LinkedIn. Look for recurring praise, complaints, and feature requests. See `references\u002Fdata-collection-guide.md` for API query examples.\n\n---\n\n## Scoring Rubric (12 Dimensions, 1-5)\n\n| # | Dimension | 1 (Weak) | 3 (Average) | 5 (Best-in-class) |\n|---|-----------|----------|-------------|-------------------|\n| 1 | **Features** | Core only, many gaps | Solid coverage | Comprehensive + unique |\n| 2 | **Pricing** | Confusing \u002F overpriced | Market-rate, clear | Transparent, flexible, fair |\n| 3 | **UX** | Confusing, high friction | Functional | Delightful, minimal friction |\n| 4 | **Performance** | Slow, unreliable | Acceptable | Fast, high uptime |\n| 5 | **Docs** | Sparse, outdated | Decent coverage | Comprehensive, searchable |\n| 6 | **Support** | Email only, slow | Chat + email | 24\u002F7, great response |\n| 7 | **Integrations** | 0-5 integrations | 6-25 | 26+ or deep ecosystem |\n| 8 | **Security** | No mentions | SOC2 claimed | SOC2 Type II, ISO 27001 |\n| 9 | **Scalability** | No enterprise tier | Mid-market ready | Enterprise-grade |\n| 10 | **Brand** | Generic, unmemorable | Decent positioning | Strong, differentiated |\n| 11 | **Community** | None | Forum \u002F Slack | Active, vibrant community |\n| 12 | **Innovation** | No recent releases | Quarterly | Frequent, meaningful |\n\n**Example completed row** (Competitor: Acme Corp, Dimension 3 – UX):\n\n| Dimension | Acme Corp Score | Evidence |\n|-----------|----------------|---------|\n| UX | 2 | App Store reviews cite \"confusing navigation\" (38 mentions); onboarding requires 7 steps before TTFV; no onboarding wizard; CC required at signup. |\n\nApply this pattern to all 12 dimensions for each competitor.\n\n---\n\n## Templates\n\n> Full template markdown is in `references\u002Fanalysis-templates.md`. Abbreviated reference below.\n\n### Feature Comparison Matrix\n\nRows: core features, pricing tiers, platform capabilities (web, iOS, Android, API).  \nColumns: your product + up to 3 competitors.  \nScore each cell 1–5. Sum to get total out of 60.  \n**Score legend:** 5=Best-in-class, 4=Strong, 3=Average, 2=Below average, 1=Weak\u002FMissing\n\n### Pricing Analysis\n\nCapture per competitor: model type (per-seat \u002F usage-based \u002F flat rate \u002F freemium), entry\u002Fmid\u002Fenterprise price points, free trial length.  \nSummarize: price leader, value leader, premium positioning, your position, and 2–3 pricing opportunity bullets.\n\n### SWOT Analysis\n\nFor each competitor: 3–5 bullets per quadrant (Strengths, Weaknesses, Opportunities for us, Threats to us). Anchor every bullet to a data signal (review quote, job posting count, pricing page, etc.).\n\n### Positioning Map\n\n2x2 axes (e.g., Simple ↔ Complex \u002F Low Value ↔ High Value). Place each competitor and your product. Bubble size = market share or funding. See `references\u002Fanalysis-templates.md` for ASCII and editable versions.\n\n### UX Audit Checklist\n\nOnboarding: TTFV (minutes), steps to activation, CC-required, onboarding wizard quality.  \nKey workflows: steps, friction points, comparative score (yours vs. theirs).  \nMobile: iOS\u002FAndroid ratings, feature parity, top complaint and praise.  \nNavigation: global search, keyboard shortcuts, in-app help.\n\n### Action Items\n\n| Horizon | Effort | Examples |\n|---------|--------|---------|\n| Quick wins (0–4 wks) | Low | Add review badges, publish comparison landing page |\n| Medium-term (1–3 mo) | Moderate | Launch free tier, improve onboarding TTFV, add top-requested integration |\n| Strategic (3–12 mo) | High | Enter new market, build API v2, achieve SOC2 Type II |\n\n### Stakeholder Presentation (7 slides)\n\n1. **Executive Summary** — Threat level (LOW\u002FMEDIUM\u002FHIGH\u002FCRITICAL), top strength, top opportunity, recommended action\n2. **Market Position** — 2x2 positioning map\n3. **Feature Scorecard** — 12-dimension radar or table, total scores\n4. **Pricing Analysis** — Comparison table + key insight\n5. **UX Highlights** — What they do better (3 bullets) vs. where we win (3 bullets)\n6. **Voice of Customer** — Top 3 review complaints (quoted or paraphrased)\n7. **Our Action Plan** — Quick wins, medium-term, strategic priorities; Appendix with raw data\n\n## Related Skills\n\n- **Product Strategist** (`product-team\u002Fproduct-strategist\u002F`) — Competitive insights feed OKR and strategy planning\n- **Landing Page Generator** (`product-team\u002Flanding-page-generator\u002F`) — Competitive positioning informs landing page messaging\n","# Competitive Teardown\n\n**Tier:** POWERFUL  \n**Category:** Product Team  \n**Domain:** Competitive Intelligence, Product Strategy, Market Analysis\n\n---\n\n## When to Use\n\n- Before a product strategy or roadmap session\n- When a competitor launches a major feature or pricing change\n- Quarterly competitive review\n- Before a sales pitch where you need battle card data\n- When entering a new market segment\n\n---\n\n## Teardown Workflow\n\nFollow these steps in sequence to produce a complete teardown:\n\n1. **Define competitors** — List 2–4 competitors to analyze. Confirm which is the primary focus.\n2. **Collect data** — Use `references\u002Fdata-collection-guide.md` to gather raw signals from at least 3 sources per competitor (website, reviews, job postings, SEO, social).  \n   _Validation checkpoint: Before proceeding, confirm you have pricing data, at least 20 reviews, and job posting counts for each competitor._\n3. **Score using rubric** — Apply the 12-dimension rubric below to produce a numeric scorecard for each competitor and your own product.  \n   _Validation checkpoint: Every dimension should have a score and at least one supporting evidence note._\n4. **Generate outputs** — Populate the templates in `references\u002Fanalysis-templates.md` (Feature Matrix, Pricing Analysis, SWOT, Positioning Map, UX Audit).\n5. **Build action plan** — Translate findings into the Action Items template (quick wins \u002F medium-term \u002F strategic).\n6. **Package for stakeholders** — Assemble the Stakeholder Presentation using outputs from steps 3–5.\n\n---\n\n## Data Collection Guide\n\n> Full executable scripts for each source are in `references\u002Fdata-collection-guide.md`. Summaries of what to capture are below.\n\n### 1. Website Analysis\n\nKey things to capture:\n- Pricing tiers and price points\n- Feature lists per tier\n- Primary CTA and messaging\n- Case studies \u002F customer logos (signals ICP)\n- Integration logos\n- Trust signals (certifications, compliance badges)\n\n### 2. App Store Reviews\n\nReview sentiment categories:\n- **Praise** → what users love (defend \u002F strengthen these)\n- **Feature requests** → unmet needs (opportunity gaps)\n- **Bugs** → quality signals\n- **UX complaints** → friction points you can beat them on\n\n**Sample App Store query (iTunes Search API):**\n```\nGET https:\u002F\u002Fitunes.apple.com\u002Fsearch?term=\u003Ccompetitor_name>&entity=software&limit=1\n# Extract trackId, then:\nGET https:\u002F\u002Fitunes.apple.com\u002Frss\u002Fcustomerreviews\u002Fid=\u003CtrackId>\u002FsortBy=mostRecent\u002Fjson?l=en&limit=50\n```\nParse `entry[].content.label` for review text and `entry[].im:rating.label` for star rating.\n\n### 3. Job Postings (Team Size & Tech Stack Signals)\n\nSignals from job postings:\n- **Engineering volume** → scaling vs. consolidating\n- **Specific tech mentions** → stack (React\u002FVue, Postgres\u002FMongo, AWS\u002FGCP)\n- **Sales\u002FCS ratio** → product-led vs. sales-led motion\n- **Data\u002FML roles** → upcoming AI features\n- **Compliance roles** → regulatory expansion\n\n### 4. SEO Analysis\n\nSEO signals to capture:\n- Top 20 organic keywords (intent: informational \u002F navigational \u002F commercial)\n- Domain Authority \u002F backlink count\n- Blog publishing cadence and topics\n- Which pages rank (product pages vs. blog vs. docs)\n\n### 5. Social Media Sentiment\n\nCapture recent mentions via Twitter\u002FX API v2, Reddit, or LinkedIn. Look for recurring praise, complaints, and feature requests. See `references\u002Fdata-collection-guide.md` for API query examples.\n\n---\n\n## Scoring Rubric (12 Dimensions, 1-5)\n\n| # | Dimension | 1 (Weak) | 3 (Average) | 5 (Best-in-class) |\n|---|-----------|----------|-------------|-------------------|\n| 1 | **Features** | Core only, many gaps | Solid coverage | Comprehensive + unique |\n| 2 | **Pricing** | Confusing \u002F overpriced | Market-rate, clear | Transparent, flexible, fair |\n| 3 | **UX** | Confusing, high friction | Functional | Delightful, minimal friction |\n| 4 | **Performance** | Slow, unreliable | Acceptable | Fast, high uptime |\n| 5 | **Docs** | Sparse, outdated | Decent coverage | Comprehensive, searchable |\n| 6 | **Support** | Email only, slow | Chat + email | 24\u002F7, great response |\n| 7 | **Integrations** | 0-5 integrations | 6-25 | 26+ or deep ecosystem |\n| 8 | **Security** | No mentions | SOC2 claimed | SOC2 Type II, ISO 27001 |\n| 9 | **Scalability** | No enterprise tier | Mid-market ready | Enterprise-grade |\n| 10 | **Brand** | Generic, unmemorable | Decent positioning | Strong, differentiated |\n| 11 | **Community** | None | Forum \u002F Slack | Active, vibrant community |\n| 12 | **Innovation** | No recent releases | Quarterly | Frequent, meaningful |\n\n**Example completed row** (Competitor: Acme Corp, Dimension 3 – UX):\n\n| Dimension | Acme Corp Score | Evidence |\n|-----------|----------------|---------|\n| UX | 2 | App Store reviews cite \"confusing navigation\" (38 mentions); onboarding requires 7 steps before TTFV; no onboarding wizard; CC required at signup. |\n\nApply this pattern to all 12 dimensions for each competitor.\n\n---\n\n## Templates\n\n> Full template markdown is in `references\u002Fanalysis-templates.md`. Abbreviated reference below.\n\n### Feature Comparison Matrix\n\nRows: core features, pricing tiers, platform capabilities (web, iOS, Android, API).  \nColumns: your product + up to 3 competitors.  \nScore each cell 1–5. Sum to get total out of 60.  \n**Score legend:** 5=Best-in-class, 4=Strong, 3=Average, 2=Below average, 1=Weak\u002FMissing\n\n### Pricing Analysis\n\nCapture per competitor: model type (per-seat \u002F usage-based \u002F flat rate \u002F freemium), entry\u002Fmid\u002Fenterprise price points, free trial length.  \nSummarize: price leader, value leader, premium positioning, your position, and 2–3 pricing opportunity bullets.\n\n### SWOT Analysis\n\nFor each competitor: 3–5 bullets per quadrant (Strengths, Weaknesses, Opportunities for us, Threats to us). Anchor every bullet to a data signal (review quote, job posting count, pricing page, etc.).\n\n### Positioning Map\n\n2x2 axes (e.g., Simple ↔ Complex \u002F Low Value ↔ High Value). Place each competitor and your product. Bubble size = market share or funding. See `references\u002Fanalysis-templates.md` for ASCII and editable versions.\n\n### UX Audit Checklist\n\nOnboarding: TTFV (minutes), steps to activation, CC-required, onboarding wizard quality.  \nKey workflows: steps, friction points, comparative score (yours vs. theirs).  \nMobile: iOS\u002FAndroid ratings, feature parity, top complaint and praise.  \nNavigation: global search, keyboard shortcuts, in-app help.\n\n### Action Items\n\n| Horizon | Effort | Examples |\n|---------|--------|---------|\n| Quick wins (0–4 wks) | Low | Add review badges, publish comparison landing page |\n| Medium-term (1–3 mo) | Moderate | Launch free tier, improve onboarding TTFV, add top-requested integration |\n| Strategic (3–12 mo) | High | Enter new market, build API v2, achieve SOC2 Type II |\n\n### Stakeholder Presentation (7 slides)\n\n1. **Executive Summary** — Threat level (LOW\u002FMEDIUM\u002FHIGH\u002FCRITICAL), top strength, top opportunity, recommended action\n2. **Market Position** — 2x2 positioning map\n3. **Feature Scorecard** — 12-dimension radar or table, total scores\n4. **Pricing Analysis** — Comparison table + key insight\n5. **UX Highlights** — What they do better (3 bullets) vs. where we win (3 bullets)\n6. **Voice of Customer** — Top 3 review complaints (quoted or paraphrased)\n7. **Our Action Plan** — Quick wins, medium-term, strategic priorities; Appendix with raw data\n\n## Related Skills\n\n- **Product Strategist** (`product-team\u002Fproduct-strategist\u002F`) — Competitive insights feed OKR and strategy planning\n- **Landing Page Generator** (`product-team\u002Flanding-page-generator\u002F`) — Competitive positioning informs landing page messaging\n",{"name":5,"description":7},"main","0b48cbb0e6d5be6ff68c0f6b28bc0c65ee21c4a1","product-team\u002Fcompetitive-teardown",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":69,"prompt":79,"zipAvailable":80},[70,73,76],{"tool":71,"command":72},"npx","npx skills add afaizalam2003\u002FMaster-claude-skill --skill competitive-teardown",{"tool":74,"command":75},"bunx","bunx skills add afaizalam2003\u002FMaster-claude-skill --skill competitive-teardown",{"tool":77,"command":78},"pnpm","pnpm dlx skills add afaizalam2003\u002FMaster-claude-skill --skill competitive-teardown","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fproduct-team\u002Fcompetitive-teardown\u002FSKILL.md",true,[82,88,92,96,100],{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fanalysis-templates.md","REFERENCE","参考文档",6674,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fproduct-team\u002Fcompetitive-teardown\u002Freferences\u002Fanalysis-templates.md",{"path":89,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fcompetitive-analysis-frameworks.md",3286,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fproduct-team\u002Fcompetitive-teardown\u002Freferences\u002Fcompetitive-analysis-frameworks.md",{"path":93,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fdata-collection-guide.md",4977,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fproduct-team\u002Fcompetitive-teardown\u002Freferences\u002Fdata-collection-guide.md",{"path":97,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Fscoring-rubric.md",5076,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fproduct-team\u002Fcompetitive-teardown\u002Freferences\u002Fscoring-rubric.md",{"path":101,"resourceType":102,"resourceTypeDesc":103,"sizeBytes":104,"sourceHtmlUrl":105},"scripts\u002Fcompetitive_matrix_builder.py","SCRIPT","脚本",10783,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fproduct-team\u002Fcompetitive-teardown\u002Fscripts\u002Fcompetitive_matrix_builder.py",[107,136,161,186,216,235],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":116,"publishedAt":55},"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",[113],{"categoryNo":114,"categoryName":115,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000037","律师与法务",[117,118,119,120,121,122,123,53,124,125,126,127,128,129,130,131,132,133,134,135],"compliance","soc2","soc2 compliance","audit evidence","audit","collect","soc","use","evidence","trust","build","map","control","type","gap","readiness","gap analysis","assess","for",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":55},"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",[],[143,144,145,146,147,148,149,150,53,124,151,152,153,154,155,156,157,158,159,160],"risk","risk management specialist","management","risk management","risk evaluation","product","Evaluation","lifecycle","risk matrix","iso","medical","iso 14971","identification","information","post-production","tree","matrix","implementing",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":167,"publishedAt":55},"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",[],[168,169,170,171,172,173,174,175,176,124,177,178,179,180,181,182,183,184,185,135],"regulatory affairs head","regulatory","head","documents","devices","health","plan","write","strategy","standards","queries","manage","strategies","de","users","respond","medical devices","manager",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":198,"publishedAt":55},"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",[192,195],{"categoryNo":193,"categoryName":194,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":196,"categoryName":197,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000032","设计师",[199,200,185,201,202,203,204,205,206,124,207,208,209,210,211,212,213,214,135,215],"quality manager qms iso13485","quality","design","workflows","validation","actions","certification","system","maintenance","document","systems","records","ISO 13485","organizations","corrective action","internal audit","preparation",{"skillNo":217,"name":218,"nameZh":6,"description":219,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":220,"categories":221,"keywords":223,"publishedAt":55},"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",[222],{"categoryNo":114,"categoryName":115,"taxonomyType":29,"taxonomyTypeDesc":30},[224,200,185,46,225,226,227,228,117,229,206,230,169,231,232,233,152,211,135,234],"quality manager qmr","policy","performance","governance","monitoring","regulatory compliance","oversight","cost","culture","leadership","person",{"skillNo":236,"name":237,"nameZh":6,"description":238,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":239,"categories":240,"keywords":248,"publishedAt":55},"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",[241,244,247],{"categoryNo":242,"categoryName":243,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":245,"categoryName":246,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":114,"categoryName":115,"taxonomyType":29,"taxonomyTypeDesc":30},[249,250,200,185,46,251,54,121,206,252,253,254,255,256,153,257,258,259,260,135],"documentation","quality documentation manager","workflow","change management","list","master","system management","documentation review","cfr","21 cfr part 11","change control","retention"]