quality-documentation-manager

tessl i github:alirezarezvani/claude-skills --skill quality-documentation-manager

Senior Quality Documentation Manager for comprehensive documentation control and regulatory document review. Provides document management system design, change control, configuration management, and regulatory documentation oversight. Use for document control system implementation, regulatory document review, change management, and documentation compliance verification.

49%

Overall

Validation — 81%

Implementation — 20%

Activation — 67%

SKILL.md

Review

Evals

Validation

81%

Warnings & errors only

Criteria	Description	Result
description_trigger_hint	Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...')	Warning
metadata_version	'metadata' field is not a dictionary	Warning
license_field	'license' field is missing	Warning

	Total	13 / 16 Passed

Implementation

20%

This skill reads like a comprehensive policy document or training manual rather than actionable guidance for Claude. It extensively describes organizational frameworks, taxonomies, and conceptual processes but provides no concrete, executable instructions. The referenced scripts and templates don't exist in the content, and the verbose explanations of standard quality management concepts waste token budget on information Claude already possesses.

Suggestions

Replace abstract framework descriptions with concrete, executable examples - show actual document templates, specific validation commands, or real code from the referenced scripts

Remove explanations of basic concepts (what document control is, what change management means) and focus only on project-specific procedures and decisions Claude needs to make

Add concrete validation steps with specific commands or checks, especially for the change control and DMS implementation workflows

Reduce the main file to a concise overview (under 100 lines) and move detailed frameworks to the referenced files, ensuring those files contain actionable content

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive explanations of concepts Claude already knows (document control, change management, regulatory compliance). The content is padded with unnecessary taxonomies, frameworks, and organizational structures that don't provide actionable guidance.	1 / 3
Actionability	Almost entirely abstract and descriptive rather than instructive. No executable code despite referencing Python scripts, no concrete commands, no specific examples of actual documents or procedures. Describes what should exist rather than how to do it.	1 / 3
Workflow Clarity	Contains workflow diagrams with sequential steps (Change Control Workflow, DMS Implementation), but lacks validation checkpoints, concrete verification steps, and feedback loops. Steps are conceptual rather than actionable with no error recovery guidance.	2 / 3
Progressive Disclosure	References external files (references/dms-storage-design.md, scripts/) which is good structure, but the main document is a monolithic wall of text with excessive inline content that should be split into separate reference documents.	2 / 3
	Total	6 / 12 Passed

Activation

67%

The description adequately covers both what the skill does and when to use it, earning full marks for completeness. However, it relies on somewhat abstract professional terminology rather than concrete actions, and the trigger terms could be expanded to include more natural variations users might employ. The regulatory/quality niche provides some distinctiveness but could be sharpened.

Suggestions

Add more concrete actions like 'create document templates', 'manage revision history', 'route documents for approval', 'generate compliance reports' to improve specificity.

Expand trigger terms to include common variations like 'SOPs', 'QMS', 'version control', 'audit trail', 'document approval', 'controlled documents', 'FDA documentation', or 'ISO compliance'.

Dimension	Reasoning	Score
Specificity	Names the domain (documentation control, regulatory review) and lists some actions (document management system design, change control, configuration management), but uses somewhat abstract terms rather than concrete specific actions like 'create document templates' or 'track revision history'.	2 / 3
Completeness	Clearly answers both what (document management system design, change control, configuration management, regulatory documentation oversight) and when (document control system implementation, regulatory document review, change management, documentation compliance verification) with explicit 'Use for' clause.	3 / 3
Trigger Term Quality	Includes relevant keywords like 'document control', 'regulatory document review', 'change management', and 'compliance verification', but missing common variations users might say like 'SOPs', 'version control', 'audit trail', 'QMS', or 'document approval workflow'.	2 / 3
Distinctiveness Conflict Risk	The regulatory/quality focus provides some distinction, but 'documentation' and 'document management' are broad terms that could overlap with general documentation skills or technical writing skills. The 'Senior Quality Documentation Manager' framing helps but isn't reflected in the trigger terms.	2 / 3
	Total	9 / 12 Passed

Reviewed

19 days ago

Table of Contents

Validation Implementation Activation

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.