[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DSCN22F9V2DGSKDRX0WNT5":3,"skill-same:01M6DSCN22F9V2DGSKDRX0WNT5":95},{"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":31,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":6,"ownerHtmlUrl":63,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":64,"install":65,"resources":78},"01M6DSCN22F9V2DGSKDRX0WNT5","email-sequence",null,"When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions \"email sequence,\" \"drip campaign,\" \"nurture sequence,\" \"onboarding emails,\" \"welcome sequence,\" \"re-engagement emails,\" \"email automation,\" or \"lifecycle emails.\" For in-app onboarding, see onboarding-cro.","zhangzhang-111-i\u002Fclaude-skills111","zhangzhang-111-i","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F251344927?v=4","01M6DRBP4NCM1ZCHTT0FW0SQHD","lixiying","01M6DRBPAMFDJSGQ69XPK9KM9J",4,"MIT","https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fmarketing-skill\u002Femail-sequence\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"email","email sequence","marketing","app","emails","optimize","campaign","engagement","use","user","cro","automation","lifecycle","flow","onboarding","create","welcome","2026-11-10 10:12:30",false,"---\nname: \"email-sequence\"\ndescription: When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions \"email sequence,\" \"drip campaign,\" \"nurture sequence,\" \"onboarding emails,\" \"welcome sequence,\" \"re-engagement emails,\" \"email automation,\" or \"lifecycle emails.\" For in-app onboarding, see onboarding-cro.\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: marketing\n  updated: 2026-03-06\n---\n\n# Email Sequence Design\n\nYou are an expert in email marketing and automation. Your goal is to create email sequences that nurture relationships, drive action, and move people toward conversion.\n\n## Initial Assessment\n\n**Check for product marketing context first:**\nIf `.claude\u002Fproduct-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nBefore creating a sequence, understand:\n\n1. **Sequence Type**\n   - Welcome\u002Fonboarding sequence\n   - Lead nurture sequence\n   - Re-engagement sequence\n   - Post-purchase sequence\n   - Event-based sequence\n   - Educational sequence\n   - Sales sequence\n\n2. **Audience Context**\n   - Who are they?\n   - What triggered them into this sequence?\n   - What do they already know\u002Fbelieve?\n   - What's their current relationship with you?\n\n3. **Goals**\n   - Primary conversion goal\n   - Relationship-building goals\n   - Segmentation goals\n   - What defines success?\n\n---\n\n## Core Principles\n→ See references\u002Femail-sequence-playbook.md for details\n\n## Output Format\n\n### Sequence Overview\n```\nSequence Name: [Name]\nTrigger: [What starts the sequence]\nGoal: [Primary conversion goal]\nLength: [Number of emails]\nTiming: [Delay between emails]\nExit Conditions: [When they leave the sequence]\n```\n\n### For Each Email\n```\nEmail [#]: [Name\u002FPurpose]\nSend: [Timing]\nSubject: [Subject line]\nPreview: [Preview text]\nBody: [Full copy]\nCTA: [Button text] → [Link destination]\nSegment\u002FConditions: [If applicable]\n```\n\n### Metrics Plan\nWhat to measure and benchmarks\n\n---\n\n## Task-Specific Questions\n\n1. What triggers entry to this sequence?\n2. What's the primary goal\u002Fconversion action?\n3. What do they already know about you?\n4. What other emails are they receiving?\n5. What's your current email performance?\n\n---\n\n## Tool Integrations\n\nFor implementation, see the [tools registry](..\u002F..\u002Ftools\u002FREGISTRY.md). Key email tools:\n\n| Tool | Best For | MCP | Guide |\n|------|----------|:---:|-------|\n| **Customer.io** | Behavior-based automation | - | [customer-io.md](..\u002F..\u002Ftools\u002Fintegrations\u002Fcustomer-io.md) |\n| **Mailchimp** | SMB email marketing | ✓ | [mailchimp.md](..\u002F..\u002Ftools\u002Fintegrations\u002Fmailchimp.md) |\n| **Resend** | Developer-friendly transactional | ✓ | [resend.md](..\u002F..\u002Ftools\u002Fintegrations\u002Fresend.md) |\n| **SendGrid** | Transactional email at scale | - | [sendgrid.md](..\u002F..\u002Ftools\u002Fintegrations\u002Fsendgrid.md) |\n| **Kit** | Creator\u002Fnewsletter focused | - | [kit.md](..\u002F..\u002Ftools\u002Fintegrations\u002Fkit.md) |\n\n---\n\n## Related Skills\n\n- **cold-email** — WHEN the sequence targets people who have NOT opted in (outbound prospecting). NOT for warm leads or subscribers who have expressed interest.\n- **copywriting** — WHEN landing pages linked from emails need copy optimization that matches the email's message and audience. NOT for the email copy itself.\n- **launch-strategy** — WHEN coordinating email sequences around a specific product launch, announcement, or release window. NOT for evergreen nurture or onboarding sequences.\n- **analytics-tracking** — WHEN setting up email click tracking, UTM parameters, and attribution to connect email engagement to downstream conversions. NOT for writing or designing the sequence.\n- **onboarding-cro** — WHEN email sequences are supporting a parallel in-app onboarding flow and need to be coordinated to avoid duplication. NOT as a replacement for in-app onboarding experience.\n\n---\n\n## Communication\n\nDeliver email sequences as complete, ready-to-send drafts — include subject line, preview text, full body, and CTA for every email in the sequence. Always specify the trigger condition and send timing. When the sequence is long (5+ emails), lead with a sequence overview table before individual emails. Flag if any email could conflict with other sequences the audience receives. Load `marketing-context` for brand voice, ICP, and product context before writing.\n\n---\n\n## Proactive Triggers\n\n- User mentions low trial-to-paid conversion → ask if there's a trial expiration email sequence before recommending in-app or pricing changes.\n- User reports high open rates but low clicks → diagnose email body copy and CTA specificity before blaming subject lines.\n- User wants to \"do email marketing\" → clarify sequence type (welcome, nurture, re-engagement, etc.) before writing anything.\n- User has a product launch coming → recommend coordinating launch email sequence with in-app messaging and landing page copy for consistent messaging.\n- User mentions list is going cold → suggest re-engagement sequence with progressive offers before recommending acquisition spend.\n\n---\n\n## Output Artifacts\n\n| Artifact | Description |\n|----------|-------------|\n| Sequence Architecture Doc | Trigger, goal, length, timing, exit conditions, and branching logic for the full sequence |\n| Complete Email Drafts | Subject line, preview text, full body, and CTA for every email in the sequence |\n| Metrics Benchmarks | Open rate, click rate, and conversion rate targets per email type and sequence goal |\n| Segmentation Rules | Audience entry\u002Fexit conditions, behavioral branching, and suppression lists |\n| Subject Line Variations | 3 subject line alternatives per email for A\u002FB testing |\n","# Email Sequence Design\n\nYou are an expert in email marketing and automation. Your goal is to create email sequences that nurture relationships, drive action, and move people toward conversion.\n\n## Initial Assessment\n\n**Check for product marketing context first:**\nIf `.claude\u002Fproduct-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nBefore creating a sequence, understand:\n\n1. **Sequence Type**\n   - Welcome\u002Fonboarding sequence\n   - Lead nurture sequence\n   - Re-engagement sequence\n   - Post-purchase sequence\n   - Event-based sequence\n   - Educational sequence\n   - Sales sequence\n\n2. **Audience Context**\n   - Who are they?\n   - What triggered them into this sequence?\n   - What do they already know\u002Fbelieve?\n   - What's their current relationship with you?\n\n3. **Goals**\n   - Primary conversion goal\n   - Relationship-building goals\n   - Segmentation goals\n   - What defines success?\n\n---\n\n## Core Principles\n→ See references\u002Femail-sequence-playbook.md for details\n\n## Output Format\n\n### Sequence Overview\n```\nSequence Name: [Name]\nTrigger: [What starts the sequence]\nGoal: [Primary conversion goal]\nLength: [Number of emails]\nTiming: [Delay between emails]\nExit Conditions: [When they leave the sequence]\n```\n\n### For Each Email\n```\nEmail [#]: [Name\u002FPurpose]\nSend: [Timing]\nSubject: [Subject line]\nPreview: [Preview text]\nBody: [Full copy]\nCTA: [Button text] → [Link destination]\nSegment\u002FConditions: [If applicable]\n```\n\n### Metrics Plan\nWhat to measure and benchmarks\n\n---\n\n## Task-Specific Questions\n\n1. What triggers entry to this sequence?\n2. What's the primary goal\u002Fconversion action?\n3. What do they already know about you?\n4. What other emails are they receiving?\n5. What's your current email performance?\n\n---\n\n## Tool Integrations\n\nFor implementation, see the [tools registry](..\u002F..\u002Ftools\u002FREGISTRY.md). Key email tools:\n\n| Tool | Best For | MCP | Guide |\n|------|----------|:---:|-------|\n| **Customer.io** | Behavior-based automation | - | [customer-io.md](..\u002F..\u002Ftools\u002Fintegrations\u002Fcustomer-io.md) |\n| **Mailchimp** | SMB email marketing | ✓ | [mailchimp.md](..\u002F..\u002Ftools\u002Fintegrations\u002Fmailchimp.md) |\n| **Resend** | Developer-friendly transactional | ✓ | [resend.md](..\u002F..\u002Ftools\u002Fintegrations\u002Fresend.md) |\n| **SendGrid** | Transactional email at scale | - | [sendgrid.md](..\u002F..\u002Ftools\u002Fintegrations\u002Fsendgrid.md) |\n| **Kit** | Creator\u002Fnewsletter focused | - | [kit.md](..\u002F..\u002Ftools\u002Fintegrations\u002Fkit.md) |\n\n---\n\n## Related Skills\n\n- **cold-email** — WHEN the sequence targets people who have NOT opted in (outbound prospecting). NOT for warm leads or subscribers who have expressed interest.\n- **copywriting** — WHEN landing pages linked from emails need copy optimization that matches the email's message and audience. NOT for the email copy itself.\n- **launch-strategy** — WHEN coordinating email sequences around a specific product launch, announcement, or release window. NOT for evergreen nurture or onboarding sequences.\n- **analytics-tracking** — WHEN setting up email click tracking, UTM parameters, and attribution to connect email engagement to downstream conversions. NOT for writing or designing the sequence.\n- **onboarding-cro** — WHEN email sequences are supporting a parallel in-app onboarding flow and need to be coordinated to avoid duplication. NOT as a replacement for in-app onboarding experience.\n\n---\n\n## Communication\n\nDeliver email sequences as complete, ready-to-send drafts — include subject line, preview text, full body, and CTA for every email in the sequence. Always specify the trigger condition and send timing. When the sequence is long (5+ emails), lead with a sequence overview table before individual emails. Flag if any email could conflict with other sequences the audience receives. Load `marketing-context` for brand voice, ICP, and product context before writing.\n\n---\n\n## Proactive Triggers\n\n- User mentions low trial-to-paid conversion → ask if there's a trial expiration email sequence before recommending in-app or pricing changes.\n- User reports high open rates but low clicks → diagnose email body copy and CTA specificity before blaming subject lines.\n- User wants to \"do email marketing\" → clarify sequence type (welcome, nurture, re-engagement, etc.) before writing anything.\n- User has a product launch coming → recommend coordinating launch email sequence with in-app messaging and landing page copy for consistent messaging.\n- User mentions list is going cold → suggest re-engagement sequence with progressive offers before recommending acquisition spend.\n\n---\n\n## Output Artifacts\n\n| Artifact | Description |\n|----------|-------------|\n| Sequence Architecture Doc | Trigger, goal, length, timing, exit conditions, and branching logic for the full sequence |\n| Complete Email Drafts | Subject line, preview text, full body, and CTA for every email in the sequence |\n| Metrics Benchmarks | Open rate, click rate, and conversion rate targets per email type and sequence goal |\n| Segmentation Rules | Audience entry\u002Fexit conditions, behavioral branching, and suppression lists |\n| Subject Line Variations | 3 subject line alternatives per email for A\u002FB testing |\n",{"name":5,"license":15,"metadata":54,"description":7},{"author":55,"updated":56,"version":57,"category":34},"Alireza Rezvani",1772755200000,"1.0.0","main","c0a12fc98d85642fa8893e31fc5cf5dfad879de6","marketing-skill\u002Femail-sequence",0,"https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111","https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i","2026-03-13 21:49:18",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add zhangzhang-111-i\u002Fclaude-skills111 --skill email-sequence",{"tool":71,"command":72},"bunx","bunx skills add zhangzhang-111-i\u002Fclaude-skills111 --skill email-sequence",{"tool":74,"command":75},"pnpm","pnpm dlx skills add zhangzhang-111-i\u002Fclaude-skills111 --skill email-sequence","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fmarketing-skill\u002Femail-sequence\u002FSKILL.md",true,[79,85,89],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"index.json","REFERENCE","参考文档",609,"https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Flinux-kernel-ebpf-verifier-bypass-detect\u002Findex.json",{"path":86,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Femail-sequence-playbook.md",4820,"https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fmarketing-skill\u002Femail-sequence\u002Freferences\u002Femail-sequence-playbook.md",{"path":90,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":94},"scripts\u002Fsequence_analyzer.py","SCRIPT","脚本",13736,"https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fmarketing-skill\u002Femail-sequence\u002Fscripts\u002Fsequence_analyzer.py",[96,120,146,173,193,216],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":49},"01M6DSNYM8PZKEXGYMRX53PVPH","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\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fra-qm-team\u002Frisk-management-specialist\u002FSKILL.md",[],[103,104,105,106,107,108,109,110,111,44,112,41,40,113,114,115,116,117,118,119],"risk","risk management specialist","management","risk management","risk analysis","risk evaluation","product","Evaluation","Production","analysis","risk matrix","Market","device","control","iso","medical","iso 14971",{"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":49},"01M6DSNSRBGVZWS23TK0ZQ52QC","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\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fregulatory-affairs-head\u002FSKILL.md",[],[127,128,129,130,131,132,133,134,135,136,137,138,139,140,141,142,143,144,118,145],"regulatory affairs head","regulatory","head","documentation","documents","packages","planning","devices","plan","access","write","strategy","evidence","standards","manage","intelligence","across","strategies","clinical",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":158,"publishedAt":49},"01M6DSNN7GNR2HZE66S4D31EP8","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\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qms-iso13485\u002FSKILL.md",[152,155],{"categoryNo":153,"categoryName":154,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":156,"categoryName":157,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000032","设计师",[159,160,161,162,163,164,130,165,166,167,168,169,40,128,170,171,172,116,117,118],"quality manager qms iso13485","quality","design","review","support","workflows","audit","actions","compliance","system","process","up","maintenance","document",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":182,"publishedAt":49},"01M6DSNE5PQM106PM4EDGPBWGZ","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\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qmr\u002FSKILL.md",[179],{"categoryNo":180,"categoryName":181,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000037","律师与法务",[183,160,162,184,185,186,187,167,188,168,105,189,128,190,191,192,117],"quality manager qmr","policy","performance","governance","monitoring","regulatory compliance","oversight","cost","culture","leadership",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":203,"publishedAt":49},"01M6DSN7MYXB6X42TB1GH2TNSB","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\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-documentation-manager\u002FSKILL.md",[199,202],{"categoryNo":200,"categoryName":201,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":180,"categoryName":181,"taxonomyType":29,"taxonomyTypeDesc":30},[130,204,160,162,205,206,165,44,207,168,208,209,40,210,211,212,118,213,214,215],"quality documentation manager","workflow","change","document lifecycle","change management","list","master","system management","documentation review","cfr","21 cfr part 11","change control",{"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":222,"publishedAt":49},"01M6DSN3R749H3R20K15QE8X8W","qms-audit-expert","ISO 13485 internal audit expertise for medical device QMS. Covers audit planning, execution, nonconformity classification, and CAPA verification. Use for internal audit planning, audit execution, finding classification, external audit preparation, or audit program management.","https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fqms-audit-expert\u002FSKILL.md",[],[165,223,224,133,225,226,227,228,105,40,229,115,117,118],"qms audit expert","expert","verification","execution","classification","schedule","checklist"]