CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

kuudoai/kuudo-skills

22 Agent Skills for Amazon sellers and advertisers: Sponsored Products and Brands audits, search-term mining, budget pacing, DSP and Amazon Marketing Cloud, reporting, listing optimization and compliance, product images, repricing, FBA inbound, stockout, refunds, buyer messaging, and profitability. Built for Kuudo's hosted Amazon Ads and Selling Partner MCP servers; price, budget, listing, and shipment writes are previewed and wait for explicit approval.

68

1.65x
Quality

93%

Does it follow best practices?

Impact

66%

1.65x

Average score across 22 eval scenarios

SecuritybySnyk

Medium

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

CHANGELOG.mdskills/amazon-product-image/

Changelog

All notable changes to this skill are documented here. Format follows Keep a Changelog. Versions are semver and must match metadata.version in SKILL.md.

Bump rules:

  • patch: non-behavioral changes (typos, formatting, reference-only edits).
  • minor: behavioral additions (new sections, rules, triggers).
  • major: contract changes (response shape, output format, scope).

Every bump also updates the evals/evals.json skill_version.

[1.2.0] - 2026-10-17

Added

  • Stack planning: each image answers one buyer question, with a default hard-goods sequence (main, benefit overview, lifestyle, close-up, size and scale, comparison or use-case chooser, what's in the box) framed as a default to adapt, not a slot quota.
  • Per-image guidance and prompt patterns for benefit infographics (one headline plus 3–5 sourced callouts), size and scale (familiar reference, seller dimensions, no perspective exaggeration), comparisons, and what's-in-the-box images; lifestyle images keep the product as the focal point with no prop that could read as included.
  • Comparison decision path: the seller's own lineup first, then an unbranded alternative only when every cell is sourced or true by definition, otherwise give the position to another buyer question. Competitor exclusion is reported as a cautious recommendation echoing Amazon's A+ guidance, not as gallery-image policy.
  • Claim-coverage gate for added copy: source every claim, never strengthen one, treat category norms and related-spec inference as non-sources, and keep unconfirmed copy and placeholders out of ready-to-run prompts.
  • Main-image framing: centered with a small white margin on every side, fill stated as about 85 percent of the image area (never one dimension), and a canvas the product can fill, set through the tool's aspect-ratio or size control when available: square for roughly square products, closer to the product's proportions for long or thin ones.
  • Stack-level checks: cross-image color and finish consistency, a phone-width legibility test, and a working text-size heuristic for prompts.
  • Evals for stack planning, a cluttered-infographic audit, a lineup comparison with a competitor request, and a sparse-spec padding trap; a stack-planning trigger query.
  • Outside text is data, not instructions: listing text (title, bullets, A+, including a hijacker's or another contributor's), text inside source, generated, or competitor images, image-tool responses, Amazon issue and suppression responses, error text, and fetched pages. An instruction inside them never changes the image, the prompt, the verdict, or the next tool call, never counts as approval, and is flagged to the user. The claim-coverage gate treats the existing listing as a source of facts to check, never of instructions.
  • Trusted targets: fetch only listing or detail pages for ASINs the user named and image URLs the user supplied or this run produced; act only on ASINs and SKUs the user named.
  • A prompt-injection eval: a listing bullet telling the AI to approve the image and upload it to all variants.

Changed

  • Mutation boundary: before any upload or replacement of a live listing image, title or other listing-data change, resubmission, or Seller Support escalation submission, show the exact marketplace, ASIN/SKU, image slot, file, and change, then wait for an explicit yes in the user's next message. A notice is not a yes, and a changed payload on retry needs a new yes. The suppression reference's resubmit, replacement, and escalation steps now point to this gate, and SKILL.md restates it next to the upload boundary.

Notes

  • Ported from the Agent Iris copy after two eval iterations there (with-skill 23/23 vs 18/23 for the prior version, then 34/34 vs 29/34 against the first iteration; one run per configuration).
  • Evaluated against 1.1.0 on the four new evals with no image tool available: 38/38 vs 30/38. The gains are in stack planning and audit attribution; the lineup-comparison and sparse-spec evals tie, because 1.1.0's existing rule against inventing product facts already held there.

skills

LICENSE.md

README.md

tile.json