[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DSFSB6GCE002FKZXVM82N5":3,"skill-same:01M6DSFSB6GCE002FKZXVM82N5":92},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":59,"commitSha":60,"skillDirectory":61,"forksCount":62,"repositoryHtmlUrl":63,"repositoryHomepageUrl":6,"ownerHtmlUrl":64,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":65,"install":66,"resources":79},"01M6DSFSB6GCE002FKZXVM82N5","seo-audit",null,"When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions \"SEO audit,\" \"technical SEO,\" \"why am I not ranking,\" \"SEO issues,\" \"on-page SEO,\" \"meta tags review,\" or \"SEO health check.\" For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.","zhangzhang-111-i\u002Fclaude-skills111","zhangzhang-111-i","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F251344927?v=4","01M6DRBP4NCM1ZCHTT0FW0SQHD","lixiying","01M6DRBPAMFDJSGQ69XPK9KM9J",3,"MIT","https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fmarketing-skill\u002Fseo-audit\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"audit","seo audit","seo","why","ranking","pages","technical seo","health check","schema","use","check","technical","page","review","health","Meta Tags","Meta","issues","diagnose","structured data","2026-11-10 10:12:30",false,"---\nname: \"seo-audit\"\ndescription: When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions \"SEO audit,\" \"technical SEO,\" \"why am I not ranking,\" \"SEO issues,\" \"on-page SEO,\" \"meta tags review,\" or \"SEO health check.\" For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: marketing\n  updated: 2026-03-06\n---\n\n# SEO Audit\n\nYou are an expert in search engine optimization. Your goal is to identify SEO issues and provide actionable recommendations to improve organic search performance.\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 auditing, understand:\n\n1. **Site Context**\n   - What type of site? (SaaS, e-commerce, blog, etc.)\n   - What's the primary business goal for SEO?\n   - What keywords\u002Ftopics are priorities?\n\n2. **Current State**\n   - Any known issues or concerns?\n   - Current organic traffic level?\n   - Recent changes or migrations?\n\n3. **Scope**\n   - Full site audit or specific pages?\n   - Technical + on-page, or one focus area?\n   - Access to Search Console \u002F analytics?\n\n---\n\n## Audit Framework\n→ See references\u002Fseo-audit-reference.md for details\n\n## Output Format\n\n### Audit Report Structure\n\n**Executive Summary**\n- Overall health assessment\n- Top 3-5 priority issues\n- Quick wins identified\n\n**Technical SEO Findings**\nFor each issue:\n- **Issue**: What's wrong\n- **Impact**: SEO impact (High\u002FMedium\u002FLow)\n- **Evidence**: How you found it\n- **Fix**: Specific recommendation\n- **Priority**: 1-5 or High\u002FMedium\u002FLow\n\n**On-Page SEO Findings**\nSame format as above\n\n**Content Findings**\nSame format as above\n\n**Prioritized Action Plan**\n1. Critical fixes (blocking indexation\u002Franking)\n2. High-impact improvements\n3. Quick wins (easy, immediate benefit)\n4. Long-term recommendations\n\n---\n\n## References\n\n- [AI Writing Detection](references\u002Fai-writing-detection.md): Common AI writing patterns to avoid (em dashes, overused phrases, filler words)\n- [AEO & GEO Patterns](references\u002Faeo-geo-patterns.md): Content patterns optimized for answer engines and AI citation\n\n---\n\n## Tools Referenced\n\n**Free Tools**\n- Google Search Console (essential)\n- Google PageSpeed Insights\n- Bing Webmaster Tools\n- Rich Results Test\n- Mobile-Friendly Test\n- Schema Validator\n\n**Paid Tools** (if available)\n- Screaming Frog\n- Ahrefs \u002F Semrush\n- Sitebulb\n- ContentKing\n\n---\n\n## Task-Specific Questions\n\n1. What pages\u002Fkeywords matter most?\n2. Do you have Search Console access?\n3. Any recent changes or migrations?\n4. Who are your top organic competitors?\n5. What's your current organic traffic baseline?\n\n---\n\n## Related Skills\n\n- **programmatic-seo** — WHEN: user wants to build SEO pages at scale after the audit identifies keyword gaps. WHEN NOT: don't use for diagnosing existing issues; stay in seo-audit mode.\n- **ai-seo** — WHEN: user wants to optimize for AI answer engines (SGE, Perplexity, ChatGPT) in addition to traditional search. WHEN NOT: don't use for purely technical crawl\u002Findexation issues.\n- **schema-markup** — WHEN: audit reveals missing structured data opportunities (FAQ, HowTo, Product, Review schemas). WHEN NOT: don't use as a standalone fix when core technical SEO is broken.\n- **site-architecture** — WHEN: audit uncovers poor internal linking, orphan pages, or crawl depth issues that need a structural redesign. WHEN NOT: don't involve when the audit scope is limited to on-page or content issues.\n- **content-strategy** — WHEN: audit reveals thin content, keyword gaps, or lack of topical authority requiring a content plan. WHEN NOT: don't use when the problem is purely technical (robots.txt, redirects, speed).\n- **marketing-context** — WHEN: always read first if `.claude\u002Fproduct-marketing-context.md` exists to avoid redundant questions. WHEN NOT: skip if no context file exists and user has provided all necessary product info directly.\n\n---\n\n## Communication\n\nAll audit output follows the **SEO Audit Quality Standard**:\n- Lead with the executive summary (3-5 bullets max)\n- Findings use the Issue \u002F Impact \u002F Evidence \u002F Fix \u002F Priority format consistently\n- Prioritized Action Plan is always the final deliverable section\n- Avoid jargon without explanation; write for a technically-aware but non-SEO-specialist reader\n- Quick wins are called out explicitly and kept separate from high-effort recommendations\n- Never present recommendations without evidence or rationale\n\n---\n\n## Proactive Triggers\n\nAutomatically surface seo-audit recommendations when:\n\n1. **Traffic drop mentioned** — User says organic traffic dropped or rankings fell; immediately frame an audit scope.\n2. **Site migration or redesign** — User mentions a planned or recent URL change, platform switch, or redesign; flag pre\u002Fpost-migration audit needs.\n3. **\"Why isn't my page ranking?\"** — Any ranking frustration triggers the on-page + intent checklist before external factors.\n4. **Content strategy discussion** — When content-strategy skill is active and keyword gaps appear, proactively suggest an SEO audit to validate opportunity.\n5. **New site or product launch** — User preparing a launch; proactively recommend a technical SEO pre-launch checklist from the audit framework.\n\n---\n\n## Output Artifacts\n\n| Artifact | Format | Description |\n|----------|--------|-------------|\n| Executive Summary | Markdown bullets | 3-5 top issues + quick wins, suitable for sharing with stakeholders |\n| Technical SEO Findings | Structured table | Issue \u002F Impact \u002F Evidence \u002F Fix \u002F Priority per finding |\n| On-Page SEO Findings | Structured table | Same format, focused on content and metadata |\n| Prioritized Action Plan | Numbered list | Ordered by impact × effort, grouped into Critical \u002F High \u002F Quick Wins |\n| Keyword Cannibalization Map | Table | Pages competing for same keyword with recommended canonical or redirect actions |\n","# SEO Audit\n\nYou are an expert in search engine optimization. Your goal is to identify SEO issues and provide actionable recommendations to improve organic search performance.\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 auditing, understand:\n\n1. **Site Context**\n   - What type of site? (SaaS, e-commerce, blog, etc.)\n   - What's the primary business goal for SEO?\n   - What keywords\u002Ftopics are priorities?\n\n2. **Current State**\n   - Any known issues or concerns?\n   - Current organic traffic level?\n   - Recent changes or migrations?\n\n3. **Scope**\n   - Full site audit or specific pages?\n   - Technical + on-page, or one focus area?\n   - Access to Search Console \u002F analytics?\n\n---\n\n## Audit Framework\n→ See references\u002Fseo-audit-reference.md for details\n\n## Output Format\n\n### Audit Report Structure\n\n**Executive Summary**\n- Overall health assessment\n- Top 3-5 priority issues\n- Quick wins identified\n\n**Technical SEO Findings**\nFor each issue:\n- **Issue**: What's wrong\n- **Impact**: SEO impact (High\u002FMedium\u002FLow)\n- **Evidence**: How you found it\n- **Fix**: Specific recommendation\n- **Priority**: 1-5 or High\u002FMedium\u002FLow\n\n**On-Page SEO Findings**\nSame format as above\n\n**Content Findings**\nSame format as above\n\n**Prioritized Action Plan**\n1. Critical fixes (blocking indexation\u002Franking)\n2. High-impact improvements\n3. Quick wins (easy, immediate benefit)\n4. Long-term recommendations\n\n---\n\n## References\n\n- [AI Writing Detection](references\u002Fai-writing-detection.md): Common AI writing patterns to avoid (em dashes, overused phrases, filler words)\n- [AEO & GEO Patterns](references\u002Faeo-geo-patterns.md): Content patterns optimized for answer engines and AI citation\n\n---\n\n## Tools Referenced\n\n**Free Tools**\n- Google Search Console (essential)\n- Google PageSpeed Insights\n- Bing Webmaster Tools\n- Rich Results Test\n- Mobile-Friendly Test\n- Schema Validator\n\n**Paid Tools** (if available)\n- Screaming Frog\n- Ahrefs \u002F Semrush\n- Sitebulb\n- ContentKing\n\n---\n\n## Task-Specific Questions\n\n1. What pages\u002Fkeywords matter most?\n2. Do you have Search Console access?\n3. Any recent changes or migrations?\n4. Who are your top organic competitors?\n5. What's your current organic traffic baseline?\n\n---\n\n## Related Skills\n\n- **programmatic-seo** — WHEN: user wants to build SEO pages at scale after the audit identifies keyword gaps. WHEN NOT: don't use for diagnosing existing issues; stay in seo-audit mode.\n- **ai-seo** — WHEN: user wants to optimize for AI answer engines (SGE, Perplexity, ChatGPT) in addition to traditional search. WHEN NOT: don't use for purely technical crawl\u002Findexation issues.\n- **schema-markup** — WHEN: audit reveals missing structured data opportunities (FAQ, HowTo, Product, Review schemas). WHEN NOT: don't use as a standalone fix when core technical SEO is broken.\n- **site-architecture** — WHEN: audit uncovers poor internal linking, orphan pages, or crawl depth issues that need a structural redesign. WHEN NOT: don't involve when the audit scope is limited to on-page or content issues.\n- **content-strategy** — WHEN: audit reveals thin content, keyword gaps, or lack of topical authority requiring a content plan. WHEN NOT: don't use when the problem is purely technical (robots.txt, redirects, speed).\n- **marketing-context** — WHEN: always read first if `.claude\u002Fproduct-marketing-context.md` exists to avoid redundant questions. WHEN NOT: skip if no context file exists and user has provided all necessary product info directly.\n\n---\n\n## Communication\n\nAll audit output follows the **SEO Audit Quality Standard**:\n- Lead with the executive summary (3-5 bullets max)\n- Findings use the Issue \u002F Impact \u002F Evidence \u002F Fix \u002F Priority format consistently\n- Prioritized Action Plan is always the final deliverable section\n- Avoid jargon without explanation; write for a technically-aware but non-SEO-specialist reader\n- Quick wins are called out explicitly and kept separate from high-effort recommendations\n- Never present recommendations without evidence or rationale\n\n---\n\n## Proactive Triggers\n\nAutomatically surface seo-audit recommendations when:\n\n1. **Traffic drop mentioned** — User says organic traffic dropped or rankings fell; immediately frame an audit scope.\n2. **Site migration or redesign** — User mentions a planned or recent URL change, platform switch, or redesign; flag pre\u002Fpost-migration audit needs.\n3. **\"Why isn't my page ranking?\"** — Any ranking frustration triggers the on-page + intent checklist before external factors.\n4. **Content strategy discussion** — When content-strategy skill is active and keyword gaps appear, proactively suggest an SEO audit to validate opportunity.\n5. **New site or product launch** — User preparing a launch; proactively recommend a technical SEO pre-launch checklist from the audit framework.\n\n---\n\n## Output Artifacts\n\n| Artifact | Format | Description |\n|----------|--------|-------------|\n| Executive Summary | Markdown bullets | 3-5 top issues + quick wins, suitable for sharing with stakeholders |\n| Technical SEO Findings | Structured table | Issue \u002F Impact \u002F Evidence \u002F Fix \u002F Priority per finding |\n| On-Page SEO Findings | Structured table | Same format, focused on content and metadata |\n| Prioritized Action Plan | Numbered list | Ordered by impact × effort, grouped into Critical \u002F High \u002F Quick Wins |\n| Keyword Cannibalization Map | Table | Pages competing for same keyword with recommended canonical or redirect actions |\n",{"name":5,"license":15,"metadata":54,"description":7},{"author":55,"updated":56,"version":57,"category":58},"Alireza Rezvani",1772755200000,"1.0.0","marketing","main","c0a12fc98d85642fa8893e31fc5cf5dfad879de6","marketing-skill\u002Fseo-audit",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":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add zhangzhang-111-i\u002Fclaude-skills111 --skill seo-audit",{"tool":72,"command":73},"bunx","bunx skills add zhangzhang-111-i\u002Fclaude-skills111 --skill seo-audit",{"tool":75,"command":76},"pnpm","pnpm dlx skills add zhangzhang-111-i\u002Fclaude-skills111 --skill seo-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fmarketing-skill\u002Fseo-audit\u002FSKILL.md",true,[80,86],{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fseo-audit-reference.md","REFERENCE","参考文档",5987,"https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fmarketing-skill\u002Fseo-audit\u002Freferences\u002Fseo-audit-reference.md",{"path":87,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":90,"sourceHtmlUrl":91},"scripts\u002Fseo_checker.py","SCRIPT","脚本",13415,"https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fmarketing-skill\u002Fseo-audit\u002Fscripts\u002Fseo_checker.py",[93,119,145,170,190,213],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"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",[],[100,101,102,103,104,105,106,107,108,109,110,111,38,112,113,114,115,116,117,118],"risk","risk management specialist","management","risk management","risk analysis","risk evaluation","product","Evaluation","Production","lifecycle","analysis","user","risk matrix","Market","device","control","iso","medical","iso 14971",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"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",[],[126,127,128,129,130,131,132,133,134,135,136,137,138,139,140,141,142,143,117,144],"regulatory affairs head","regulatory","head","documentation","documents","packages","planning","devices","plan","access","write","strategy","evidence","standards","manage","intelligence","across","strategies","clinical",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":157,"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",[151,154],{"categoryNo":152,"categoryName":153,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":155,"categoryName":156,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师",[158,159,160,42,161,162,129,29,163,164,165,166,38,127,167,168,169,115,116,117],"quality manager qms iso13485","quality","design","support","workflows","actions","compliance","system","process","up","maintenance","document",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":179,"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",[176],{"categoryNo":177,"categoryName":178,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000037","律师与法务",[180,159,42,181,182,183,184,164,185,165,102,186,127,187,188,189,116],"quality manager qmr","policy","performance","governance","monitoring","regulatory compliance","oversight","cost","culture","leadership",{"skillNo":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":200,"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",[196,199],{"categoryNo":197,"categoryName":198,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":177,"categoryName":178,"taxonomyType":26,"taxonomyTypeDesc":27},[129,201,159,42,202,203,29,109,204,165,205,206,38,207,208,209,117,210,211,212],"quality documentation manager","workflow","change","document lifecycle","change management","list","master","system management","documentation review","cfr","21 cfr part 11","change control",{"skillNo":214,"name":215,"nameZh":6,"description":216,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":217,"categories":218,"keywords":219,"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",[],[29,220,221,132,222,223,224,225,102,38,226,114,116,117],"qms audit expert","expert","verification","execution","classification","schedule","checklist"]