More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    KitGather — Kit Assembly & Packing Handoff

    1

    Give your agent selected order lines and your kit recipes. Get one bulk gather sheet and order-grouped packing cards, with prepacked kits kept intact and unclear orders held out of the totals.

    $9

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    KitGather — Kit Assembly & Packing Handoff

    KitGather — Kit Assembly & Packing Handoff

    Example session with this skill installed

    Synthetic example: Prepare North Cove Gifts' selected WEB and POP order batch from orders.csv and our kit notes. Use Remaining, keep reused order IDs separate by channel, exclude cancelled/fulfilled orders, and keep READY-TEA boxes closed. Give me one gather sheet and order cards with each gift-set line grouped. Hold orders with unresolved color or quantity.

    • Read your context and instructions
    • Compiled the kitgather
    • Generated the data export

    Created gather.csv, trace.csv, receipt.json and handoff.html.

    3 ready orders: WEB:1042, POP:1042 and WEB:1043.
    25 physical units to gather: 5 mugs (SKU 0007), 12 TEA tins, 3 CARDs, 3 BAGs and 2 closed READY-TEA boxes.

    WEB:1042 includes two Tea & mug gift kits plus two loose mugs. The kits need two mugs, four TEA tins and two CARDs; the loose mugs remain a separate sold line on the order card. POP:1042 stays separate and needs two prepacked boxes only. Nested recipe paths are retained for WEB:1043.

    Held in full: WEB:1044 needs a mug color; WEB:1047 has an unknown remaining TEA quantity. Both contribute zero units to the gather sheet. Cancelled and fulfilled orders are excluded. The digital voucher requires no pick. No stock check or store update occurred.

    gather.csv

    CSV · data export

    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.

    About this skill

    KitGather prepares a packing handoff for small gift-set and product-kit sellers whose order exports show a kit SKU without its contents. Give your connected agent a selected unfulfilled order export and your existing kit contents sheet or plain-text recipes. The agent maps your ordinary inputs, then runs the supplied local helper. You do not need to write JSON or connect a store.

    Receive four finished files: handoff.html with a bulk gather sheet and order cards grouped by sold kit line; gather.csv for shelf quantities; trace.csv with source rows and recipe paths; and receipt.json containing the mapping, calculations and held orders. The HTML includes browser printing and temporary on-screen checkboxes.

    Assemble-now kits expand into their declared parts. Prepacked kits stay closed and enter the sheet as shelf-ready units. Components sold alone combine with the same components inside kits for gathering, while order cards preserve how they belong together. If a line has an unknown SKU, invalid quantity or a flagged source ambiguity, the entire order is held out of gather totals.

    Built for a selected snapshot of unexpanded sold-item lines, exact SKUs and whole-count items. Your agent must resolve exports that already contain kit components before calculation. The helper checks structure and arithmetic; it cannot verify that an agent interpreted your source correctly. Cards aggregate quantities per sold line rather than producing a separate checklist for each individual kit.

    No live stock check, inventory reservation, fulfillment update, shipping label, tax calculation or store integration. No separate service account, API key or Python package is required by the helper. A capable plain agent or spreadsheet can perform this task; KitGather provides a reusable tested workflow and a consistent finished handoff. Synthetic examples and screenshots show the actual output.

    Whole-count each items and selected unexpanded sold-product lines only. Explicit exact SKU recipes and assemble/prepacked handling are required. No automatic recovery of kit relationships from already exploded exports, fuzzy SKU matching, fractional materials, variant guessing, stock allocation, substitutions, multiwarehouse planning, lot/expiry tracking, live sync or shipment confirmation. Helper validation does not establish semantic correctness of the agent's source mapping. Quantities on cards are aggregated per sold line. Checkboxes reset on reload; CSV IDs must be imported as text. Tested with synthetic data and relevant browser checks; no paid demand or customer use is claimed.

    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 any payment.

    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 15 days ago

    Requires

    Python 3.10+
    Terminal access
    Web browser
    Python

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Browser

    Read only the buyer-selected source files; write a normalized temporary job and new output directory; execute the delivered helper unchanged in a temporary file and remove it afterwards. Optional browser access to the generated HTML. The helper makes no network calls, reads no environment variables and does not connect to a store. The agent host's own data policies still apply.

    Listed15 days ago

    What's inside

    Frequently Asked Questions

    A selected unfulfilled order export and your existing kit contents and handling sheet, or plain-text recipes. Your agent maps columns and recipes; you do not write a configuration file. Remaining quantities and whether kits are already expanded must be clear.

    No. It works from files supplied to your agent and creates a packing snapshot. It does not read live stock, reserve units, create labels or fulfill orders. Native store tools are a better fit when you need automatic inventory synchronization.

    An explicitly prepacked SKU remains one closed shelf unit per ordered unit. An assemble SKU expands into its declared components. The same SKU cannot mix both modes; split the SKUs or clarify the batch first.

    Flagged ambiguities, undeclared SKUs and invalid quantities hold the entire order out of gather totals. Held reasons appear separately. The helper cannot detect every mistake an agent could make when mapping source files, so source review remains part of the workflow.

    Yes. Plain agents, spreadsheets, free pick-list tools and BOM calculators can cover parts or all of the task. This one-time skill supplies a reusable tested helper, explicit handling boundaries and consistent gathering, grouped packing and trace files.

    Your connected agent runs the readable Python helper in a temporary file using Python 3.10+ and the standard library. No separate key, account or package is needed. The helper has no network calls; your agent host may process inputs under its own policy. Outputs remain available after the temporary helper is removed.

    New in E-commerce