higgsfield-acting
Writes the character-performance layer of a video prompt as behavior under pressure, not displayed emotion — objective, obstacle, tactics, beats, subtext,…
Tests whether a scene is structurally worth generating before any shot is prompted — a five-element engine of Goal, Obstacle, Tactic, Reversal, and Value Shift. Use when the user has a scene, sequence, beat outline, or script and wants it audited or strengthened; when a sequence
$ npx -y skills add OSideMedia/higgsfield-ai-prompt-skill --skill higgsfield-scene-engine --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/higgsfield-scene-engineContext preview
The summary Claude sees to decide when to auto-load this skill.
Tests whether a scene is structurally worth generating before any shot is prompted — a five-element engine of Goal, Obstacle, Tactic, Reversal, and Value Shift. Use when the user has a scene, sequence, beat outline, or script and wants it audited or strengthened; when a sequence
name: higgsfield-scene-engine description: "Tests whether a scene is structurally worth generating before any shot is prompted — a five-element engine of Goal, Obstacle, Tactic, Reversal, and Value Shift. Use when the user has a scene, sequence, beat outline, or script and wants it audited or strengthened; when a sequence generates cleanly but lands flat and nobody can say why; when shots look good individually but the run of them does not build; or when the user asks 'is this scene working', 'what's weak here', or 'why doesn't this land'. Upstream of prompting — it decides WHICH shots deserve the credits, not how to write them. Pairs with higgsfield-character-design (who the characters are) and higgsfield-shotlist-director (turning the settled scene into shots)." user-invocable: true metadata: tags: [higgsfield, story, scene, structure, sequence, audit, dramaturgy, pre-production, reversal, value-shift] version: 1.0.0 updated: 2026-08-22 parent: higgsfield
`[DEMO — Tigran (tig-scene-engine), 2026-06-26]` `[UNPROVEN HERE]` **These definitions are bespoke and deliberately not the textbook ones.** Apply them as written; do not substitute standard screenwriting glosses, which are looser and will pass scenes this engine fails.
**Why a prompter carries this.** Every shot costs credits and iterations. A structurally dead scene generates just as cleanly as a live one — the model has no opinion about whether a beat earns its place — so the failure surfaces only after the footage exists and the cut does not build. This skill is the cheapest pass in the repo: it runs on text, before any generation, and its whole job is to stop you paying to render a scene that cannot work.
It decides **which** shots deserve the spend. `higgsfield-shotlist-director` turns the settled scene into shots; `higgsfield-acting` writes the performance inside them.
---
The single, unchanging thing the hero is fighting for: to fix what has already been established and reach, as fast as possible, the result that resolves it. "Already established" means *anything* set up earlier — deep backstory, a few scenes ago, or one minute ago.
about **tactics**, never about the goal.
remove the scene and the chain still holds, the scene fails. No orphan scenes.
**Obstacle + Stakes**. A hero taking a tactic the stakes would not justify (showering while the building burns) is a flaggable inconsistency: name it as bad writing or as deliberate self-sabotage.
A strong circumstance that **jeopardizes** either one stage of the path or the whole goal. It *threatens*; it does not merely *cost*.
hard wall** (a dead battery — you cannot search a dead machine). A wall typically spawns a fresh sub-goal with its own terrain.
goal).
tactic needed → no scene.
obstacle is fake and the scene goes slack.
The move the threat **forces** the hero to choose — a reasonable guess on his current, often incomplete, knowledge. This is **search under uncertainty, not error-as-stupidity.**
The engine is a **knowledge gap**: the distance between what he believes and what is.
next move. The drama is the narrowing, not the punishment.
something new.
a wheel-spin. A failing tactic is only a weakness when the failure teaches nothing.
A turn against expectation. Three forms:
1. **My own action flips on me** — what I did *for* something starts working *against* it (I shower to make the pitch; the shower makes me late and I miss it). 2. **Hidden agency revealed** — the thing or person I thought I was acting *on* was acting *on me* all along. The thriller move; it often fires exactly when the knowledge gap closes. 3. The general case: the situation turns opposite to what the tactic intended.
**Placement:** at least one reversal **per sequence**. A single scene may be pure escalation, but a *resolved sequence* with zero reversals **fails**.
A **sequence** is the run of scenes from when a specific jeopardy opens to when it resolves — overcome, or it defeats him and forces a new path. Sequences **nest**, and each resolving unit needs its own reversal. Flag which scale you are auditing.
**The change in the AUDIENCE'S read of a character, triggered by a reversal.** The keystone, and the most misunderstood element: it does not happen on the page, it happens in the viewer's mind. Each reversal forces the audience to **re-judge** the character — a moving verdict they keep revising (*nice → experienced → cunning → no, he's desperate → devoted son → what a man*).
> **THE CORE RULE: a reversal with no value shift is inert.** A structural turn is not a > reversal unless it moves the audience's verdict. If you cannot name a **before-verdict** > and an **after-verdict** the audience would hold, the turn is dead weight no matter how > much plot flipped.
Audit the **trajectory**, not just
A comprehensive Claude skill library for generating high-quality prompts on Higgsfield AI — the cinematic video and image generation platform.
Writes the character-performance layer of a video prompt as behavior under pressure, not displayed emotion — objective, obstacle, tactics, beats, subtext,…
Use when the user asks about Higgsfield's one-click Apps, wants to know which app to use for a specific output, or needs guidance on the Apps workflow.
Use when the user asks about Higgsfield Assist (the built-in GPT-5 copilot), how to use the platform's native AI assistant, credit optimization strategies,…
Use when the user asks about audio in Higgsfield videos, needs to add dialogue or lip-sync, wants sound effects or ambient sound in generated video, asks about…
Use when the user asks about camera movements, shot types, or how to describe camera behavior in a Higgsfield prompt. Contains all named camera controls with…
Use when the user mentions Higgsfield Canvas, a node-based or node graph workspace, an infinite board/canvas, chaining generations into a pipeline, or wants to…