Agent skill · affaan-m

operator-approval-loop

Operator approval contract with internal filing notices for agent-drafted outbound messages, hashed drafts, epoch-keyed decisions, durable delivery claims and receipts, and a pre-draft baseline gate. Use when an agent drafts messages to external counterparties and a human operator must approve, reject, or steer each send before it leaves.

What it needs

About 8k tokens when loaded.

What this skill does

Operator Approval Loop An agent that talks to external counterparties should never send on its own judgment and should keep the operator informed internally. This skill defines the contract: every outbound draft is filed as an obligation, an operator decides on the exact text, and a delivery ledger proves what went out. When to Use An agent drafts replies to customers, suppliers, investors, or partners in a shared channel, email, or chat, and a human must approve before send. You need an audit trail that links each sent message to the exact draft text, the operator who approved it, and the decision time. You have seen a stale approval release a rewritten draft, or two workers deliver the same approved message twice. Drafts keep re-asking counterparties for facts the ledger already holds. How It Works Objects Object Meaning --- --- Obligation One thing we owe a counterparty. Status moves drafted, then approved or rejected, then sent. Carries direction, counterparty, channel, and an updatedat epoch. Draft Sidecar row holding the exact draft text, a sha256 of that text, origin coordinates (platform, channel, thread, user), and priority (P0 to P3). One per obligation, replaced on re-file. Decision An operator's approve or reject, recorded with the operator id, a nonce, and the draft epoch it was made against. Approval snapshot Immutable text, hash, epoch and destination recorded by the already-authorized decision writer. Missing snapshots cannot grant dispatch. Claim Durable reservation with a random token and state; at most one active claim per obligation. Delivery Ledger row proving one send or notice for one (obligation, decision) pair. The reference schema is in references/approval-ledger.sql. Filing a draft 1. Clean inputs. Strip control characters, collapse whitespace in single-line fields, and enforce length caps (draft, summary, context, counterparty). Empty or oversized fields are refused, not truncated silently. 2. Run the baseline gate (below). …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills affaan-m/operator-approval-loop--e341fa

View the source on GitHub

Browse the @skills marketplace