agentleFS
qwwiwiqwwiwi/agentos-skills-public/skills/higgsfield-generate/SKILL.md

higgsfield-generate

Skill4 starsChanged 4 months agoMITView on GitHub

Generate images/videos via Higgsfield AI. Models: GPT Image 2, Nano Banana 2/Pro, Soul V2/Cinema/Cast/Location, Seedance 2.0, Veo 3.1, Kling 3.0, Flux 2, Z Image, Hailuo; plus Marketing Studio ads with avatars/products/hooks/settings. Use when: "generate an image", "make a picture", "make a video", "animate this photo", "image-to-video", "edit/stylize/remix this image", "produce a clip", "create an ad", "make a UGC video", "product demo", "unboxing", "TV spot", "brand video", "presenter video", "import product from URL", "create avatar for ad". Supports text-to-image, image-to-image, image-to-video, reference-based generation, and Marketing Studio. Auto-detects upload IDs vs previous job IDs. Chain with higgsfield-soul-id when the user wants face/identity consistency. NOT for: training Soul Character (use higgsfield-soul-id), product photoshoots (use higgsfield-product-photoshoot), marketplace listing cards (use higgsfield-marketplace-cards), text/chat/TTS tasks.

  • Pipes a download into a shell

20 other projects use a version of this, 19 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use higgsfield-websites, higgsfield-brandkit and 5 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.
  • higgsfield-aiSkill

    higgsfield-websites

    Build, edit, and deploy full-stack websites, apps and games via the Higgsfield CLI (`higgsfield website …`). Each is a React 19 + TanStack Start SSR app in one Cloudflare Worker (D1/R2/KV/DO/Containers). THREE product types, picked via `--type` on create: `website` (standalone, no Higgsfield integration — references/website-flow.md), `app` (Sign in with Higgsfield + fnf SDK, Quanta — references/app-flow.md), `game` (realtime multiplayer rooms — references/game-flow.md). Routes to the right flow; each carries its own rules and deploy/publish gates. Use when: "build me a website", "make a landing page", "create a web app", "build a SaaS dashboard / portfolio", "make me a game", "deploy this site", "publish". Also owns GAME ART: "make a spritesheet", "tileable texture", "animate a 3D character", game music/SFX — see the game-* references. NOT for: single image/video/audio generation (higgsfield-generate), product photos (higgsfield-product-photoshoot), marketplace cards (higgsfield-marketplace-cards).

    Also in 5 projects that use this

  • higgsfield-aiSkill

    higgsfield-brandkit

    Create and extend complete visual brand systems through the Higgsfield CLI and bundled deterministic local tooling: palettes, SVG logo marks, typography, mockups, social graphics, packaging, signage, merchandise, posters, presentation decks, and editable PPTX/PDF brandbooks. Preserves official supplied assets, persists approvals locally, and regenerates only dependent outputs. Use when: "create a brand kit", "make a visual identity", "design a logo and brandbook", "apply this logo to branded assets", "make packaging or signage", or "extend our existing branding". Chain with higgsfield-generate for general image production and Marketing Studio brand-kits when importing website metadata for ads. NOT for unbranded image generation (use higgsfield-generate), product catalog photography (use higgsfield-product-photoshoot), website implementation (use higgsfield-websites), or native Figma/Canva/PSD/AI delivery.

    Also in 4 projects that use this

  • attentiondotnetSkill

    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

  • +2 more from higgsfield-ai

The file

We split this skill into the rules it gives an agent

12 rules. 4 are common, 3 are distinctive, and 5 are very specific to this project.

  • 4

    Common

    Most of the 19 edited versions we read keep these.

  • 3

    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. Distinctive:

    Before any other command, make sure the CLI is installed and authenticated:

    line 31
  2. Very specific:

    If higgsfield is not on $PATH, install it:

    line 33
  3. Very specific:

    If higgsfield account status fails with Session expired / Not authenticated, ask the user to run higgsfield auth login (interactive, opens …

    line 37
  4. Common:

    No internal jargon. Don't narrate "calling higgsfield cost", "polling job".

    line 44
  5. Common:

    Don't batch-ask. Pick a sane default model and ask one thing at a time only if genuinely missing.

    line 46
  6. Distinctive:

    Don't pre-estimate cost. Just submit unless the user asks.

    line 47
  7. Common:

    All advertising / commercial / branded ad video → Marketing Studio (see Marketing Studio below)

    line 68
  8. Very specific:

    Validate quickly: If unsure of params, run higgsfield model get <jst> --json once and pass only what's needed.

    line 79
  9. Common:

    Use these exact list commands when the user asks what already exists:

    line 129
  10. Very specific:

    Default: higgsfield marketing-studio avatars list and pick a preset matching the brand voice.

    line 155
  11. Very specific:

    Add --hook_id <hook_id> and/or --setting_id <setting_id> when a setup hook/setting was selected.

    line 180
  12. Distinctive:

    When the user gives a product URL and wants a marketing video in one go:

    line 187

“Common” is measured: kept by at least 6 in 10 of the 19 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

Higgsfield Generate

Submit jobs to any Higgsfield model. Wraps the higgsfield CLI. Covers generic image/video gen and Marketing Studio (branded ads, avatars, products, hooks, settings).

Step 0 — Bootstrap

Before any other command, make sure the CLI is installed and authenticated:

  1. If higgsfield is not on $PATH, install it:
    curl -fsSL https://raw.githubusercontent.com/higgsfield-ai/cli/main/install.sh | sh
  2. If higgsfield account status fails with Session expired / Not authenticated, ask the user to run higgsfield auth login (interactive, opens a browser) and wait for them to confirm before continuing.

Skip both checks if higgsfield account status already prints account info.

UX Rules

  1. Be concise. No raw IDs, no JSON dumps in chat. Print result URL when ready.
  2. No internal jargon. Don't narrate "calling higgsfield cost", "polling job".
  3. Detect the user's language from the first message and reply in it. Technical args (--aspect_ratio 16:9) stay English.
  4. Don't batch-ask. Pick a sane default model and ask one thing at a time only if genuinely missing.
  5. Don't pre-estimate cost. Just submit unless the user asks.
  6. Pass --wait to generate create so the command blocks until done and prints the result URL itself. Avoid the two-step create → wait pattern.

Workflow — generic generation

  1. Pick a model. Practical defaults from production use:

    Image:

    • Brand product visual (Pinterest pin, lifestyle, hero banner, ad pack, virtual try-on) → use higgsfield-product-photoshoot instead. NOT this skill.
    • Branded ad image with avatar + product (Marketing Studio shape) → Marketing Studio Image (see Marketing Studio below)
    • Aesthetic UGC / fashion editorial / lifestyle character → Soul 2.0
    • Cinematic still frame → Soul Cinema
    • Highly characterful creative persona (text-only, distinctive) → Soul Cast
    • Locations / environments / no-people scenes → Soul Location (best in class)
    • Vector illustrations OR face edit + complex scene swap → Seedream 4.5
    • Soul Character (reference id from higgsfield-soul-id) → Soul 2.0 for stills, Soul Cinema for cinematic
    • Fast and cheap iteration → Z Image
    • Character or cartoon-style work → Nano Banana 2; step up to Nano Banana Pro on hard cases
    • Default for everything else → GPT Image 2. Graphic design, UI, banners, typography, and high-fidelity general generation.

    Video:

    • All advertising / commercial / branded ad video → Marketing Studio (see Marketing Studio below)
    • Default all-purpose serious video (multi-shot, consistent identity, motion-heavy) → Seedance 2.0. SOTA.
    • Single-plane scene without strong dynamics, cheaper than Seedance 2.0 → Kling 3.0
    • Cheap clean shot without cuts → Seedance 1.5 Pro
    • Cinema-grade highest fidelity → Cinema Studio Video 3.0
    • Cheap with strong physics, no audio needed → Minimax Hailuo
    • Fast batch / volume → Veo 3.1 Lite

    For the actual --model ID to pass to higgsfield generate create, run higgsfield model list --json | jq to map display names to IDs. See references/model-catalog.md for the full table.

  2. Pass media inputs straight to flags. Media flags accept a local file path or a UUID. CLI auto-uploads paths and auto-detects job vs upload for UUIDs. No need to pre-upload. Each model declares accepted roles (image, start_image, end_image, video, audio) — see references/media-inputs.md.
  3. Validate quickly. If unsure of params, run higgsfield model get <jst> --json once and pass only what's needed. Use schema defaults otherwise. The server returns adjustments for non-fatal coercions (e.g. aspect_ratio=99:99 → closest match) and a structured error for invalid declared-param values.
  4. Submit and wait in one shot. higgsfield generate create <jst> --prompt "..." [media flags] [param flags] --wait. Blocks until terminal status and prints the result URL on stdout. Tunables: --wait-timeout 20m (default 10m), --wait-interval 5s (default 3s).
  5. Deliver. Send the URL plus a one-line summary (model, duration if video).

To inspect or rerun later, higgsfield generate list --json and higgsfield generate get <id> --json work for retrospection. higgsfield generate wait <id> is still available if you ever need to rejoin a job started without --wait.

Media flags

FlagUse forModels that accept it
--image <path-or-id>reference imagemost image models, seedance_2_0, veo3, marketing_studio_video
--start-image <path-or-id>first frame for image-to-video transitionskling3_0, kling2_6, veo3_1, seedance_2_0, marketing_studio_video
--end-image <path-or-id>last frame for transitionskling3_0, seedance_2_0, marketing_studio_video
--video <path-or-id>reference videoseedance_2_0
--audio <path-or-id>reference audio (lipsync, soundtrack match)seedance_2_0 (use this, NOT --generate-audio)

Each flag accepts either a local file path (auto-uploaded) or a UUID (upload id from higgsfield upload create, or a previous job id). Each model declares its own role set via MEDIA_ROLES. See references/media-inputs.md for the full table.

Common params

Flags pass through to model schema. Use higgsfield model get <jst> to discover.

higgsfield generate create gpt_image_2 --prompt "neon city at dusk" --aspect_ratio 16:9 --resolution 2k --wait
higgsfield generate create nano_banana_2 --prompt "anime character concept, expressive pose" --image ./ref.png --wait
higgsfield generate create seedance_2_0 --prompt "camera dollies in" --start-image ./first.png --duration 8 --wait
higgsfield generate create text2image_soul_v2 --prompt "..." --soul-id <soul_ref_id> --quality 2k --wait

For machine-readable output (chained pipelines, agent context), add --json. With --wait --json you get the final job object array. Without --wait, you get the job IDs.

Stdin prompt: echo "..." | higgsfield generate create z_image --wait.

Soul image quality: for text2image_soul_v2 and soul_cinematic, pass --quality 1.5k or --quality 2k. These are UI-facing tiers; the backend maps them to 720p/1080p and model-specific dimensions from the selected --aspect_ratio. soul_location has no quality selector; it uses fixed dimensions per aspect ratio.

Marketing Studio

Branded image/video gen: avatars + products + optional setup hooks/settings + ad-style modes. Use models marketing_studio_video and marketing_studio_image.

Concepts

  • Avatar — presenter face. Curated preset (browse higgsfield marketing-studio avatars list) or custom (uploaded photos via higgsfield marketing-studio avatars create). For UGC modes, an avatar is optional if the brief clearly mentions a person; the backend can create a Soul Character automatically. Pass an avatar when the user wants a specific presenter.
  • Product — brand item with title + reference images. Imported from URL (higgsfield marketing-studio products fetch --url ...) or created from uploaded images (higgsfield marketing-studio products create).
  • Webproduct — App Store / web page version. Auto-routes when fetching App Store URLs.
  • Hook — reusable opening angle / ad hook. Browse with higgsfield marketing-studio hooks list. Hook text is prepended to the user's prompt; it does not replace --prompt.
  • Setting — reusable environment / scene context. Browse with higgsfield marketing-studio settings list.
  • Ad reference — reusable inspiration video that can be bound to an avatar and/or product. Created from an uploaded video (--video-input <upload_id>) or a previous generation job (--job <job_id>). Browse with higgsfield marketing-studio ad-references list. See references/marketing-ad-references.md.

Discovery commands

Use these exact list commands when the user asks what already exists:

higgsfield marketing-studio avatars list --json
higgsfield marketing-studio products list --json
higgsfield marketing-studio hooks list --json
higgsfield marketing-studio settings list --json
higgsfield marketing-studio ad-references list --json

--hook_id and --setting_id are supported by marketing_studio_video only; do not pass them to marketing_studio_image.

UX rules (additional)

  • One question per phase. Don't ask product+avatar+mode upfront.
  • Two ad approaches are mutually exclusive. Either the user gives an ad reference video (reference-driven) or picks hook/setting blocks (composed-from-blocks) — never both. If the user has an ad reference selected, do not offer hook/setting; if hook/setting are picked, do not offer to attach an ad reference.
  • Ad reference source. The only valid inputs are a local video file (uploaded via higgsfield upload create ... --video) or a prior video job. If the user provides anything else, ask for a local file.

Workflow — quick ad video

  1. Get product.
    • Existing product → higgsfield marketing-studio products list --json
    • URL → higgsfield marketing-studio products fetch --url <url> --wait (polls until import done)
    • Local images → higgsfield upload create <photo>... then higgsfield marketing-studio products create --title "..." --image <id>... Capture product id. When using --hook_id, strongly prefer passing --product_ids; hooks are designed to pivot into a product and work poorly without product context.
  2. Pick avatar if needed.
    • Default: higgsfield marketing-studio avatars list and pick a preset matching the brand voice.
    • Custom: higgsfield marketing-studio avatars create --name "..." --image <upload_id>. For UGC modes, you may omit --avatars when no specific presenter is required and the brief mentions a person; the backend can synthesize a Soul Character.
  3. Optionally pick setup items.
    • Hook: higgsfield marketing-studio hooks list --json
    • Setting: higgsfield marketing-studio settings list --json Pass selected IDs as --hook_id <hook_id> and --setting_id <setting_id> for marketing_studio_video only. Do not copy the hook's prompt into --prompt unless the user explicitly wants to reinforce the same wording.
  4. Pick mode if needed. Default is ugc; --mode is not required just because --hook_id is present. Other current slugs: ugc_how_to, ugc_unboxing, product_showcase, product_review, tv_spot, wild_card, ugc_virtual_try_on, virtual_try_on. Hook/setting are valid only for ugc, ugc_how_to, ugc_unboxing, product_review, ugc_virtual_try_on — do not pass --hook_id / --setting_id with the other modes. See references/marketing-modes.md.
  5. Generate (one-shot).
    PRODUCT_IDS_JSON=$(mktemp)
    AVATARS_JSON=$(mktemp)
    printf '["<product_id>"]' > "$PRODUCT_IDS_JSON"
    printf '[{"id":"<avatar_id>","type":"preset"}]' > "$AVATARS_JSON"
    
    higgsfield generate create marketing_studio_video \
      --prompt "..." \
      --avatars @"$AVATARS_JSON" \
      --product_ids @"$PRODUCT_IDS_JSON" \
      --mode ugc \
      --duration 15 \
      --resolution 720p \
      --aspect_ratio 9:16 \
      --wait
    Add --hook_id <hook_id> and/or --setting_id <setting_id> when a setup hook/setting was selected. product_ids and avatars are JSON arrays; pass them via @/path/to/file.json. Do not pass a bare UUID to --product_ids. Resolution is 480p or 720p. Aspect ratio is one of auto/21:9/16:9/4:3/1:1/3:4/9:16. --generate-audio true is supported here (unlike seedance_2_0). --wait blocks until done; bump --wait-timeout 30m for longer ad runs.
  6. Deliver. URL + one-line summary (mode, duration).

Click-to-Ad shortcut (URL-driven)

When the user gives a product URL and wants a marketing video in one go:

# 1. Trigger fetch (returns the product id and starts background scrape)
higgsfield marketing-studio products fetch --url https://shop.example.com/sneakers --wait

# 2. Generate the marketing video against the same URL — backend reuses the entity
higgsfield generate create marketing_studio_video \
  --url https://shop.example.com/sneakers \
  --mode ugc \
  --duration 15 \
  --aspect_ratio 9:16 \
  --wait

Backend dedupes by URL, so repeated runs reuse the existing entity instead of re-fetching.

Workflow — marketing image

Same as above but use marketing_studio_image model:

higgsfield generate create marketing_studio_image \
  --prompt "..." \
  --aspect_ratio 1:1 \
  --resolution 2k \
  --wait

Errors

  • Missing required params: prompt → user gave no prompt; ask for it.
  • Invalid values: aspect_ratio=99:99 (allowed: ...) → bad enum; pick from allowed.
  • Unknown params: foo → schema doesn't accept that flag; check higgsfield model get <jst>. If this happens for hook_id or setting_id, the selected model/job_set_type does not support Marketing Studio setup items.
  • Session expired → higgsfield auth login.

See references/troubleshooting.md for more.

Reference docs

Load on demand:

  • references/model-catalog.md — picking the right model for the task
  • references/prompt-engineering.md — writing prompts that work
  • references/media-inputs.md — image/video reference flows
  • references/troubleshooting.md — common errors and fixes
  • references/marketing-avatars.md — preset vs custom avatars
  • references/marketing-products.md — URL fetch vs manual product create
  • references/marketing-setup-items.md — hooks/settings discovery and usage
  • references/marketing-ad-references.md — ad reference videos (create/list/get)
  • references/marketing-modes.md — every Marketing Studio mode

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.