gep

Classifies GEP SMART source-to-pay operations into read, write, and destructive gates for safe execution.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Operating GEP SMART without judgment risks committing money, publishing sourcing events to suppliers, or overriding fraud flags unintentionally. This Skill gives an AI agent the operator judgment to classify every GEP action by consequence and pause consequential ones for human approval. ## Core Features & Use Cases - Action Classification: Maps GEP operations across sourcing, contracts, requisitions, POs, receipts, and invoices into read, reversible write, committing write, and destructive tiers with matching gates. - AI Automation Guardrails: Treats GEP MINERVA / QUANTUM Intelligence agent outputs as gated input, not authority, and flags touchless matching and config changes as control-surface decisions. - Edge States & Recovery: Covers exception tiers, sealed-bid envelopes, blanket releases, credit memos, supplier holds, and prohibited circumvention patterns with recovery paths. - Use Case: When asked to release an out-of-tolerance invoice exception in GEP, the agent recognizes it as destructive, routes it to a named approver, and re-reads the match state instead of auto-clearing it. ## Quick Start Ask the agent to classify and safely process a GEP SMART task such as approving a requisition or resolving an invoice match exception.

Frequently Asked Questions about gep

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

FAQPage Schema
How do I safely approve an invoice in GEP SMART?

Approving or releasing an invoice is a committing write because it creates the payable and authorizes payment. Re-read the match status, tolerances, and any fraud flags first, and treat out-of-tolerance exceptions as destructive overrides requiring a named approver.

What is the difference between a GEP sourcing event, award, contract, and PO?

They are four separate governed steps, each with its own workflow. Publishing an event is outbound, awarding commits the outcome and notifies suppliers, and realizing it as a contract or PO is a further committing step that must not be collapsed or skipped.

Can GEP MINERVA AI agent recommendations be treated as approvals?

No. A MINERVA / QUANTUM Intelligence recommendation is read-class analysis, not authority. Acting on it inherits the class of the underlying action, so accepting a buying recommendation commits the requisition and must be gated accordingly.

When should I not use this GEP SMART skill?

Do not apply it to other S2P suites like SAP Ariba, Coupa, JAGGAER, or Ivalua, to GEP NEXXE supply-chain or GEP GREEN sustainability products, or to ERP-side posting and payment in SAP FI/MM, which belong to their own skills.

Why is changing GEP QUANTUM configuration considered destructive?

Editing a workflow route, tolerance band, validation rule, AI touchless setting, role, or ERP mapping re-gates every future transaction fleet-wide. It requires a named approver plus a sample re-check of what the change now lets through.

How are GEP invoice match exceptions tiered?

An auto-cleared within-tolerance exception is a system action needing no gate, a non-blocking manual acknowledgment is committing, and an out-of-tolerance override or hold release is destructive because it authorizes payment despite the mismatch.