mastercontrol

Classifies MasterControl quality and manufacturing actions into read, write, and destructive gates.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/MetaFloor-AI/metafloor-scm-plugin-openai --skill mastercontrol-metafloor-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mastercontrol
Source: https://github.com/MetaFloor-AI/metafloor-scm-plugin-openai/tree/main/skills/platforms/quality/mastercontrol
Command: npx skills add https://github.com/MetaFloor-AI/metafloor-scm-plugin-openai --skill mastercontrol-metafloor-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Operating a validated GxP system like MasterControl is risky because nearly every meaningful write is a routed, e-signed act on an immutable audit trail, and mistakes like a wrong complaint reportability call or a premature batch release cannot be undone. This Skill gives an AI agent the judgment to classify each MasterControl action and pause consequential ones for human approval. ## Core Features & Use Cases - Action classification matrix: Maps MasterControl operation families (route advances, e-signatures, dispositions, document releases, batch releases, config changes) to read, reversible write, committing write, and destructive gates. - GxP domain model: Covers quality events (deviations, CAPA, complaints, change control, audits), document control with Released vs Effective states, the training cascade, and Manufacturing Excellence electronic batch records with review by exception. - Recovery and edge-state guidance: Provides correct-forward recovery patterns, reclassification rules, and seam handling toward LIMS and ERP systems. - Use Case: When asked to release a batch in MasterControl, the agent checks for open exceptions and missing signatures, treats the release as a destructive action, and requires a named approver before executing. ## Quick Start Ask the agent to classify and safely execute a MasterControl action such as advancing a change control route or releasing a controlled SOP.

Frequently Asked Questions about mastercontrol

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely release a batch in MasterControl?

Batch release is treated as a destructive action requiring a named approver and a re-read of live state. Before releasing, verify every flagged exception is dispositioned, all required signatures are captured, and no linked deviation is open, since review by exception only surfaces flagged items.

What is the difference between Released and Effective in MasterControl document control?

Released means a document is approved and issued, while Effective means it is in force on its effective date. A future-dated release leaves the prior revision governing, and releasing also auto-assigns training tasks to mapped roles.

Why is a complaint reportability decision so high risk?

The reportability call starts a statutory clock at awareness, such as a 30-day or 5-day MDR deadline. A wrong non-reportable decision misses a regulatory deadline that no forward correction fully repairs, so it is gated as the hardest destructive action.

Can MasterControl actions be undone after an e-signature?

No. A completed signature task is a permanent 21 CFR Part 11 record on an immutable audit trail. Corrections are made forward as new entries; nothing is erased, and signing on another's behalf is a data-integrity violation.

When should I use a different skill instead of MasterControl?

Use the Veeva Vault QMS skill for Vault-based quality records, SAP QM for inspection lots and usage decisions, LabWare for LIMS lab results, and SAP MM for physical stock movements. MasterControl owns the routed quality decision, not lab values or stock postings.