Agent skill

Quality Documentation Manager

by borghei in borghei/Claude-Skills

Document control for medical device QMS, covering numbering, version control, change management, and 21 CFR Part 11 compliance.

MITAuto-check passedDevelopment

Install Quality Documentation Manager

skills CLI
$ npx skills add borghei/Claude-Skills --skill quality-documentation-manager -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install borghei/Claude-Skills quality-documentation-manager --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/ra-qm-team/quality-documentation-manager .claude/skills/quality-documentation-manager && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
quality-documentation-manager
GitHub stars
881
Token cost
~5.1k tokens
SKILL.md length
2,072 words
Files
4 (incl. scripts, references)
Skills in repo
349
Repo updated
First seen
Licence
MIT

At a glance

Document control for medical device QMS, covering numbering, version control, change management, and 21 CFR Part 11 compliance.

  • Works in 8 steps: Assign document number per numbering… → Create document using controlled template → Route for review to required reviewers → …
  • Document control procedures
  • SKILL.md covers Table of Contents, Clarify First, Document Control Workflow and Document Numbering System, plus 4 more sections
  • Runs Python scripts from its folder; calls python

What it does

Quality Documentation Manager is an agent skill from borghei/Claude-Skills. Document control for medical device QMS, covering numbering, version control, change management, and 21 CFR Part 11 compliance. Use for document control procedures, change control workflows, and electronic signature compliance.

Its SKILL.md is about 5.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts and reference files (for example `references/21cfr11-compliance-guide.md`, `references/document-control-procedures.md` and `scripts/document_validator.py`).

It sits in Development, covering Git workflow. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.

When your agent uses it

  • Document control procedures
  • Change control workflows
  • Electronic signature compliance

Example prompts

  • “/quality-documentation-manager”

Requirements

  • Python 3

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Assign document number per numbering procedure
  2. Create document using controlled template
  3. Route for review to required reviewers
  4. Address review comments and document responses
  5. Obtain required approval signatures
  6. Assign effective date and distribute
  7. Update Document Master List
  8. Validation: Document accessible at point of use; obsolete versions removed

What it can do on your machine

Read from SKILL.md and the folder at commit 4a698e8. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Quality Documentation Manager loads about 5.1k tokens when it runs, and up to ~11k if it reads all its reference files. Until then it costs about 64 tokens; SKILL.md has 2,072 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~64
When it runs · the whole SKILL.md, loaded when a task matches
~5.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~11k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 2,072 words, ~5,071 tokens.

Download SKILL.mdSave it as .claude/skills/quality-documentation-manager/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
quality-documentation-manager
description
Document control for medical device QMS, covering numbering, version control, change management, and 21 CFR Part 11 compliance. Use for document control procedures, change control workflows, and electronic signature compliance.
license
MIT + Commons Clause
metadata.version
1.0.0
metadata.author
borghei
metadata.category
compliance
metadata.domain
document-control
metadata.updated
2026-03-31
metadata.tags
document-control, 21-cfr-part-11, electronic-signatures, sop

Quality Documentation Manager

Document control system design and management for ISO 13485-compliant quality management systems, including numbering conventions, approval workflows, change control, and electronic record compliance.


Table of Contents


Clarify First

Before setting up document control or validating a document, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • Document type — QM, SOP, WI, TF, SPEC, or PLN (sets the required reviewers, approvers, and numbering)
  • Regulatory scope — ISO 13485 only vs 21 CFR Part 11 electronic records (determines whether audit-trail and e-signature controls are required)
  • Change classification — administrative, minor, major, or emergency (sets the approval path and impact assessment)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the document.

Document Control Workflow

Implement document control from creation through obsolescence:

  1. Assign document number per numbering procedure
  2. Create document using controlled template
  3. Route for review to required reviewers
  4. Address review comments and document responses
  5. Obtain required approval signatures
  6. Assign effective date and distribute
  7. Update Document Master List
  8. Validation: Document accessible at point of use; obsolete versions removed
Document Lifecycle Stages
StageDefinitionActions Required
DraftUnder creation or revisionAuthor editing, not for use
ReviewCirculated for reviewReviewers provide feedback
ApprovedAll signatures obtainedReady for training/distribution
EffectiveTraining complete, releasedAvailable for use
SupersededReplaced by newer revisionRemove from active use
ObsoleteNo longer applicableArchive per retention schedule
Document Types and Prefixes
PrefixDocument TypeTypical Content
QMQuality ManualQMS overview, scope, policy
SOPStandard Operating ProcedureProcess-level procedures
WIWork InstructionTask-level step-by-step
TFTemplate/FormControlled forms
SPECSpecificationProduct/process specs
PLNPlanQuality/project plans
Required Reviewers by Document Type
Document TypeRequired ReviewersRequired Approvers
SOPProcess Owner, QAQA Manager, Process Owner
WIArea Supervisor, QAArea Manager
SPECEngineering, QAEngineering Manager, QA
TFProcess OwnerQA
Design DocumentsDesign Team, QADesign Control Authority

Document Numbering System

Assign consistent document numbers for identification and retrieval.

Numbering Format

Standard format: PREFIX-CATEGORY-SEQUENCE[-REVISION]

Example: SOP-02-001-A

SOP = Document type (Standard Operating Procedure)
02  = Category code (Document Control)
001 = Sequential number
A   = Revision indicator
Category Codes
CodeFunctional AreaDescription
01Quality ManagementQMS procedures, management review
02Document ControlThis area
03Human ResourcesTraining, competency
04Design & DevelopmentDesign control processes
05PurchasingSupplier management
06ProductionManufacturing procedures
07Quality ControlInspection, testing
08CAPACorrective/preventive actions
09Risk ManagementISO 14971 processes
10Regulatory AffairsSubmissions, compliance
Numbering Workflow
  1. Author requests document number from Document Control
  2. Document Control verifies category assignment
  3. Document Control assigns next available sequence number
  4. Number recorded in Document Master List
  5. Author creates document using assigned number
  6. Validation: Number format matches standard; no duplicates in Master List
Revision Designation
Change TypeRevision IncrementExample
Major revisionIncrement numberRev 01 → Rev 02
Minor revisionIncrement sub-revisionRev 01 → Rev 01.1
AdministrativeNo change or letter suffixRev 01 → Rev 01a

See references/document-control-procedures.md for complete numbering guidance.


Approval and Review Process

Obtain required reviews and approvals before document release.

Review Workflow
  1. Author completes document draft
  2. Author submits for review via routing form or DMS
  3. Reviewers assigned based on document type
  4. Reviewers provide comments within review period (5-10 business days)
  5. Author addresses comments and documents responses
  6. Author resubmits revised document
  7. Approvers sign and date
  8. Validation: All required reviewers completed; all comments addressed with documented disposition
Comment Disposition
DispositionAction Required
AcceptIncorporate comment as written
Accept with modificationIncorporate with changes, document rationale
RejectDo not incorporate, document justification
DeferAddress in future revision, document reason
Approval Matrix
Document Level 1 (Policy/QM): CEO or delegate + QA Manager
Document Level 2 (SOP): Department Manager + QA Manager
Document Level 3 (WI/TF): Area Supervisor + QA Representative
Signature Requirements
ElementRequirement
NamePrinted name of signer
SignatureHandwritten or electronic signature
DateDate signature applied
RoleFunction/role of signer

Change Control Process

Manage document changes systematically through review and approval.

Change Control Workflow
  1. Identify need for document change
  2. Complete Change Request Form with justification
  3. Document Control assigns change number and logs request
  4. Route to reviewers for impact assessment
  5. Obtain approvals based on change classification
  6. Author implements approved changes
  7. Update revision number and change history
  8. Validation: Changes match approved scope; change history complete
Change Classification
ClassDefinitionApproval LevelExamples
AdministrativeNo content impactDocument ControlTypos, formatting
MinorLimited content changeProcess Owner + QAClarifications
MajorSignificant content changeFull review cycleNew requirements
EmergencyUrgent safety/complianceExpedited + retrospectiveSafety issues
Impact Assessment Checklist
Impact AreaAssessment Questions
TrainingDoes change require retraining?
EquipmentDoes change affect equipment or systems?
ValidationDoes change require revalidation?
RegulatoryDoes change affect regulatory filings?
Other DocumentsWhich related documents need updating?
RecordsWhat records are affected?
Change History Documentation

Each document must include change history:

| Revision | Date | Description | Author | Approver |
|----------|------|-------------|--------|----------|
| 01 | 2023-01-15 | Initial release | J. Smith | M. Jones |
| 02 | 2024-03-01 | Updated workflow | J. Smith | M. Jones |

21 CFR Part 11 Compliance

Implement electronic record and signature controls for FDA compliance.

Part 11 Scope
Applies ToDoes Not Apply To
Records required by FDA regulationsPaper records
Records submitted to FDAInternal non-regulated documents
Electronic signatures on required recordsGeneral email communication
Electronic Record Controls
  1. Validate system for accuracy and reliability
  2. Implement secure audit trail for all changes
  3. Restrict system access to authorized individuals
  4. Generate accurate copies in human-readable format
  5. Protect records throughout retention period
  6. Validation: Audit trail captures who, what, when for all changes
Audit Trail Requirements
RequirementImplementation
SecureCannot be modified by users
Computer-generatedSystem creates automatically
Time-stampedDate and time of each action
Original valuesPrevious values retained
User identityWho made each change
Electronic Signature Requirements
RequirementImplementation
Unique to individualNot shared between persons
At least 2 componentsUser ID + password minimum
Signature manifestationName, date/time, meaning displayed
Linked to recordCannot be excised or copied
Signature Manifestation

Every electronic signature must display:

ElementExample
Printed nameJohn Smith
Date and time2024-03-15 14:32:05 EST
MeaningApproved for Release
System Controls Checklist

Access Controls:

  • Unique user ID for each person
  • Password complexity enforced
  • Account lockout after failed attempts
  • Session timeout after inactivity

Audit Trail:

  • All record creation logged
  • All modifications logged with old/new values
  • User identity captured
  • Date/time stamp on all entries

Security:

  • Role-based access control
  • Encryption for data at rest and in transit
  • Regular backup and tested recovery

See references/21cfr11-compliance-guide.md for detailed compliance requirements.


Reference Documentation

Document Control Procedures

references/document-control-procedures.md contains:

  • Document numbering system and format
  • Document lifecycle stages and transitions
  • Review and approval workflow details
  • Change control process with classification criteria
  • Distribution and access control methods
  • Record retention periods and disposal procedures
  • Document Master List requirements
21 CFR Part 11 Compliance Guide

references/21cfr11-compliance-guide.md contains:

  • Part 11 scope and applicability
  • Electronic record requirements (§11.10)
  • Electronic signature requirements (§11.50, 11.100, 11.200)
  • System control specifications
  • Validation approach and documentation
  • Compliance checklist and gap assessment template
  • Common FDA deficiencies and prevention

Tools

Document Validator
bash
# Validate document metadata
python scripts/document_validator.py --doc document.json

# Interactive validation mode
python scripts/document_validator.py --interactive

# JSON output for integration
python scripts/document_validator.py --doc document.json --output json

# Generate sample document JSON
python scripts/document_validator.py --sample > sample_doc.json

Validates:

  • Document numbering convention compliance
  • Title and status requirements
  • Date validation (effective, review due)
  • Approval requirements by document type
  • Change history completeness
  • 21 CFR Part 11 controls (audit trail, signatures)
Sample Document Input
json
{
  "number": "SOP-02-001",
  "title": "Document Control Procedure",
  "doc_type": "SOP",
  "revision": "03",
  "status": "Effective",
  "effective_date": "2024-01-15",
  "review_date": "2025-01-15",
  "author": "J. Smith",
  "approver": "M. Jones",
  "change_history": [
    {"revision": "01", "date": "2022-01-01", "description": "Initial release"},
    {"revision": "02", "date": "2023-01-15", "description": "Updated workflow"},
    {"revision": "03", "date": "2024-01-15", "description": "Added e-signature requirements"}
  ],
  "has_audit_trail": true,
  "has_electronic_signature": true,
  "signature_components": 2
}

Document Control Metrics

Track document control system performance.

Key Performance Indicators
MetricTargetCalculation
Document cycle time<30 daysAverage days from draft to effective
Review completion rate>95%Reviews completed on time / Total reviews
Change request backlog<10Open change requests at month end
Overdue review rate<5%Documents past review date / Total effective
Audit finding rate<2 per auditDocument control findings per internal audit
Show full SKILL.md (829 more words)Show less
Periodic Review Schedule
Document TypeReview Frequency
PolicyEvery 3 years
SOPEvery 2 years
WIEvery 2 years
SpecificationsAs needed or with product changes
Forms/TemplatesEvery 3 years

Regulatory Requirements

ISO 13485:2016 Clause 4.2
Sub-clauseRequirement
4.2.1Quality management system documentation
4.2.2Quality manual
4.2.3Medical device file (technical documentation)
4.2.4Control of documents
4.2.5Control of records
FDA 21 CFR 820
SectionRequirement
820.40Document controls
820.180General record requirements
820.181Device master record
820.184Device history record
820.186Quality system record
Common Audit Findings
FindingPrevention
Obsolete documents in useImplement distribution control
Missing approval signaturesEnforce workflow before release
Incomplete change historyRequire history update with each revision
No periodic review scheduleEstablish and enforce review calendar
Inadequate audit trailValidate DMS for Part 11 compliance

Troubleshooting

ProblemLikely CauseResolution
Document validator reports "invalid numbering format"Document number does not match the PREFIX-CATEGORY-SEQUENCE patternEnsure the number follows the format SOP-02-001 (type prefix, 2-digit category code, 3-digit sequence). Check that the prefix matches a recognized document type (QM, SOP, WI, TF, SPEC, PLN).
Validation flags missing approver despite having signaturesapprover field is null or empty in the input JSONPopulate the approver field with the name of the approving authority. For SOPs, both Process Owner and QA Manager are required.
Review date validation fails for a current documentreview_date is in the pastUpdate the review date to reflect the next scheduled review. Documents past their review date should be flagged for periodic review and re-approval.
Change history marked incompleteNot all revisions have entries in the change_history arrayEvery revision increment must have a corresponding change history entry with revision number, date, description, and author. Fill gaps in the history.
Part 11 controls flagged despite using an eDMShas_audit_trail or has_electronic_signature set to falseSet both to true and ensure signature_components is at least 2 (user ID + password minimum per Part 11). Verify the eDMS produces computer-generated, timestamped audit trails.
Interactive mode does not display all validation rulesTerminal width too narrow for table outputWiden the terminal window or use --output json for structured output that is not affected by display width.
Obsolete documents still appearing as "Effective"Status field not updated during revision cycleWhen a new revision is released, update the prior revision's status to "Superseded" and ensure it is removed from points of use. Run the validator against the superseded document to confirm.

Success Criteria

  • Document numbering system enforced with zero duplicate numbers in the Document Master List and 100% format compliance
  • Document cycle time (draft to effective) averages less than 30 business days across all document types
  • Review completion rate exceeds 95% (reviews completed on time vs. total reviews initiated)
  • Overdue periodic review rate below 5% of total effective documents at any point
  • 21 CFR Part 11 compliance verified for all electronic records: audit trails capture who/what/when for every change, electronic signatures include printed name, date/time, and meaning
  • Change control process handles 100% of document changes through the classification workflow (Administrative/Minor/Major/Emergency) with documented impact assessments
  • Zero external audit findings related to document control in the most recent certification or surveillance audit

Scope & Limitations

In Scope:

  • Document numbering convention design and validation
  • Document lifecycle management (Draft through Obsolete)
  • Review and approval workflow enforcement
  • Change control process with classification and impact assessment
  • 21 CFR Part 11 electronic record and electronic signature compliance validation
  • Periodic review schedule management
  • Document Master List maintenance

Out of Scope:

  • eDMS software selection, implementation, or validation (the tool validates metadata, not the DMS platform itself)
  • EU Annex 11 computerized system validation (complementary to Part 11 but requires separate assessment approach)
  • Technical file / Design History File content creation (use regulatory-affairs-head for technical documentation)
  • Record retention schedule creation (the tool validates dates but does not determine regulatory retention periods)
  • Physical document distribution or archival logistics
  • Training record management (the tool validates training-related documents but does not manage training programs)

Integration Points

SkillIntegration
quality-manager-qms-iso13485Document control (Clause 4.2.3) and record control (Clause 4.2.4) are core QMS processes; the validator enforces ISO 13485 documentation requirements
qms-audit-expertInternal audits of Clause 4.2 verify document control effectiveness; audit findings drive document process improvements
quality-manager-qmrDocument control metrics (cycle time, overdue reviews, backlog) are reported to management review as QMS performance indicators
fda-consultant-specialistFDA QMSR (effective Feb 2026) incorporates ISO 13485 Clause 4.2 by reference; Part 11 compliance remains a separate FDA requirement for electronic records
capa-officerCAPA actions frequently require document revisions; the change control process tracks CAPA-driven document changes

Tool Reference

document_validator.py

Validates document metadata, numbering conventions, and regulatory control requirements.

FlagRequiredDescription
--docYes (or --interactive or --sample)Path to document metadata JSON file containing number, title, type, revision, status, dates, approvers, change history, and Part 11 fields
--interactiveNoLaunch interactive validation mode for guided document entry
--outputNoOutput format: json for structured output with severity-rated findings, omit for human-readable text
--sampleNoGenerate a sample document JSON template (pipe to file with > sample_doc.json)

© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (scripts, references) in ra-qm-team/quality-documentation-manager of borghei/Claude-Skills.

  • SKILL.md
  • references/21cfr11-compliance-guide.md
  • references/document-control-procedures.md
  • scripts/document_validator.py

Open the folder on GitHubat commit 4a698e8

Compare with similar skills

Quality Documentation Manager next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Quality Documentation Manager compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Quality Documentation Manager this skillborghei/Claude-Skills881—~5.1kAutomated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Code Design Rationale Investigatorcursor/plugins10k9 repos~2.6kAutomated safety check: PassNone
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Migrate Internal Package into GhostTryGhost/Ghost55k—~3.8kAutomated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0

Similar skills

  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Official

    Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.

    10k GitHub starsUsed in 9 repos~2.6k tokens
    DevelopmentAuto-check passed
  • Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed
  • Moves a package from another TryGhost repository into Ghost as an internal workspace package while keeping its Git history, with checkpoints for the steps that need an administrator.

    55k GitHub stars~3.8k tokensUpdated today
    DevelopmentAuto-check passed
  • Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed
  • Writes Conventional Commits whose bodies carry action lines recording the intent, decisions and constraints behind a change, not only what changed.

    29k GitHub starsUsed in 1 repo~2.7k tokens
    DevelopmentAuto-check passed

More from borghei/Claude-Skills

All 349 skills in this repo
  • Agents In The Team

    borghei/Claude-Skills

    Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.

    881 GitHub stars~4.2k tokensUpdated today
    Auto-check passed
  • AI Content Disclosure

    borghei/Claude-Skills

    Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.

    881 GitHub stars~3.4k tokensUpdated today
    Auto-check passed
  • AI Prototyping

    borghei/Claude-Skills

    Idea to AI-generated prototype to customer validation to engineering handoff.

    881 GitHub stars~3.6k tokensUpdated today
    Auto-check passed
  • Analytics Engineer

    borghei/Claude-Skills

    Analytics engineering across data modeling, dbt, transformation, and semantic layers.

    881 GitHub stars~3.4k tokensUpdated today
    Auto-check passed
  • Ansoff Matrix

    borghei/Claude-Skills

    Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.

    881 GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Brainstorm Okrs

    borghei/Claude-Skills

    OKR brainstorming and validation using the Radical Focus framework — outcome objectives, measurable key results, counter-metrics.

    881 GitHub stars~1.4k tokensUpdated today
    Auto-check passed

Categories

Questions about Quality Documentation Manager

What does Quality Documentation Manager do?

Document control for medical device QMS, covering numbering, version control, change management, and 21 CFR Part 11 compliance. Quality Documentation Manager is an agent skill from borghei/Claude-Skills. Document control for medical device QMS, covering numbering, version control, change management, and 21 CFR Part 11 compliance.

When should I use Quality Documentation Manager?

Quality Documentation Manager fits situations like: document control procedures; change control workflows; electronic signature compliance.

How do I install Quality Documentation Manager in Claude Code?

Run `npx skills add borghei/Claude-Skills --skill quality-documentation-manager -a claude-code`. Or copy the skill folder (ra-qm-team/quality-documentation-manager in borghei/Claude-Skills) into .claude/skills/quality-documentation-manager in your project. Claude Code loads it when a task matches its description.

How do I install Quality Documentation Manager in Codex?

Run `npx skills add borghei/Claude-Skills --skill quality-documentation-manager -a codex`. Or copy the skill folder (ra-qm-team/quality-documentation-manager in borghei/Claude-Skills) into .agents/skills/quality-documentation-manager in your project. Codex loads it when a task matches its description.

Can I use Quality Documentation Manager in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add borghei/Claude-Skills --skill quality-documentation-manager -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/quality-documentation-manager, .gemini/skills/quality-documentation-manager, .github/skills/quality-documentation-manager and .opencode/skills/quality-documentation-manager in your project.

What does Quality Documentation Manager need to run?

Going by SKILL.md and its folder, Quality Documentation Manager needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.

Does Quality Documentation Manager access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Quality Documentation Manager safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Quality Documentation Manager use?

Quality Documentation Manager is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Quality Documentation Manager use?

About 5.1k tokens (SKILL.md is roughly 20k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 6.3k tokens, read only when the agent opens those files.

What are the alternatives to Quality Documentation Manager?

Skills that share tags, products or a category with Quality Documentation Manager: Finishing a Development Branch (obra/superpowers, 296k stars), Code Design Rationale Investigator (cursor/plugins, 10k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars) and Migrate Internal Package into Ghost (TryGhost/Ghost, 55k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Quality Documentation Manager?

borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 881 GitHub stars. The repository holds 349 skills in this directory. The repository was last updated on October 7, 2026.

Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.