Build and ship Amazon Ads creative assets end to end: generate compliant images (custom and lifestyle images, brand logos, display banners) and ad copy, then register them through the Amazon Ads MCP creative assets API. IF the user wants ad creative for Sponsored Brands, Sponsored Display, Amazon DSP, or eCommerce display — asks what size or file format an ad image must be, wants a lifestyle image for an ad, needs one image resized into square/wide/tall, asks whether text or a logo may appear in the creative, wants ad headline copy inside Amazon's limits, or has a rejected ad — OR wants to upload, register, version, search, or check the status of a creative asset (assetId, assetSubType, failedSpecChecks, PROCESSING, upload URL, creative asset library) — THEN invoke this skill. DO NOT invoke for retail product listing photos on a detail page (that is the amazon-product-image skill), or for campaign structure, bidding, budgets, or reporting.

Use whenever the user works with Amazon Marketing Cloud (AMC): SQL, workflows, audiences (rule-based or lookalike), playbooks (frequency, off-Amazon conversions, keyword clustering, lookalikes, programmatic audience framework, enhanced scoring, CLTV), custom attribution (first/last-touch, linear, position-based), first-party data uploads, ad-product filtering, AMC sandbox, cross-channel overlap, reach, frequency, or NTB analysis. Triggers: "AMC", "Amazon Marketing Cloud", "AMC SQL", "AMC workflow", "AMC audience", "AMC query", "AMC playbook", DSP audiences, attribution model, path-to-conversion, ad frequency, NTB, DOOH, Sponsored TV incremental reach, Sponsored Brands, Brand Store insights, Events Manager / CAPI, Audience Segment Insights, Amazon Your Garage, or SQL referencing tables like sponsored_ads_traffic, dsp_impressions, dsp_clicks, amazon_attributed_events_by_traffic_time, conversions_all, conversions_with_relevance.

Use when requests involve Amazon Ads unified/v1 reporting, CreateReport, reproducing a familiar Sponsored Products, Sponsored Brands, or Sponsored Display report on v1, v3-to-v1 report migration, report-field compatibility, or retrieving an asynchronous v1 report. Excludes AMC, legacy-v3 execution, live entity state, and campaign mutation.

Produce a Sponsored Brands (SB) campaign performance review from SB Campaigns Report data: portfolio summary, top and worst campaigns by efficiency, low-CTR creative signals, new-to-brand (NTB) analysis when present, placement or format splits if columns exist, and actionable recommendations. Use when users ask for Sponsored Brands audits, SB headline/video/store spotlight reviews, brand awareness efficiency, NTB share, SB CTR vs benchmarks, or SB campaign deep-dives. The agent must fetch and parse the report for the user’s environment — do not assume a global variable, fixed file path, or stable Amazon export schema; write loader and column-mapping code after inspecting the actual artifact.

Use when auditing Sponsored Products campaign portfolio structure through Amazon Ads MCP, including spend concentration, budget utilization, delivery gaps, low-engagement campaigns, targeting-type mix, or campaign naming hygiene.

Mine Sponsored Products search terms end-to-end via the Amazon Ads MCP: generate the SP Search Term report via allv1_AdsApiv1CreateReport using v1 dotted field IDs (searchTerm.value, metric.totalCost, metric.sales, budgetCurrency.value — not legacy Console headers), pre-flight validate with report_fields before CreateReport, filter adProduct.value SPONSORED_PRODUCTS, download CSV and parse with the v1 DictReader pattern, partition PAT ASINs in searchTerm.value, elicit brand markers and thresholds, segment into generic and branded gold tables, surface negatives, sufficiency-gated rising stars, and PAT stream. Never use metric.cost / metric.spend or legacy CSV column names. Trigger on: SP search term mining, search term gold, search term negatives, search term report, PAT vs keyword, brand vs generic split, rising stars, exact-match harvest, attribution window questions, or any variant of "find me wasted spend / scale-worthy keywords / branded defenders" via the Amazon Ads MCP.

Use when creating, editing, auditing, or troubleshooting Amazon listing images, including main images, alternate images, infographics, lifestyle imagery, size and scale, comparison, and what's-in-the-box images, fashion photography, multipacks, swatches, suppression, or image error 100239. Also use when planning which images a listing needs and in what order.

Calculate Amazon per-unit margin, break-even or target-margin price, affordable ad spend, and period P&L waterfalls. Use for ASIN profitability, unit economics, contribution or channel margin, landed cost, COGS, TACoS, fee and return impact, settlement reconciliation, or period-over-period margin movement. Excludes live repricing, return-reason diagnosis, and ad campaign reporting.

Create, run, and manage Amazon FBA inbound shipments with the SP-API Fulfillment Inbound v2024-03-20 workflow: build an inbound plan, pack, pick placement and carrier, confirm delivery windows, get labels, add tracking, check status, edit, or cancel. Pauses at every fee-charging or irreversible step for the seller's explicit choice and confirms each async operation before moving on. Use whenever a seller wants to send or ship inventory to Amazon or FBA, create or check an inbound plan or shipment, compare placement fees or partnered-carrier quotes, get FNSKU, box, or pallet labels or a bill of lading, set prep or label owners, enter tracking or PRO numbers, book an FC drop-off appointment, or cancel a shipment, even if they only say "send stock to Amazon". Do not use for replenishment forecasting or stockout risk, FBA inventory health, outbound or multi-channel orders, AWD, Vendor (1P) shipments, listings, or advertising.

Pre-flight compliance gate for Amazon Seller Central listings. Works out which Amazon listing requirements and regulatory rules (FDA, EPA, CPSC, FCC, FTC, required disclosures, GTIN, category gating) apply to a product, checks whether the seller is gated or ineligible on the ASIN, asks the seller once for the facts only they know, and returns a met/unmet checklist with a go or hold. Never writes a listing itself. Use whenever a seller asks "can I list this", "what do I need to sell X", "is this compliant", or about restricted or gated categories, certificates, or required labels, and before any listing edit that adds or changes a product claim (antimicrobial, FDA approved, organic, bamboo), ingredients, category, condition, or identifiers. Do not use for fixing listing errors, copy optimization, or buyability (amazon-sp-listing-optimizer), account-health or policy questions unrelated to a specific product, or legal advice.

Audit, optimize, fix, and edit Amazon Seller Central listings and A+ Content through an SP-API MCP server, for one listing or a whole catalog. Use whenever the user asks to review, audit, optimize, edit, fix, rewrite, or "look at" a listing — titles, item highlights, bullets, descriptions, search terms, browse nodes, attributes, images, variations, brand, A+ modules, or Brand Story. Also use to diagnose why a listing is suppressed, shows errors or warnings, isn't in search, or can't be bought (inactive, no offer), and for submission error codes such as 90057, 99001, 99010, or 97779. Trigger even when the user just names an ASIN or SKU and says "check it", "clean it up", or "what's wrong with it". Also use to regenerate listing images from existing product photos with an image model (Gemini/OpenAI), then validate and patch them. Do not use for "can I sell this product" compliance pre-checks (amazon-sp-listing-compliance), restock planning, or price-level strategy (amazon-sp-repricing).

Send order-scoped messages from an Amazon seller to a buyer with the SP-API Messaging API: check which message types an order allows, pick the right one, draft the text in the buyer's language within Amazon's content rules, attach invoices, warranties, or legally required documents, and send only after the seller approves an exact preview. Handles one order or a batch. Use whenever a seller wants to contact, notify, or message a buyer about an order: a delay or unexpected problem, confirming customization, delivery scheduling, an order question before shipping, a Home Services visit, a digital access key, or sending an invoice, warranty, or legal disclosure, even if they only say "let the customer know" or "email the buyer". Do not use for requesting reviews or seller feedback (Solicitations API), reading or replying to the buyer-seller inbox, marketing or promotional messages, A-to-z claims, returns, refunds, or Vendor (1P) orders.

Analyze Amazon FBA customer returns and seller-fulfilled return requests from Seller Central or SP-API exports. Use for return volume, high-return ASINs or SKUs, return-rate calculations, reason and disposition analysis, customer-comment themes, prior-period comparisons, damaged-versus-reimbursed review candidates, or client-ready Amazon returns reporting. Do not use for general Amazon Ads reporting, listing optimization without returns evidence, or financial refund totals without transaction data.

Design and run an Amazon repricing strategy from live SP-API data: compute per-SKU floors from real fee estimates, diagnose why the Featured Offer (Buy Box) is being lost, segment the catalog, write rules and guardrails, and produce a reviewable price change-set. IF the user is losing the Buy Box, asks what price to set, wants a repricing strategy or repricing rules, is in a price war or being undercut, needs a floor or break-even price, asks about Automate Pricing or a third-party repricer, or mentions ANY_OFFER_CHANGED, featured offer expected price, getCompetitivePricing, or Buy Box percentage — THEN invoke this skill. It proposes price changes and validates them before any write, and never applies prices unattended. DO NOT invoke for advertising bids or ad budgets (that is amazon-budget-pacing), listing copy or images, inventory forecasting, or returns analysis.

Use when analyzing Amazon Seller Central Sales & Traffic Business Reports or GET_SALES_AND_TRAFFIC_REPORT data for traffic, conversion, ordered sales, ASIN performance, daily trends, or optional Amazon Business B2B segmentation.

ASIN-level Amazon SQP / organic search diagnostics tied to search queries and n-gram themes: impression/click/purchase share, conversion index, funnel gaps, shipping and price friction, variant cannibalization, and lift-aware opportunity ranking. Use when users analyze Search Query Performance per ASIN, need SKU-specific SEO/PDP/ops recommendations from SQP, want RankScore-style prioritization, report QA badges for findings, stop-word hygiene for n-grams, or ASIN+query decision records alongside ngram-keyword-framework query-level rules. Not a substitute for Ads-only n-gram bid rules — use ngram-keyword-framework for sponsored search-term rollups.

Find FBA SKUs at risk of stocking out and whether inbound shipments will land in time. Reads live FBA inventory and FBA sales velocity, uses Amazon's own days-of-supply and recommended ship-in quantity and date when available, ranks SKUs by risk, and checks each at-risk SKU against its inbound shipments' arrival windows. Read-only. Use whenever a seller asks "am I going to run out", about stockout risk, days of cover or supply, FBA stock levels, restock or replenishment timing, what to send in next, or whether a shipment will arrive before a SKU sells out, even if they just ask "how's my inventory looking". Do not use for creating or managing inbound shipments (amazon-sp-fba-inbound), price changes or repricing (amazon-sp-repricing), stranded or aged-inventory fees, inventory ledger reconciliation, AWD, listings, or advertising.

Use when an AI agent needs to connect to a human's Kuudo account before calling any Kuudo capability — checking whether the session already exposes the Agent Auth MCP tools, registering a delegated connection with them, presenting the human's approval link, and reading account/organization data once approved. Covers the connect/approve/execute flow, approval timeouts and expiry, and the one-installation-per-human rule. Do not use to configure an MCP server, edit client configuration, or install packages — point the human to Kuudo's own connection guide instead. Do not use to design or modify the Agent Auth protocol itself, to request capabilities beyond read_account and read_organization, or to approve, deny, or sign in on the human's behalf.

Use at the start of Amazon commerce work involving Amazon Ads, Seller Central, or Vendor Central when Kuudo skills are installed.