quality-documentation-manager

Document control system management for medical device QMS. Covers document numbering, version control, change management, and 21 CFR Part 11 compliance. Use when working on document control procedures, change control workflows, document numbering, version management, electronic signature compliance, or regulatory documentation review.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./ra-qm-team/skills/quality-documentation-manager/SKILL.md

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-organized regulatory reference skill with strong workflow validation and executable tooling. Its main weaknesses are some generic QMS knowledge padding and one unreferenced bundle script.

Suggestions

Add a short usage section for scripts/document_version_control.py (or link it from the version-control workflow) so every bundled tool is discoverable.

Move self-evident reference tables (lifecycle definitions, signature elements, common audit findings) into the reference files and keep SKILL.md to the actionable specifics.

Add an explicit validate-fix-retry loop inline in at least one workflow (e.g., "if the validator reports errors, fix the JSON and re-run") rather than relying on the script's interactive mode.

Dimension	Reasoning	Score
Conciseness	Mostly tabular and efficient, but several sections explain concepts Claude already knows (lifecycle stage definitions, signature element names, common audit findings, KPIs) that could be trimmed or moved to the reference files.	3 / 5
Actionability	Provides copy-paste-ready CLI commands for the validator, a concrete sample document JSON, and specific procedural workflows with an exact numbering format (PREFIX-CATEGORY-SEQUENCE[-REVISION]); minor gaps as most of the body is procedural reference rather than runnable code.	4 / 5
Workflow Clarity	Every multi-step workflow (Document Control, Numbering, Review, Change Control, Electronic Record Controls) ends with an explicit bolded Validation: acceptance checkpoint, supplemented by checklists and a validator script with interactive/JSON feedback modes.	5 / 5
Progressive Disclosure	Good structure with a Table of Contents, a dedicated Reference Documentation section describing each reference file's contents, and one-level-deep references; however, the bundled script document_version_control.py is never referenced in the body, leaving one asset undiscoverable.	4 / 5
	Total	16 / 20 Passed

Description

83%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, well-structured description that clearly states both its purpose and a concrete trigger clause for a specialized regulatory niche. It could nudge higher by converting topic nouns into concrete actions and adding a few more synonyms.

Suggestions

Lead with concrete action verbs (e.g., "Assigns document numbers, manages revisions, routes approvals, validates 21 CFR Part 11 controls") instead of "Covers ...".

Add high-frequency synonyms to the Use-when clause such as "SOPs", "audit trail", and "document master list".

Tighten the niche framing by pairing "document control" with "medical device / ISO 13485" earlier to reduce overlap with generic document skills.

Dimension	Reasoning	Score
Specificity	Enumerates several specific capability areas — "document numbering, version control, change management, and 21 CFR Part 11 compliance" — giving broad coverage, though framed as covered topics ("Covers...") rather than concrete action verbs, leaving minor gaps.	4 / 5
Completeness	Explicitly answers both what ("Document control system management for medical device QMS... Covers...") and when ("Use when working on...") with concrete trigger phrases, matching the top anchor structure.	5 / 5
Trigger Term Quality	The "Use when" clause lists six natural trigger phrases ("document control procedures, change control workflows, document numbering, version management, electronic signature compliance, or regulatory documentation review") with good coverage; a few common synonyms (e.g., SOP, audit trail) are absent from the description text.	4 / 5
Distinctiveness Conflict Risk	The medical-device QMS plus 21 CFR Part 11 framing carves a clear regulatory niche with distinct triggers; minor overlap risk remains with generic document-management skills given the broad term "document control".	4 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: ra-qm-team/skills/quality-documentation-manager/SKILL.md
Commit: 19392f7

Reviewed: ~1 hour ago

Table of Contents

Discovery Implementation Validation

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.