CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

71

1.26x
Quality

35%

Does it follow best practices?

Impact

95%

1.26x

Average score across 6 eval scenarios

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./ra-qm-team/quality-manager-qmr/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

N/A

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

Something went wrong

Implementation

35%

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

This skill is a comprehensive but excessively verbose reference document that reads more like a quality management handbook than a concise skill file. While it has reasonable workflow structure with validation checkpoints and references to external files, the vast majority of content (KPI definitions, culture survey questions, compliance matrices, decision frameworks) is reference material that should be split into separate files. The skill would benefit enormously from aggressive trimming to focus on the core workflows and decision points, pushing detailed tables and templates into referenced documents.

Suggestions

Move the detailed reference tables (Core Quality KPIs, Culture Survey Categories, Compliance Matrix, Quality Objective Structure template, Management Review Input Template) into the referenced files and keep only summary pointers in the main skill body.

Reduce the main skill to under 150 lines focusing on the key workflows, escalation logic, and authority boundaries—the content Claude actually needs to make decisions.

Add explicit feedback loops to workflows, especially for regulatory compliance monitoring (e.g., 'If impact assessment reveals gaps → trigger CAPA → re-assess after implementation').

Remove tables that describe general quality management knowledge Claude already possesses (e.g., SMART criteria explanation, generic culture improvement actions) and focus on organization-specific or non-obvious guidance.

DimensionReasoningScore

Conciseness

This is extremely verbose at ~400+ lines. Much of the content consists of reference tables (compliance matrices, KPI definitions, culture survey questions, objective categories) that Claude already knows or could generate on demand. The management review input template, quality objective structure template, and numerous lookup tables bloat the skill far beyond what's needed for actionable guidance.

1 / 3

Actionability

The workflows provide numbered step sequences which give some concrete guidance, and there are templates with fill-in-the-blank structures. However, there is no executable code shown (the script reference just points to an external file), and much of the content is descriptive tables and frameworks rather than specific executable instructions. The guidance is more procedural/organizational than technically actionable.

2 / 3

Workflow Clarity

Multiple workflows are clearly sequenced with numbered steps, and each ends with a validation checkpoint. However, the validation steps are fairly generic ('Each KPI has owner, target, data source'), and there are no feedback loops for error recovery. For processes involving regulatory compliance and quality system changes (which are consequential), the lack of explicit error handling and retry mechanisms is a gap.

2 / 3

Progressive Disclosure

There is a table of contents and references to external files (management-review-guide.md, quality-kpi-framework.md, scripts), which is good. However, the main file itself is monolithic with enormous amounts of inline content (KPI tables, culture assessment dimensions, compliance matrices, decision frameworks) that should be in reference files rather than the main skill body.

2 / 3

Total

7

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
alirezarezvani/claude-skills
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.