← HiggsfieldCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
changed
Update to Higgsfield
Snapshot Sep 30, 2026 · 23:18 UTC · version 2.1.0
Collection source: not recorded for this historical snapshot. These snapshots do not have a confirmed matching collection source. Differences in file lists alone do not establish changes to the package.
Supporting file metadata differs
Newly listed paths: agents/openai.yaml. This compares saved file lists, not package contents; a different collection source can change the list.
Observed in package metadata. These changes alone do not establish a new customer-facing feature.
Supporting files
Before
[]
After
[{"relative_path":"agents/openai.yaml","size_in_bytes":245}]
Compare saved observations
Download comparison JSONFull technical diff · 1 changed fields
changed /included_files
BEFORE
[]
AFTER
[
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 245
}
]Full snapshot data
{
"name": "higgsfield",
"description": "Resolve and execute named Higgsfield presets and slash commands, or browse Viral and Marketing Studio preset galleries. Resolve a named preset before loading production workflows suggested by its name, including cover or unboxing workflows; only returned instructions can request those helpers. Also route named /MODEL_NAME invocations. Ordinary model questions, media generation and Marketing Studio brand-kit records use direct tools. Mentioning Higgsfield alone, quoted/translated commands and explicitly negated commands are not invocations.\n",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 245
}
],
"skill_md_contents": "---\nname: higgsfield\ndescription: >\n Resolve and execute named Higgsfield presets and slash commands, or browse\n Viral and Marketing Studio preset galleries. Resolve a named preset before\n loading production workflows suggested by its name, including cover or\n unboxing workflows; only returned instructions can request those helpers.\n Also route named /MODEL_NAME invocations. Ordinary model questions, media\n generation and Marketing Studio brand-kit records use direct tools.\n Mentioning Higgsfield alone, quoted/translated commands and explicitly\n negated commands are not invocations.\n---\n\n# Higgsfield presets and commands\n\nResolve an explicitly selected preset or command before choosing another creative workflow. A product image alone does not override the user's chosen entry.\n\n## Browse\n\n- Both Viral and Marketing Studio: `get_presets` without `source`.\n- `/effects`: `source:\"viral\"`.\n- `/product`: `source:\"marketing_studio\", category:\"product-shot\"`.\n- `/motion`: `source:\"marketing_studio\", category:\"motion\"`.\n- `/marketing-studio`: `source:\"marketing_studio\"`.\n- Bundled recipes and commands: `get_preset_instructions` without `preset`.\n\nBrowsing does not submit jobs. The widget handles pagination; request another page only when the user asks. A catalog listing is not a resolved entry: load the chosen ID before execution.\n\n## Resolve and follow the entry\n\nFor `/genjutsu`, resolve the named server command first; its instructions choose the motion-transfer or object-replacement model. Do not treat the family name as a concrete model ID.\n\nFor other named entries, call `get_preset_instructions` with the exact slash token before requesting media. Examples: `/hero-shot`, `/reel-cover`, `/genjutsu`, `/use-after-effects`. Read references only when the returned instructions require them.\n\n- **Recipe:** follow its prompt, supported customization and generation workflow. Do not substitute a generic photoshoot or reinterpret the master prompt.\n- **Workflow:** follow the selected instructions and their required tools; collect missing inputs before submitting.\n- **Setup or instructions:** use the required environment. A cloud sandbox cannot install or control a desktop application. Loading instructions does not install software or prove a connection; respect the user's requested setup/editing scope and verify any claimed connection.\n- **Gallery entry:** the text response includes its input schema and exact detail lookup. Map relevant attachments to unambiguous slots, upload each once, then call `get_presets` once with source, preset_id and any initial_inputs. Leave missing fields for the widget. A bare gallery slash, preview or browse request opens the detail only. Generate only when the user requests it or uses Recreate. Check input readiness; available capability is not permission. Never send catalog IDs to ordinary generate_image or generate_video.\n\nWhen a token unambiguously names a supported generation model, use the matching generation tool with the user's brief and media. Resolve unfamiliar model IDs through `models_search` and `models_get`. A bare model name is not a generation brief: collect the subject or prompt and required media before submitting.\n\nA `not_found` result means the token is a plain-language hint, not a blocker: infer the intended output from the token, the request, attached media and the conversation, then complete it with ordinary tools and sensible defaults. Do not say the preset or command does not exist or ask the user to pick another one; never pass the token as a preset, catalog or model ID. Ask only when no outcome can be inferred, and ask about the outcome, not the command.\n\n## Deliver once\n\nFor ordinary generate_* results, use the auto-updating generation widget and `jobs_wait` with `timeout_seconds:15`; do not open a duplicate display unless requested.\n\nAfter execute_preset or a widget message with submitted job IDs, never execute again. For one job, use job_display and jobs_wait. For multiple jobs, wait in groups of at most eight and display the complete indexed set with show_generation_by_ids (up to 24 per call). Preserve returned order; do not use history to rediscover these jobs. A timeout can leave submission unknown: do not repeat an action merely because its response was lost.\n"
}SHA-256: f9585a050e17ac0f90fb65a1e2ed216d74d0597dfb7f6ca47d536111c6ab48f6