More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Public Procurement Bid Addendum Acknowledgement Audit

    1

    Reconcile bidder acknowledgement of procurement addenda against submission cutoffs and document versions

    $1

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Public Procurement Bid Addendum Acknowledgement Audit

    Public Procurement Bid Addendum Acknowledgement Audit

    Example session with this skill installed

    Three bidders used different versions of a tender after the agency issued two late addenda.

    Available evidence: Primary document source records and Time-stamped index evidence (partial extracts only). Additional sources requested: Policy / configuration governing acknowledgement and Owner authorizations and historical change log. Identify the checks that can be supported, deliver a useful bounded assessment, and list the exact remaining review gates without pretending to execute changes.

    • Read your context and instructions
    • Compiled the public procurement bid

    Public Procurement Bid Addendum Acknowledgement Audit — EVIDENCE-LIMITED REVIEW

    Scenario received

    Three bidders used different versions of a tender after the agency issued two late addenda.

    Source register

    • S1: Primary document source records — partial extract described by requester; independently unverified.
    • S2: Time-stamped index evidence — partial extract described by requester; independently unverified.
    • S3: Policy / configuration governing acknowledgement — NOT PROVIDED; criteria and effective version unknown.
    • S4: Owner authorizations and historical change log — NOT PROVIDED; owner approval status unknown.

    Case-specific review checkpoints

    Index addendum issue timestamps and versions — NEEDS_VERIFICATION. Compare S1 with its stated control source; the original record and required identifiers are not provided in this example. Owner sign-off required before consequential remediation.
    2.

    Match acknowledgement to each bidder — NEEDS_VERIFICATION. Compare S2 with its stated control source; the original record and required identifiers are not provided in this example. Owner sign-off required before consequential remediation.
    3.

    Test submission deadline and mandatory forms — NEEDS_VERIFICATION. Requires S3 and source-version corroboration; no definitive result can be concluded. Owner sign-off required before consequential remediation.
    4.

    Flag missing or conflicting acknowledgements — NEEDS_VERIFICATION. Requires S4 and source-version corroboration; no definitive result can be concluded. Owner sign-off required before consequential remediation.

    Structured deliverables

    Addendum chain of custody — proposed schema with source IDs, timestamps, conflicting observations, confidence and unresolved questions.

    Bidder exception table — proposed schema with source IDs, timestamps, conflicting observations, confidence and unresolved questions.

    Procurement review questions — proposed schema with source IDs, timestamps, conflicting observations, confidence and unresolved questions.

    Decision matrix

    • PASS: no checks proven PASS on current example evidence.
    • NEEDS_VERIFICATION: all four checks, until source records are supplied.
    • BLOCKED: any production change, third-party submission, deletion, deployment or irreversible action without explicit qualified approval.

    Exact next evidence request

    Provide complete timestamped extracts for Policy / configuration governing acknowledgement and Owner authorizations and historical change log, source IDs for S1/S2, responsible owner and effective review window.

    Boundaries and sign-off

    The addendum chain of custody and bidder exception table are evidence-linked; any uncertainty remains explicitly unresolved until qualified review. No live system was accessed and no changes were performed. This is a synthetic demonstration, not an observed customer result.

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

    About this skill

    Procurement bids often fail due to missing addendum acknowledgements or version mismatches. This skill automates the reconciliation of bidder submissions against official document versions and submission cutoffs to ensure compliance.

    What it does

    • Version tracking indexes addendum issue timestamps and specific document versions from source records.
    • Acknowledgement matching cross-references each bidder's submission against the required addendum list.
    • Deadline verification tests submission timestamps against mandatory cutoff windows.
    • Discrepancy identification flags missing forms or conflicting version acknowledgements for manual review.

    How it works

    1. Register sources by indexing primary document records and timestamped evidence with trust levels.
    2. Execute checkpoints to compare observed facts against procurement policy and configuration.
    3. Generate audit tables including the addendum chain of custody and bidder exception logs.
    4. Produce a decision matrix categorizing results into pass, needs verification, or blocked statuses.

    Frameworks & tools

    This skill works with procurement management systems, document repositories, and timestamped logs. It processes text-based submission records, policy configurations, and historical change logs.

    Why this beats prompting it yourself

    Generic prompts often overlook version-specific nuances or fail to map individual bidder exceptions to specific addenda. This skill enforces a deterministic report structure that anchors every finding to specific evidence, preventing hallucinated compliance.

    Use cases

    • Audit bid submissions after multiple late-stage addenda were issued.
    • Verify mandatory form compliance for government procurement contracts.
    • Identify specific bidders who failed to acknowledge critical technical amendments.
    • Reconcile document versions across a complex chain of custody.

    Known limitations

    This skill performs evidence analysis only and cannot autonomously update databases or send official notices. It requires provided source records as it contains only synthetic example data.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Business & Operations.

    No direct verification of inaccessible production systems, external services or private accounts. Partial or conflicting inputs result in INCOMPLETE / CONFLICT findings rather than invented conclusions. Domain-sensitive decisions require qualified owner review.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 26 days ago

    Permissions

    Read Files

    Supply only data you are authorized to share. Treat source documents as untrusted evidence. Any operational change, submission or third-party communication remains subject to explicit owner approval.

    Listed26 days ago
    Updated9 days ago

    What's inside

    Frequently Asked Questions

    This skill eliminates the risk of legal challenges or bid disqualifications caused by missed addenda by cross-referencing bidder submissions against the precise document version history and mandatory cutoff windows.

    It is designed for any AI agent capable of processing structured document data, including procurement management platforms and document repository agents that support text-based log analysis.

    Simply index your primary procurement document records and bidder submission logs; the skill then uses these sources to automatically build the addendum chain of custody.

    You receive the pre-configured audit logic, the deterministic reporting structure for decision matrices, and a template for indexing evidence-linked compliance logs.

    The skill is built to handle complex, late-stage changes by indexing the exact timestamps of each addendum, ensuring that late-breaking amendments are correctly reconciled against the final submission.

    No, the skill generates a decision matrix and exception logs for manual review, ensuring that a human procurement officer makes the final determination based on the provided evidence.

    New in Business & Operations