labware

Classifies LabWare LIMS operations by risk and gates consequential lab actions for human approval.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Operating a validated GxP laboratory information management system like LabWare LIMS carries serious compliance risk: authorizing a result is a 21 CFR Part 11 e-signature, an OOS result can be wrongly invalidated, and a batch can be released over an open failure. This Skill gives an AI agent the operator judgment to classify every LabWare action as read, reversible write, committing write, or destructive, and to stop consequential ones for human approval. ## Core Features & Use Cases - Risk-classified operation matrix: Maps sample login, result entry, review/authorization, batch disposition, COA issuance, and spec edits into read / reversible / committing / destructive classes with gating rules. - OOS/OOT and stability guidance: Covers the laboratory-phase OOS investigation, retest vs resample rules, stability study pulls, and the seams to the QMS (deviations, CAPA) and ERP (stock disposition). - Guardrails and recovery paths: Enforces segregation of duties, immutable audit-trail correct-forward patterns, and refusal rules for spec-gaming, testing into compliance, and releasing over an open OOS. - Use Case: An analyst asks the agent to release a batch while a dissolution result is flagged OOS; the Skill classifies the release as destructive, blocks it, and routes the work through the OOS investigation playbook instead. ## Quick Start Ask the agent to walk through entering, reviewing, and authorizing an assay result in LabWare and releasing the batch on spec.

Frequently Asked Questions about labware

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

FAQPage Schema
How do I safely authorize a result in LabWare LIMS?

Authorizing a result in LabWare is a 21 CFR Part 11 e-signature that locks the value and releases it to the COA and batch disposition. The Skill requires a second person to review and authorize, blocks authorization over an open OOS or missing required result, and treats it as a committing action needing human approval.

What should I do when a LabWare result is flagged OOS?

An OOS flag is a stop for investigation, not a rejected batch or a value to overwrite. Run the LabWare laboratory-phase investigation to check analyst, instrument, and prep; invalidation requires a documented assignable cause, and retest or resample only follows the OOS protocol.

Does this Skill handle SAP QM or QMS deviations?

No, it explicitly defers those. SAP QM inspection lots and stock postings belong to the sap-qm and sap-mm skills, while deviations, root-cause investigations, and CAPA belong to a QMS skill such as veeva-vault-qms. LabWare owns only the lab-phase evidence.

Can a batch be released in LabWare with an open OOS?

No. Batch disposition is the AND of every contributing sample: all results must be authorized, in-spec, with no open OOS and no out-of-calibration instrument behind a value. Releasing over an open failure is classified as destructive and refused.

Why is editing a spec limit in LabWare treated as destructive?

A spec limit or rounding rule is master data that re-defines pass/fail for future and open samples. Editing it to pass a failing result is spec-gaming, and any production config change is a validated computer-system change requiring change control, not an operator edit.