Token导航 LogoToken导航

Agent Skill · 开发

quality-documentation-manager(质量文件经理)

用于辅助文档、README、Markdown、说明文和内容稿件的整理与改写。它适合让 Agent 提炼结构、补齐章节、统一术语、检查链接或把零散材料整理成可读文档。使用时应保留项目已有事实、命令和路径,不要把未确认的信息写成确定结论;涉及对外文案时,还需要控制语气,避免过度营销或夸大能力。

quality-documentation-manager 是开发类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证为 MIT,第三方扫描有未通过项,按安装量在开发类的 21,746 个 Skill 里排第 6,631。

总安装 4,509周安装 186GitHub Stars 13,213下载 1,473核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:quality-documentation-manager(质量文件经理)
来源仓库:https://github.com/alirezarezvani/claude-skills
仓库路径:skills/quality-documentation-manager
安装命令:
npx skills add https://github.com/alirezarezvani/claude-skills --skill quality-documentation-manager
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/alirezarezvani/claude-skills --skill quality-documentation-manager

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

quality-documentation-manager 建立符合 ISO 13485 要求的受控文档管理系统与编号规范。涵盖文档创建、审批、修订与废止全生命周期管控,支持电子化记录合规性设计。提供模板库与变更控制流程图示例,确保质量文件可追溯且版本一致。

输出文档需经授权人员签字批准,禁止在未授权状态下发布正式质量记录。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/quality-documentation-manager

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/alirezarezvani/claude-skills --skill quality-d…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

quality-documentation-manager 怎么安装?

在终端执行 npx skills add https://github.com/alirezarezvani/claude-skills --skill quality-documentati…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

quality-documentation-manager 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

quality-documentation-manager 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

quality-documentation-manager 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

quality-documentation-manager 用的人多吗?

公开数据是累计安装 4,509 次,近一周安装 186 次,下载 1,473 次,GitHub 13,213 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

quality-documentation-manager 安全吗?

第三方扫描有未通过项,风险较高。除非你确认过源码,否则不建议直接安装到常用环境。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 3 个目录同时收录,说明这个 Skill 流传比较广。
  • 许可证明确为 MIT,商用和分发边界好判断。
  • 来源仓库有 13,213 星,维护活跃度相对可查。

先想清楚的地方

  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理开发类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
skill-vetter

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
quality-documentation-manager

质量文件经理 · 本页

4,50913,213只读MIT未通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

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


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

# 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

{
  "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

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

平台分布

Claude Code

29.92%
按下载量换算441

OpenCode

24.77%
按下载量换算365

Gemini CLI

19.56%
按下载量换算288

Antigravity

11.77%
按下载量换算173

Codex

7.48%
按下载量换算110

Cursor

3.56%
按下载量换算52

安全审计

Gen Agent Trust Hub

未通过

Socket

可疑

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。

继续浏览同类 Skills