nft launch qa gate

    1

    A final pre-flight quality gate for NFT projects covering contracts, metadata, art, and operational readiness.

    $14.99

    Secure checkout via Stripe

    30-day refund guarantee

    Converts to your local currency at checkout

    0 installsSecurity scanned

    Works with the AI tools you already use

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

    nft launch qa gate

    Example session with this skill installed

    Run a final launch QA on my NFT project. I have attached the smart contract, the metadata folder, and the frontend config file. We are launching 10k items at 0.05 ETH each on Base.

    • Read your context and instructions
    • Compiled the nft launch qa
    • Generated the document

    I have completed the audit of the contract source, metadata schema, and site configuration.

    NFT Launch Readiness Audit

    VERDICT: DO NOT SHIP
    Critical: 1 | High: 1 | Medium: 2 | Low: 1

    IDSeverityCategoryFindingImpactRecommendation
    QA-01CRITICALContractwithdraw() function lacks onlyOwner modifier.Anyone can drain the mint proceeds.Add onlyOwner or AccessControl check.
    QA-02HIGHMetadataToken IDs 450-500 reference missing CID in IPFS.50 NFTs will have broken images at reveal.Re-upload missing assets and update baseURI.
    QA-03MEDIUMFrontendChain ID is set to 84531 (Testnet) instead of 8453.Users will be prompted to switch to the wrong network.Update constants.ts to Base Mainnet ID.
    QA-04MEDIUMEconomicsMax mint per transaction is higher than total supply.Possible contract revert on large mint attempts.Set maxMint to a reasonable cap (e.g., 10).
    QA-05LOWOpsProject lacks an emergency pause playbook.Slow response during a front-end exploit.Document the setPaused(true) procedure.

    Launch blockers:

    1. Fix the withdraw function to prevent unauthorized fund drainage.
    2. Resolve the 50 missing metadata assets in the IPFS directory.
    3. Update the frontend configuration to point to Base Mainnet.

    Next steps

    1. Apply the access control fix to the smart contract and re-run the audit.
    2. Verify the IPFS hash for the complete 10k collection.
    3. Update the frontend environment variables for production.

    nft-launch-qa-gate.pdf

    PDF · document

    Generated

    Example file from a real run - the skill writes it into your workspace.

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

    What you get

    Audit smart contract mint logic and access controls before mainnet deploy.Validate consistency between IPFS metadata and on-chain URI references.Check frontend configuration for correct chain IDs and mint prices.Provide a structured SHIP or DO NOT SHIP verdict based on risk severity.

    About this skill

    The problem

    Launching an NFT collection with broken metadata, incorrect mint limits, or flawed withdrawal logic leads to permanent financial loss and community backlash. Developers often miss small configuration errors in the rush to deploy across multiple layers of the stack.

    What it does

    • Evaluates smart contract parameters including supply caps, mint limits, and access controls.
    • Validates metadata integrity across the entire collection to ensure no broken URIs or missing traits.
    • Checks website integration for correct chain IDs, RPC configurations, and wallet connection logic.
    • Assesses operational readiness including admin wallet setups and incident response plans.
    • Issues a formal SHIP or DO NOT SHIP verdict based on verified evidence rather than assumptions.

    Why this beats prompting it yourself

    General prompts often overlook the interdependencies between the contract, the IPFS metadata, and the frontend minting site. This skill enforces a structured severity framework and demands specific evidence for every claim, preventing the AI from hallucinating a "pass" on unchecked files.

    Use cases

    • Performing a final sanity check 24 hours before a mainnet deployment.
    • Auditing a client project to ensure all deliverables meet production standards.
    • Validating metadata consistency after generating a large-scale generative art collection.

    Known limitations

    Does not execute live blockchain transactions or perform deep gas optimization. It relies on provided artifacts like contract source code and metadata files.

    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 today

    • Passed all security checks, Safe to install

    Listedtoday

    Frequently Asked Questions