Higgsfield Marketplace Cards
Generate compliant marketplace main images, secondary product shots, and A+ style modules via the Higgsfield CLI for listing-ready visuals.
Overview
Higgsfield Marketplace Cards is an agent skill most often used in Launch (also Grow content) that produces marketplace-compliant product image sets through the Higgsfield CLI.
Install
npx skills add https://github.com/higgsfield-ai/skills --skill higgsfield-marketplace-cardsWhat is this skill?
- Routes intent to `higgsfield marketplace-cards create` with backend-owned compliance references and private prompt templ
- Supports scopes: main, product-images, aplus, and full-set via --scope for staged listing packs.
- Creates nano_banana_2 jobs and returns result URLs after the backend enhancer step.
- Bootstrap: official CLI install via curl installer and `higgsfield auth login` when account status fails.
- Explicitly excludes generic brand photoshoots, video/UGC ads, and Soul Character training—points to sibling Higgsfield s
- Skill version 0.3.0 with --scope main|product-images|aplus|full-set
- Job model nano_banana_2 with backend enhancer before image creation
Adoption & trust: 35.4k installs on skills.sh; 378 GitHub stars; 1/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need sales-ready marketplace listing images and A+ modules but lack compliant templates and a repeatable CLI workflow from your agent.
Who is it for?
Indie ecommerce operators listing on marketplaces who already use or can install the Higgsfield CLI and want agent-driven listing visuals.
Skip if: Generic brand product photography without listing context, video or UGC ad generation, or Soul Character training—use the dedicated Higgsfield skills instead.
When should I use this skill?
User asks for marketplace listing images, product detail cards, secondary images, infographics, lifestyle listing shots, A+ style content, marketplace image sets, or sales-ready product visuals.
What do I get? / Deliverables
You receive scoped marketplace image job URLs from Higgsfield after auth and CLI create, aligned to main, gallery, A+, or full-set listing needs.
- Higgsfield marketplace-cards jobs scoped to main, product-images, aplus, or full-set
- Printed result URLs for generated listing and A+ style visuals
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Launch → ASO because outputs are marketplace listing and conversion assets, not generic brand shoots. ASO subphase covers store-compliant imagery, infographics, and A+ modules that directly affect listing click-through and conversion.
Where it fits
Produce a compliant main image and full-set gallery before submitting a new SKU to a marketplace.
Regenerate A+ modules for holiday positioning without redoing non-listing brand photography.
Mock listing visuals to test positioning before committing inventory to a channel.
How it compares
CLI intent router with private compliance templates—not a local image editor and not interchangeable with higgsfield-product-photoshoot for non-marketplace shoots.
Common Questions / FAQ
Who is higgsfield-marketplace-cards for?
Solo builders and sellers who want marketplace main images, secondary shots, infographics, and A+ style modules generated through Higgsfield from an AI coding agent.
When should I use higgsfield-marketplace-cards?
At Launch when preparing store listings and ASO assets, and in Grow → Content when refreshing seasonal secondary images or A+ modules for existing SKUs.
Is higgsfield-marketplace-cards safe to install?
It allows Bash to install and run the Higgsfield CLI; review the Security Audits panel on this Prism page and only authenticate with accounts and API access you trust.
SKILL.md
READMESKILL.md - Higgsfield Marketplace Cards
# Marketplace Cards Create marketplace-ready product visuals with `higgsfield marketplace-cards create`. The CLI first calls the backend enhancer, where marketplace rules and templates are kept private, then creates `nano_banana_2` jobs and prints result URLs. ## Bootstrap 1. If `higgsfield` is not on `$PATH`, install it by running the official installer with Bash: `curl -fsSL https://raw.githubusercontent.com/higgsfield-ai/cli/main/install.sh | sh`. 2. If `higgsfield account status` fails with authentication errors, ask the user to run `higgsfield auth login`. ## UX Rules 1. Respond in the user's language. 2. Ask at most one concise confirmation question before running. 3. Prefer a product image. If the user provides only text or a URL, proceed only when the product details are clear. 4. Do not write final image-generation prompts yourself. Backend enhancement owns that. 5. Final answer should contain only the ready image URLs and short labels. ## Scope Selection Use `--scope` when the user asks for a common bundle: | Scope | Creates | |---|---| | `main` | 1 marketplace main image | | `product-images` | main image + 5 secondary images | | `aplus` | main image + 7 A+ modules | | `full-set` | main image + 5 secondary images + 7 A+ modules | Use repeated `--asset` only for custom subsets: - `main_image` - `infographic` - `multi_angle` - `detail_shot` - `lifestyle` - `whats_in_box` - `aplus_hero_banner` - `aplus_pain_points` - `aplus_features` - `aplus_ingredients` - `aplus_efficacy` - `aplus_how_to_use` - `aplus_endorsement` ## Command Build and run one `higgsfield marketplace-cards create` command from the user's request. For common bundles, use `--scope <main|product-images|aplus|full-set>`, `--prompt "<short product and listing intent>"`, optional repeated `--image <path-or-upload-id>`, and optional context flags: `--product_context`, `--brand_context`, `--category`, `--visual_style`. Examples to mirror when choosing arguments: - Product images: `higgsfield marketplace-cards create --scope product-images --prompt "sparkling peach lemonade can for marketplace listing" --image ./can.png --category "beverage"` - Full set: `higgsfield marketplace-cards create --scope full-set --prompt "premium skincare serum, clean clinical marketplace visual system" --image ./serum.jpg --brand_context "minimal white and sage palette"` - Custom subset: repeat `--asset`, for example `--asset main_image --asset infographic --asset lifestyle`. - Existing completed main image job: use `--main-job <completed_main_job_id>` with the requested secondary or A+ `--asset` values. ## Delivery Print URLs with labels: ```text Marketplace cards ready: - Main image: https://... - Infographic: https://... - Lifestyle: https://... ``` Avoid JSON, job IDs, internal model names, or enhanced prompt text unless the user explicitly asks.