agentleFS
Sign inStart free
agentik-osagentik-os/claude-code-skills/higgsfield-soul-id/SKILL.md

higgsfield-soul-id

Skill1 starsChanged 56 days agoMITView on GitHub

Train a face-faithful Soul Character on a person's photos for identity-consistent image and video generation — the visual-identity anchor reused across all Soul-powered output. Use when the user says "/omg-higgsfield-soul-id", "/higgsfield-soul-id", "train my face", "create my Soul", "digital twin", "consistent character", or "brand avatar". R-VISUAL-ID: plugs into the brand-identity pipeline and chains into higgsfield-generate via --soul-id. Requires the higgsfield CLI, auth, and a paid plan.

  • Pipes a download into a shell

17 other projects use a version of this, 16 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use higgsfield-marketplace-cards, higgsfield-websites and 6 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-marketplace-cards

    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).

    Also in 12 projects that use this

  • 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

  • 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

  • +3 more from higgsfield-ai

The file

We split this skill into the rules it gives an agent

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

  • 2

    Common

    Most of the 17 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Before any other command:

    line 22
  2. Very specific:

    If higgsfield is not on $PATH, install it:

    line 24
  3. Very specific:

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

    line 28
  4. Common:

    Ask for the smallest set of inputs: name + photos.

    line 35

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

OmegaOS skill — vendored from higgsfield-ai/skills (github.com/higgsfield-ai/skills). Triggers /omg-higgsfield-soul-id (and /higgsfield-soul-id). Governed by R-VISUAL-ID. Requires: the higgsfield CLI (installed at runtime), higgsfield auth login, and a paid plan (Basic+).

Higgsfield Soul Character

Train a face-faithful identity model. Reusable across all Soul-powered generations.

Step 0 — Bootstrap

Before any other command:

  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) and wait for confirmation.
  3. Soul training requires a paid plan (Basic+). If higgsfield account status shows free plan, tell the user before submitting.

UX Rules

  1. Be concise. No raw IDs in chat. Just say "Soul ready" with a name reference.
  2. Detect language and respond in it. CLI flags stay English.
  3. Ask for the smallest set of inputs: name + photos. Pick a sensible model variant.
  4. Polling is silent — training takes minutes. Don't repeat status updates.

Workflow

  1. Get name. One word, used for later reference. Ask if missing.
  2. Get photos. 5–20 face photos, varied angles and lighting. Local paths or already-uploaded IDs both work — --image accepts either.
  3. Pick variant.
    • --soul-2 — for image generation (default)
    • --soul-cinematic — for cinematic / video work Choose based on user's stated downstream use. Default to --soul-2.
  4. Submit.
    higgsfield soul-id create --name "<name>" --soul-2 --image ./photo1.png --image ./photo2.png ...
higgsfield soul-id create --name "<name>" --soul-2 --image <upload_id> --image <upload_id> ...
    CLI auto-uploads paths. Captures returned reference id.
  5. Wait. higgsfield soul-id wait <id>. Silent. Default timeout 30m.
  6. Deliver. "Soul <name> ready. Use in generate with --soul-id <id>."

Use the Soul

Once trained, pass to higgsfield-generate:

higgsfield generate create text2image_soul_v2 --prompt "..." --soul-id <ref_id> --quality 2k --wait
higgsfield generate create soul_cinematic --prompt "..." --soul-id <ref_id> --quality 2k --wait

Listing existing Souls

higgsfield soul-id list                   # all references
higgsfield soul-id get <id>               # one by id

Errors

  • Minimum Basic plan required — user is on free plan; tell them.
  • Training failed — check photos quality (5+ unique faces, well-lit).
  • Session expired → higgsfield auth login.

Reference docs

  • references/photo-guide.md — what photos work best
  • references/troubleshooting.md — common training failures

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.

Check your setup, free