More screenshots

    Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIGitHub CopilotGitHub CopilotGemini CLIGemini CLI+20 more

    🧾 Custom Order Proof Checker

    1

    Check a custom order's approved proof against the actual local production file and source-linked later requests before reviewing the handoff.

    $5

    Secure checkout via Stripe

    30-day refund guarantee

    Converts to your local currency at checkout

    0 installsSecurity scanned
    🧾 Custom Order Proof Checker

    🧾 Custom Order Proof Checker

    Example session with this skill installed

    Check the supplied fictional C-104 fixture. It has explicit approval for proof P2/v2, a production file copied from P1/v1, and an undecided request to add 2027 after handoff. Compare the actual supplied files and preserve source references.

    • Read your context and instructions
    • Compiled the custom order proof

    Custom Order Proof Check

    Fictional fixture run; local source paths shortened for display.

    Result: MISMATCH

    MATCHED means supplied normalized bindings and checked bytes reconcile through the stated record coverage. Exact quotes are checked for presence, not interpreted. This does not establish visual equivalence, authenticity, legal approval, unseen messages, or actual production release.

    C-104 — MISMATCH

    Approved proof: P2; comparison: byte_identity.

    • MISMATCH / WRONG_PRODUCTION_PROOF: Production is bound to P1; latest approval is for P2. Sources: S3, S2, S4, S5.

    MISMATCH / PRODUCTION_BYTES_DIFFER: Production bytes differ from the approved proof; no evidenced export mapping was supplied. Sources: S3, S2, S4, S5.

    • MISMATCH / POST_HANDOFF_REQUEST: Change CH1 has no recorded seller decision: Add 2027 under names. Source: S6.

    The file table checks each current file against its manifest digest. A matching digest alone does not mean the production file matches the approved proof; use the order result and findings above.

    File rolePathActual SHA-256Manifest hash check
    proof P1proof-v1.svg1cdb69fac49d3bb27153b61c979cc80b46a5d7f0b19fca72f3aca6ae653b4142MATCHED
    proof P2proof-v2.svg63ec0d44c0ebfd267b92e605f3e2a0bbfeec7850072d28267259c64e7213de4fMATCHED
    productionproduction.svg1cdb69fac49d3bb27153b61c979cc80b46a5d7f0b19fca72f3aca6ae653b4142MATCHED

    Source record

    S1

    Source: evidence.txt — fictional export line 2 — quote_found

    2026-09-14 08:00 -05:00 Seller: Created C-104 proof-v1.svg, proof P1, version v1.

    S2

    Source: evidence.txt — fictional export line 3 — quote_found

    2026-09-14 09:00 -05:00 Seller: Created C-104 proof-v2.svg, proof P2, version v2, adding Sam.

    S3

    Source: evidence.txt — fictional export line 4 — quote_found

    2026-09-14 09:15 -05:00 Buyer replying to C-104 proof-v2.svg: I approve proof P2, version v2, Avery and Sam.

    S4

    Source: evidence.txt — fictional export line 5 — quote_found

    2026-09-14 09:20 -05:00 Seller check record: production.svg is copied from proof P1, version v1.

    S5

    Source: evidence.txt — fictional export line 6 — quote_found

    2026-09-14 09:25 -05:00 Seller handoff record: production.svg handed to the production queue for C-104.

    S6

    Source: evidence.txt — fictional export line 7 — quote_found

    2026-09-14 09:45 -05:00 Buyer: Please add 2027 under the names. Seller has not decided whether this later request can be accepted.

    S7

    Source: evidence.txt — fictional export line 8 — quote_found

    2026-09-14 10:00 -05:00 Fixture supplier: These selected C-104 records cover the example through 10:00 -05:00; there are no other records in this fictional example.

    Connects securely to your tools. The creator never sees your data.

    What you get

    Check that the production asset corresponds to the explicitly approved proofReview a later customer request without silently replacing approvalExpose ambiguous approval wording or missing production filesKeep a source-linked review beside the manual order record

    About this skill

    Custom Order Proof Checker helps an agent turn supplied order records and local files into a source-linked review. Its Python helper hashes the actual proof and production bytes, checks the normalized approval/version binding, and flags missing approval context, changed files, newer proofs and unresolved later requests. Each order returns MATCHED, MISMATCH or UNVERIFIED with an exception report and the cited source passages. A documented production export relation is kept separate from byte identity. The package includes the skill, a local Python helper, documented input schema and fictional examples. The agent still gathers and interprets the selected evidence. The helper does not extract PDFs, read inboxes, compare visual appearance, authenticate approval or release work to production.

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean 8 days ago

    • Passed all security checks, Safe to install

    Listed8 days ago

    What's inside

    Frequently Asked Questions