CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

medical-device-mdr-auditor

Audit medical device technical files against EU MDR 2017/745 regulations.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Academic Writing/medical-device-mdr-auditor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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.

The skill body delivers genuinely useful audit specifics (parameter table, MDR check points, output format, exit codes) but wraps them in heavy template boilerplate, duplicate sections, and machine-specific paths. Consolidating to the audit-relevant content and moving generic process material into the existing reference file would improve every dimension.

Suggestions

Remove the boilerplate sections (Key Features, Risk Assessment, Security Checklist, Lifecycle Status, Evaluation Criteria, Dependencies listing standard-library modules) and the circular 'See ## X above' pointers; keep only the audit workflow, parameters, check points, and output format.

Replace the hardcoded '/Users/z04030865/...' paths and the nonexistent '20260318/scientific-skills/...' cd target with relative paths ('python scripts/main.py --input <technical-file-dir> --class IIa') so examples are copy-paste ready.

Move the audit check-point details and process boilerplate into references/audit-reference.md and keep a single clearly signaled '## References' section linking it, eliminating the duplicate References sections.

DimensionReasoningScore

Conciseness

The body is noticeably verbose with several padded boilerplate sections ('Key Features', 'Risk Assessment', 'Security Checklist', 'Lifecycle Status', 'Evaluation Criteria') that add no skill-specific knowledge, lists standard-library modules ('dataclasses', 'enum') as dependencies, and duplicates content (two '## References' sections, overlapping 'Output Requirements' and 'Response Template'). It stops short of anchor 1 because it never explains basic concepts Claude already knows.

2 / 5

Actionability

Concrete, executable guidance is present: py_compile and --help commands, a complete parameter table, exit codes, a compliance-level table, and a realistic JSON output example. It falls short of a 5 because all three usage examples hardcode a machine-specific path ('/Users/z04030865/.openclaw/workspace/...') and one example cds into a directory ('20260318/scientific-skills/...') that does not exist relative to the skill.

4 / 5

Workflow Clarity

Steps are listed and a fallback path with error handling exists, but the 'Workflow' and 'Example run plan' sections are generic boilerplate ('confirm the user objective', 'produce a bounded deliverable') rather than audit-specific sequencing, and batch mode (--config) has no output-validation checkpoint. Circular pointers ('See ## Usage above', 'See ## Workflow above') further blur the actual sequence.

3 / 5

Progressive Disclosure

A real reference file exists and is linked (references/audit-reference.md), but the link is buried in a second '## References' section while the first '## References' section lists only regulation citations, so navigation is confusing. Roughly 150 lines of boilerplate that belongs in reference files (risk tables, security checklists, lifecycle metadata) are inlined in SKILL.md, matching the 'some structure but could be better organized' anchor.

3 / 5

Total

12

/

20

Passed

Description

65%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.

The description is concise, specific, and highly distinct within its regulatory niche, but it omits any explicit 'when to use' trigger guidance and only names one concrete action. Adding a 'Use when...' clause and mentioning the specific artifacts checked (CER, PMS plan, PMCF plan) would raise both completeness and specificity.

Suggestions

Append a trigger clause such as 'Use when auditing medical device technical documentation for EU MDR 2017/745 compliance, or when the user mentions MDR, CER, PMS, or PMCF documents.'

Enumerate the concrete audit actions, e.g., 'Verify Clinical Evaluation Reports, Post-Market Surveillance plans, and PMCF plans against MDR Annex XIV and Article 83 requirements.'

Include common synonyms users would say, such as 'compliance', 'CE marking', and 'regulatory submission', to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

The description names a precise domain ('medical device technical files', 'EU MDR 2017/745 regulations') and a single concrete action ('Audit'), which matches the anchor for naming a domain with 1-2 concrete actions but not comprehensive coverage. It does not list the specific audit activities (e.g., checking CERs, PMS plans, PMCF plans) needed for a 4.

3 / 5

Completeness

The 'what' is clearly stated (audit medical device technical files against EU MDR 2017/745), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which the judging guidelines cap at 3. Not a 4 because 'when' is entirely absent rather than just under-specified.

3 / 5

Trigger Term Quality

Natural trigger terms like 'medical device', 'technical files', 'audit', 'EU MDR 2017/745', and 'regulations' give good keyword coverage, matching the 'good keyword coverage; a few natural terms missing' anchor. Common variations such as 'compliance', 'CE marking', or 'regulatory submission' are absent, preventing a 5.

4 / 5

Distinctiveness Conflict Risk

The description occupies a clear niche (EU MDR regulatory auditing of medical device technical files) with distinct trigger terms, giving minimal conflict risk with other skills. This matches the top anchor exactly.

5 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Academic Writing/medical-device-mdr-auditor/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.