Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →coco-research/scroll-world
Build an immersive scroll-scrubbed "fly through the world" landing page for any industry or brand using Higgsfield. As the visitor scrolls, a pre-rendered camera flies from outside each scene into its interior, then flows on to the next scene with NO cuts — one continuous connected flight (Emons-style isometric diorama world, or any art direction you pick). The skill interviews the user for the topic, the story beats/sections, and brand kit, then generates cohesive scenes + seamless camera clips
Passed 16 of 19 test cases with the skill, and 4 of 19 without it.
and 15 more in the full report
13 fixed5 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are using Kling 3.0 to render video transition clips. A developer adds `--resolution 1080p` and omits audio settings in the CLI call command. What will happen, and what are the exact CLI flags required for Kling 3.0 in this pipeline?
| Checked | Without skill | With skill |
|---|---|---|
| State that Kling 3.0 rejects the `--resolution` parameter and renders at 720p native resolution. | Missed | Passed |
| Pass `--sound off` in the CLI call when generating clips with Kling 3.0. | Missed | Passed |
The instructions your model reads when the skill loads.
Produces a landing page where scroll drives a camera: it dives from outside a scene into its interior, then flies out and into the next scene, continuously, with no visible cuts. The visuals are AI-generated — stills via Higgsfield (or Codex), the video chain via Monid by default (pay-per-clip Seedance 2.0; Higgsfield credits as fallback) — and the page just scrubs pre-rendered video by scroll position. This is the same technique behind Apple's scroll-through product pages — the camera genuinely moves, scroll only drives time.
What you generate: N scene stills → N "dive-in" camera clips → N-1 "connector" clips that join consecutive scenes seamlessly → a portable scrub engine that plays the whole chain as one flight.
The one rule that makes or breaks it: seams must be frame-identical. Read The seamless chain before generating any connector. Getting this wrong is the single most common failure and produces a visible "pop" between scenes.
Do not assume a frontend framework. The scrub engine in references/scrub-engine.js is
self-contained vanilla JS (it builds its own DOM + injects its own CSS into a container
you give it), so it drops into plain HTML, Next.js, Vue, a Python-served page, anything.
The value of this skill is the Higgsfield pipeline, the prompts, and the seam method —
not the framework.
monid --version,
monid keys list (active key) and monid balance — the chain is billed per
clip in USD (Step 1.7 has the numbers; a 1080p N=6 chain ≈ $27). If the CLI is
missing or the balance can't cover the chain, say so and fall back to
rendering the chain on Higgsfield credits instead — same model, same
pipeline, different biller (Step 4 → Monid backend).gpt_image_2) and is the home of the kling3_0 NSFW fallback
and the fallback chain. If higgsfield is not on $PATH, install per the
higgsfield-generate skill. If higgsfield workspace list fails auth, ask the user
to run higgsfield auth login (interactive OAuth — you cannot run it) and, if needed,
higgsfield workspace set <id>. Confirm credits cover the stills (~N imagetest cases passed, vs 4 / 19 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.