agentleFS
qwwiwiqwwiwi/agentos-skills-public/skills/higgsfield-marketplace-cards/SKILL.md

higgsfield-marketplace-cards

Skill4 starsChanged 4 months agoMITView on GitHub

Generate marketplace product image cards through Higgsfield: compliant main image, secondary product images, and A+ style content modules. Use when the user asks for marketplace listing images, product detail cards, secondary product images, product infographics, lifestyle listing shots, A+ style content, marketplace image sets, or sales-ready product visuals. Backend owns marketplace compliance references and prompt templates; this skill only routes user intent to the CLI. NOT for generic brand product photography without marketplace/listing context (use higgsfield-product-photoshoot), video generation or UGC ads (use higgsfield-generate), or Soul Character training (use higgsfield-soul-id).

  • Pipes a download into a shell

15 other projects use a version of this, 7 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use animation-vocabulary, review-animations and 2 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • boraoztuncSkill

    animation-vocabulary

    Reverse-lookup glossary that turns a vague description of a web animation or motion effect into its exact term ("the bouncy thing when a popover opens" → Pop in; "the iOS rubber-band scroll" → Rubber-banding). Use when the user asks "what's it called when…", or describes a motion effect without knowing its name and wants the right word to prompt an AI or designer with. For naming an effect, not designing or building one.

    Also in 3 projects that use this

  • arkanSkill

    review-animations

    Reviews animation and motion code against a high craft bar derived from Emil Kowalski's design engineering philosophy. Default to flagging; approval is earned.

    Also in 3 projects that use this

  • VercelSkill

    emil-design-eng

    This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.

    Also in 3 projects that use this

  • AnasX7Skill

    design-taste-frontend

    Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

9 rules. 4 are common, 0 are distinctive, and 5 are very specific to this project.

  • 4

    Common

    Most of the 8 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Create marketplace-ready product visuals with higgsfield marketplace-cards create.

    line 21
  2. Very specific:

    If higgsfield is not on $PATH, install it by running the official installer with Bash: curl -fsSL …

    line 26
  3. Very specific:

    If higgsfield account status fails with authentication errors, ask the user to run higgsfield auth login.

    line 27
  4. Common:

    Ask at most one concise confirmation question before running.

    line 32
  5. Common:

    Prefer a product image. If the user provides only text or a URL, proceed only when the product details are clear.

    line 33
  6. Common:

    Do not write final image-generation prompts yourself.

    line 34
  7. Very specific:

    Use --scope when the user asks for a common bundle:

    line 39
  8. Very specific:

    Use repeated --asset only for custom subsets:

    line 48
  9. Common:

    Avoid JSON, job IDs, internal model names, or enhanced prompt text unless the user explicitly asks.

    line 88

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

ScopeCreates
main1 marketplace main image
product-imagesmain image + 5 secondary images
aplusmain image + 7 A+ modules
full-setmain 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:

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.