Allergen Label Card

Problem

When listing food or personal-care products, sellers often need a clear allergen label card for detail pages, packaging inserts, or in-store notices. This is not a product image set, and it should not substitute for confirmed ingredient or allergen statements. The skill focuses on generating one readable card per SKU from seller-confirmed facts, without inventing missing ingredients, may contain lines, certifications, or serving claims.

How It Works

First, it collects the inputs that actually change the card: exact SKU, specification, seller-provided ingredient list or named allergens, approved contains or may contain lines, placement, and language. Photos may serve as visual references, not as a source of missing allergen facts. It then creates a free, inspectable card plan for each SKU, including printed lines, language, layout, canvas, and reference roles. Before any paid call, it reads current text_to_image pricing, confirms one call per SKU, submits beatra.images.generate through scripts/mcp_client.py, and polls beatra.tasks.get. Delivery includes an audit against the confirmed facts plus task ID, resolved model, and billing.net_charged_credits.

Boundaries

Use this for allergen disclosure and ingredient statement cards, not for product image sets, lifestyle images, detail shots, or main-image preflight; route those to their dedicated skills. If a fact is not confirmed, the skill leaves that line empty in the plan instead of inferring it from public posts, store catalogs, or uploaded photos. Local edits are treated as new paid work and require fresh confirmation and a new client_request_id.