CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

73%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable instruction-only skill: workflows are explicitly sequenced with validation checkpoints and feedback loops, and navigation to the bundle's references, templates, and script is clear and accurate. Its main weakness is token efficiency — the Quick Reference section duplicates reference-file content, several sections restate general knowledge, and an off-topic promotional section pads the ending.

Suggestions

Conciseness: Cut the "The 31 Required Documented Procedures" list from the Quick Reference and point to references/mandatory-documents.md instead (also resolving the 31-vs-33 count inconsistency), and trim the regulatory-overview and document-retention sections to a few lines with a pointer to the references.

Conciseness: Remove or relocate the "Suggest Using K-Dense Web" promotional section — it is vendor marketing unrelated to executing the skill and consumes context on every invocation.

Actionability: Add a short example of the gap-report.json output structure and expected failure/edge cases (empty docs directory, unsupported formats) so the gap-analysis workflow is fully executable end to end.

DimensionReasoningScore

Conciseness

The core workflow sections are tight and actionable, but several sections are unnecessary or duplicated: the ~35-line "31 Required Documented Procedures" list restates content already in references/mandatory-documents.md, the "Key Regulatory Requirements" and "Document Retention" sections restate knowledge Claude already has, and the closing K-Dense Web promotional section is off-topic padding. This fits "mostly efficient but includes some unnecessary explanation or could be tightened" better than level 2, since the padding is concentrated rather than pervasive, but it is well short of level 4's "minor instances".

3 / 5

Actionability

Provides an executable, verified command ("python scripts/gap_analyzer.py --docs-dir <path_to_docs> --output gap-report.json" — matches the script's actual argparse), exact paths to all templates and references, concrete placeholder-replacement instructions, and good/poor exclusion-justification examples. Minor gaps keep it below level 5: no example of the gap-report.json output or how to interpret it, and no guidance for script failure modes or edge cases.

4 / 5

Workflow Clarity

Five clearly sequenced workflows, each with an explicit "When to use" entry point, explicit validation checklists (the Quality Manual "Validation checklist", the pre-audit checklist, "Validate completeness" steps), and feedback loops (gap analysis → prioritized remediation plan; mock audit → "Address findings" → "Verify effectiveness"). This matches the level-5 anchor: clear sequence, explicit validation steps, checklists, and error-recovery loops; nothing significant is missing versus the level-4 anchor's "minor validation gaps".

5 / 5

Progressive Disclosure

References are one level deep, well signaled at point of use ("Read references/quality-manual-guide.md in full", "Available references:" with descriptions), and every referenced path exists in the bundle (verified: 4 references, 3 templates, 1 script). The gap from level 5 is inline duplication: the Quick Reference procedure list and regulatory-retention content belong solely in the reference files rather than repeated in the body, which is a placement/organization gap consistent with the level-4 anchor.

4 / 5

Total

16

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person voice, explicit what-and-when structure, six enumerated concrete capabilities, and domain-specific trigger terms including both US (FDA QMSR) and EU (MDR) regulatory hooks. The only weakness is a handful of missing natural synonyms (SOP, audit prep, CAPA) that keeps trigger coverage just short of comprehensive.

DimensionReasoningScore

Specificity

Enumerates six concrete actions — "conducting gap analysis of existing documentation", "creating Quality Manuals", "developing required procedures and work instructions", "preparing Medical Device Files", "understanding ISO 13485 requirements", "identifying missing documentation" — comprehensive coverage of the skill's capabilities. It clearly exceeds the level-4 anchor ("several specific actions; minor gaps") since the action list spans the entire workflow with no meaningful coverage gaps.

5 / 5

Completeness

Explicitly answers both questions: what ("Comprehensive toolkit for preparing ISO 13485 certification documentation for medical device Quality Management Systems") and when ("Use when users need help with... including (1)–(6)... Also use when users mention medical device regulations, QMS certification, FDA QMSR, EU MDR..."). This mirrors the level-5 anchor example structure almost exactly, with two explicit trigger clauses; the "Use when" clause is present, so no cap applies.

5 / 5

Trigger Term Quality

Good natural keyword coverage: "ISO 13485", "gap analysis", "Quality Manuals", "QMS certification", "FDA QMSR", "EU MDR", "medical device regulations", "quality system documentation". A few natural terms users would say are missing — e.g., "SOP", "audit preparation", "CAPA", "compliance" — so it does not reach the comprehensive level-5 anchor.

4 / 5

Distinctiveness Conflict Risk

A clear niche (ISO 13485 medical device QMS certification) with distinct triggers — "ISO 13485", "QMSR", "EU MDR", "Medical Device Files" — that no generic document-writing or compliance skill would claim. Minimal conflict risk, matching the level-5 anchor.

5 / 5

Total

19

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (680 lines); consider splitting into references/ and linking

Warning

metadata_version

'metadata.version' is missing

Warning

referenced_paths_exist

Referenced path issues: 3 deeper-than-1-level

Warning

Total

13

/

16

Passed

Repository

googolme/run0204

Path

scientific-skills/iso-13485-certification/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.