iso-13485-certification
Comprehensive toolkit for preparing ISO 13485 certification documentation for medical device Quality Management Systems. Use when users need help with ISO 13485 QMS documentation, including (1) conducting gap analysis of existing documentation, (2) creating Quality Manuals, (3) developing required procedures and work instructions, (4) preparing Medical Device Files, (5) understanding ISO 13485 requirements, or (6) identifying missing documentation for medical device certification. Also use when users mention medical device regulations, QMS certification, FDA QMSR, EU MDR, or need help with quality system documentation.
Install
mkdir -p .claude/skills/iso-13485-certification && curl -L -o skill.zip "https://mcp.directory/api/skills/download/5864" && unzip -o skill.zip -d .claude/skills/iso-13485-certification && rm skill.zipInstalls to .claude/skills/iso-13485-certification
About this skill
ISO 13485 Certification Documentation Assistant
Overview
This skill helps medical device manufacturers prepare comprehensive documentation for ISO 13485:2016 certification. It provides tools, templates, references, and guidance to create, review, and gap-analyze all required Quality Management System (QMS) documentation.
What this skill provides:
- Gap analysis of existing documentation
- Templates for all mandatory documents
- Comprehensive requirements guidance
- Step-by-step documentation creation
- Identification of missing documentation
- Compliance checklists
When to use this skill:
- Starting ISO 13485 certification process
- Conducting gap analysis against ISO 13485
- Creating or updating QMS documentation
- Preparing for certification audit
- Transitioning from FDA QSR to QMSR
- Harmonizing with EU MDR requirements
Core Workflow
1. Assess Current State (Gap Analysis)
When to start here: User has existing documentation and needs to identify gaps
Process:
-
Collect existing documentation:
- Ask user to provide directory of current QMS documents
- Documents can be in any format (.txt, .md, .doc, .docx, .pdf)
- Include any procedures, manuals, work instructions, forms
-
Run gap analysis script:
python scripts/gap_analyzer.py --docs-dir <path_to_docs> --output gap-report.json -
Review results:
- Identify which of the 31 required procedures are present
- Identify missing key documents (Quality Manual, MDF, etc.)
- Calculate compliance percentage
- Prioritize missing documentation
-
Present findings to user:
- Summarize what exists
- Clearly list what's missing
- Provide prioritized action plan
- Estimate effort required
Output: Comprehensive gap analysis report with prioritized action items
2. Understand Requirements (Reference Consultation)
When to use: User needs to understand specific ISO 13485 requirements
Available references:
references/iso-13485-requirements.md- Complete clause-by-clause breakdownreferences/mandatory-documents.md- All 31 required procedures explainedreferences/gap-analysis-checklist.md- Detailed compliance checklistreferences/quality-manual-guide.md- How to create Quality Manual
How to use:
-
For specific clause questions:
- Read relevant section from
iso-13485-requirements.md - Explain requirements in plain language
- Provide practical examples
- Read relevant section from
-
For document requirements:
- Consult
mandatory-documents.md - Explain what must be documented
- Clarify when documents are applicable vs. excludable
- Consult
-
For implementation guidance:
- Use
quality-manual-guide.mdfor policy-level documents - Provide step-by-step creation process
- Show examples of good vs. poor implementation
- Use
Key reference sections to know:
- Clause 4: QMS requirements, documentation, risk management, software validation
- Clause 5: Management responsibility, quality policy, objectives, management review
- Clause 6: Resources, competence, training, infrastructure
- Clause 7: Product realization, design, purchasing, production, traceability
- Clause 8: Measurement, audits, CAPA, complaints, data analysis
3. Create Documentation (Template-Based Generation)
When to use: User needs to create specific QMS documents
Available templates:
- Quality Manual:
assets/templates/quality-manual-template.md - CAPA Procedure:
assets/templates/procedures/CAPA-procedure-template.md - Document Control:
assets/templates/procedures/document-control-procedure-template.md
Process for document creation:
-
Identify what needs to be created:
- Based on gap analysis or user request
- Prioritize critical documents first (Quality Manual, CAPA, Complaints, Audits)
-
Select appropriate template:
- Use Quality Manual template for QM
- Use procedure templates as examples for SOPs
- Adapt structure to organization's needs
-
Customize template with user-specific information:
- Replace all placeholder text: [COMPANY NAME], [DATE], [NAME], etc.
- Tailor scope to user's actual operations
- Add or remove sections based on applicability
- Ensure consistency with organization's processes
-
Key customization areas:
- Company information and addresses
- Product types and classifications
- Applicable regulatory requirements
- Organization structure and responsibilities
- Actual processes and procedures
- Document numbering schemes
- Exclusions and justifications
-
Validate completeness:
- All required sections present
- All placeholders replaced
- Cross-references correct
- Approval sections complete
Document creation priority order:
Phase 1 - Foundation (Critical):
- Quality Manual
- Quality Policy and Objectives
- Document Control procedure
- Record Control procedure
Phase 2 - Core Processes (High Priority): 5. Corrective and Preventive Action (CAPA) 6. Complaint Handling 7. Internal Audit 8. Management Review 9. Risk Management
Phase 3 - Product Realization (High Priority): 10. Design and Development (if applicable) 11. Purchasing 12. Production and Service Provision 13. Control of Nonconforming Product
Phase 4 - Supporting Processes (Medium Priority): 14. Training and Competence 15. Calibration/Control of M&M Equipment 16. Process Validation 17. Product Identification and Traceability
Phase 5 - Additional Requirements (Medium Priority): 18. Feedback and Post-Market Surveillance 19. Regulatory Reporting 20. Customer Communication 21. Data Analysis
Phase 6 - Specialized (If Applicable): 22. Installation (if applicable) 23. Servicing (if applicable) 24. Sterilization (if applicable) 25. Contamination Control (if applicable)
4. Develop Specific Documents
Creating a Quality Manual
Process:
-
Read the comprehensive guide:
- Read
references/quality-manual-guide.mdin full - Understand structure and required content
- Review examples provided
- Read
-
Gather organization information:
- Legal company name and addresses
- Product types and classifications
- Organizational structure
- Applicable regulations
- Scope of operations
- Any exclusions needed
-
Use template:
- Start with
assets/templates/quality-manual-template.md - Follow structure exactly (required by ISO 13485)
- Replace all placeholders
- Start with
-
Complete required sections:
- Section 0: Document control, approvals
- Section 1: Introduction, company overview
- Section 2: Scope and exclusions (critical - must justify exclusions)
- Section 3: Quality Policy (must be signed by top management)
- Sections 4-8: Address each ISO 13485 clause at policy level
- Appendices: Procedure list, org chart, process map, definitions
-
Key requirements:
- Must reference all 31 documented procedures (Appendix A)
- Must describe process interactions (Appendix C - create process map)
- Must define documentation structure (Section 4.2)
- Must justify any exclusions (Section 2.4)
-
Validation checklist:
- All required content per ISO 13485 Clause 4.2.2
- Quality Policy signed by top management
- All exclusions justified
- All procedures listed in Appendix A
- Process map included
- Organization chart included
Creating Procedures (SOPs)
General approach for all procedures:
-
Understand the requirement:
- Read relevant clause in
references/iso-13485-requirements.md - Understand WHAT must be documented
- Identify WHO, WHEN, WHERE for your organization
- Read relevant clause in
-
Use template structure:
- Follow CAPA or Document Control templates as examples
- Standard sections: Purpose, Scope, Definitions, Responsibilities, Procedure, Records, References
- Keep procedures clear and actionable
-
Define responsibilities clearly:
- Identify specific roles (not names)
- Define responsibilities for each role
- Ensure coverage of all required activities
-
Document the "what" not excessive "how":
- Procedures should define WHAT must be done
- Detailed HOW-TO goes in Work Instructions (Tier 3)
- Strike balance between guidance and flexibility
-
Include required elements:
- All elements specified in ISO 13485 clause
- Records that must be maintained
- Responsibilities for each activity
- References to related documents
Example: Creating CAPA Procedure
- Read ISO 13485 Clauses 8.5.2 and 8.5.3 from references
- Use
assets/templates/procedures/CAPA-procedure-template.md - Customize:
- CAPA prioritization criteria for your organization
- Root cause analysis methods you'll use
- Approval authorities and responsibilities
- Timeframes based on your operations
- Integration with complaint handling, audits, etc.
- Add forms as attachments:
- CAPA Request Form
- Root Cause Analysis Worksheet
- Action Plan Template
- Effectiveness Verification Checklist
Creating Medical Device Files (MDF)
What is an MDF:
- File for each medical device type or family
- Replaces separate DHF, DMR, DHR (per FDA QMSR harmonization)
- Contains all documentation about the device
Required contents per ISO 13485 Clause 4.2.3:
- General description and intended use
- Label and instructions for use specifications
- Product specifications
- Manufacturing specifications
- Procedures for purchasing, manufacturing, servicing
- Procedures for measuring and monitoring
- Installation requirements (if applicable)
- Risk management file(s)
- Verification and validation information
- Design and development file(s) (when applicable)
Process:
- Identify each device type or family
- Create MDF structure (folder or binder)
- Collect or create each required element
- Ensure traceability between documents 5
Content truncated.
More by K-Dense-AI
View all skills by K-Dense-AI →You might also like
flutter-development
aj-geddes
Build beautiful cross-platform mobile apps with Flutter and Dart. Covers widgets, state management with Provider/BLoC, navigation, API integration, and material design.
drawio-diagrams-enhanced
jgtolentino
Create professional draw.io (diagrams.net) diagrams in XML format (.drawio files) with integrated PMP/PMBOK methodologies, extensive visual asset libraries, and industry-standard professional templates. Use this skill when users ask to create flowcharts, swimlane diagrams, cross-functional flowcharts, org charts, network diagrams, UML diagrams, BPMN, project management diagrams (WBS, Gantt, PERT, RACI), risk matrices, stakeholder maps, or any other visual diagram in draw.io format. This skill includes access to custom shape libraries for icons, clipart, and professional symbols.
ui-ux-pro-max
nextlevelbuilder
"UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient."
godot
bfollington
This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.
nano-banana-pro
garg-aayush
Generate and edit images using Google's Nano Banana Pro (Gemini 3 Pro Image) API. Use when the user asks to generate, create, edit, modify, change, alter, or update images. Also use when user references an existing image file and asks to modify it in any way (e.g., "modify this image", "change the background", "replace X with Y"). Supports both text-to-image generation and image-to-image editing with configurable resolution (1K default, 2K, or 4K for high resolution). DO NOT read the image file first - use this skill directly with the --input-image parameter.
fastapi-templates
wshobson
Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.
Related MCP Servers
Browse all serversSerena is a free AI code generator toolkit providing robust code editing and retrieval, turning LLMs into powerful artif
Desktop Commander MCP unifies code management with advanced source control, git, and svn support—streamlining developmen
Use any LLM for deep research. Performs multi-step web search, content analysis, and synthesis for comprehensive researc
Empower AI with the Exa MCP Server—an AI research tool for real-time web search, academic data, and smarter, up-to-date
Boost Postgres performance with Postgres MCP Pro—AI-driven index tuning, health checks, and safe, intelligent SQL optimi
Control Gmail, Google Calendar, Docs, Sheets, Slides, Chat, Forms, Tasks, Search, and Drive with AI. Comprehensive Googl
Stay ahead of the MCP ecosystem
Get weekly updates on new skills and servers.