CtrlK
BlogDocsLog inGet started
Tessl Logo

capa-officer

CAPA system management for medical device QMS. Covers root cause analysis, corrective action planning, effectiveness verification, and CAPA metrics. Use when running CAPA investigations, 5-Why analysis, fishbone diagrams, root cause determination, corrective action tracking, effectiveness verification, or CAPA program optimization.

73

Quality

92%

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

The canonical home for this skill is capa-officer in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 content is a well-structured, actionable CAPA reference with strong workflow sequencing and validation checkpoints. Its main weakness is progressive disclosure: it references bundle files that are not actually shipped, leaving inlined content that should have been split out.

Suggestions

Ship the referenced bundle files (references/rca-methodologies.md, references/effectiveness-verification-guide.md, scripts/capa_tracker.py) or remove the references and keep the content inline — do not point at files that do not exist.

Move the full 5-Why worked example and RCA method detail into references/rca-methodologies.md to reduce duplication with the inline summary and tighten token use.

Verify the capa_tracker.py script matches the documented flags (--capas, --interactive, --output json, --sample) so the copy-paste commands are actually executable.

DimensionReasoningScore

Conciseness

The body is dense and mostly reference-grade (tables, templates, decision trees) with little padding of concepts Claude already knows, but the full 5-Why example and RCA method detail are inlined while also being attributed to references/rca-methodologies.md, creating some duplication that could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready commands ('python scripts/capa_tracker.py --capas capas.json --output json'), a complete sample JSON input, and concrete templates (5-Why, action plan) that cover the common CAPA cases.

5 / 5

Workflow Clarity

Each major process (investigation, action planning, effectiveness verification) is a numbered sequence with an explicit '**Validation:**' checkpoint, plus decision trees, checklists, and feedback loops ('CAPA INEFFECTIVE → re-investigate root cause / revise actions').

5 / 5

Progressive Disclosure

Structure and inline reference signaling ('See references/rca-methodologies.md') are clear, but the referenced files (references/rca-methodologies.md, references/effectiveness-verification-guide.md, scripts/capa_tracker.py) do not exist in the bundle, so navigation dead-ends and content that should live in those files remains inlined.

3 / 5

Total

17

/

20

Passed

Description

100%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 excellent: third-person, concise, and explicit about both capabilities and trigger conditions. It lists multiple concrete actions and comprehensive natural trigger terms with minimal conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'root cause analysis, corrective action planning, effectiveness verification, and CAPA metrics' plus '5-Why analysis, fishbone diagrams, root cause determination, corrective action tracking, effectiveness verification, or CAPA program optimization' — giving comprehensive coverage of the domain.

5 / 5

Completeness

Explicitly answers both 'what' ('CAPA system management for medical device QMS. Covers root cause analysis, corrective action planning, effectiveness verification, and CAPA metrics.') and 'when' ('Use when running CAPA investigations, 5-Why analysis...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

The 'Use when' clause covers natural domain phrases including synonyms ('root cause analysis' / 'root cause determination', '5-Why analysis', 'fishbone diagrams') that a user would actually say, with comprehensive coverage.

5 / 5

Distinctiveness Conflict Risk

A clear niche (CAPA within medical device QMS) with distinct triggers like '5-Why analysis', 'fishbone diagrams', and 'effectiveness verification' that are unlikely to fire for unrelated skills.

5 / 5

Total

20

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 8 missing

Warning

Total

14

/

16

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.