Seedance motion
OpenGod - 14-module AI super skill. Fuses 18 of Top 50 GitHub AI projects.
npx -y skills add 381487190/opengod --skill seedance-motionAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
This skill should be used when the user asks for body action, choreography, physics, object movement, movement timing, action continuity, stunt direction, or motion-reference mapping in Seedance 2.0.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
4.7 KB, 895 tokens by cl100k_base, as published. Nobody here has run it
seedance-motion
Use physical verbs and consequences. Motion should be observable on screen, timed within the clip, and assigned to a subject or object. Prefer one strong action with a visible endpoint over several vague actions competing for attention.
Load [ref:reference-workflow] for video-motion references, [ref:shot-list-continuity] for action handoffs across shots, [ref:examples-by-mode] for safe edit, extend, and R2V patterns, and [ref:directing-engine] when motion is performance: translate the scene's emotion into one true visible gesture per beat - a playable action with an objective and subtext - instead of an emotion word the model cannot render.
Intent
Motion is the verb of the user's story - the thing they came to see HAPPEN. The soul here is consequence: motion that begins, lands, and changes something feels lived; motion that loops feels generated. Every action carries the story one beat forward, or it doesn't belong in the clip.
Motion Contract
State: actor/object, action, force level, timing, physical consequence, continuity requirement, and endpoint.
| Motion type | Strong phrase | Weak phrase |
|---|---|---|
| Subtle acting | Character A inhales, grips the cup tighter, then sets it down without looking away | she feels nervous |
| Product material | condensation beads gather, merge, and slide down the bottle neck | the product looks refreshing |
| Choreography | Character B ducks under the swinging bag, pivots left, and stops in a guarded stance | fast action fight scene |
| Object physics | paper receipt lifts in the fan breeze, flips once, and lands face-up | papers move dynamically |
| Environmental motion | rain streaks diagonally across the backlight while puddle ripples spread from footsteps | stormy weather atmosphere |
Physics-Forward Pattern
Official material claims strong physics; extract it by writing causes and letting the model compute consequences (field-observed emphasis - test before promising results). State mass, force, and material, then name one consequence the camera can see: the heavy oak door swings shut and the candle flames bend toward it beats the door closes dramatically. Consequences prove the action: weight shows in landing compression, momentum in overshoot and recovery, friction in skid length, wind in what it displaces. One physical cause with two or three visible consequences reads stronger than three separate actions.
Timing Pattern
Use a three-beat structure for short clips: setup, action, changed end state. Example: 0-2s: candle flame steady; 2-4s: door opens and flame bends; 4-6s: smoke trail curls toward the hallway. Time segmentation is useful for action, VFX, lip-sync, and product demonstrations, but avoid frame-perfect overload unless the user truly needs it.
When sound drives the motion, pair each visible change with one beat or SFX: door click at 2s, light pulse on the downbeat, hand releases the cup on the final chime. Do not ask for many cuts, locations, and micro-actions inside one short clip.
Reference Motion Rules
For reference footage, use only owned, licensed, public-domain, stock, mocap, rehearsal, or self-recorded material. Map @Video1 to motion, camera, timing, or blocking, not identity, unless the identity is authorized. If a reference contains a real person, transfer only general motion or camera behavior and explicitly exclude likeness transfer.
Stability Rules
Hands, faces, logos, and product geometry drift when too many actions occur. Reduce motion around fragile details: lock the camera for lip-sync, keep hands in simple poses, ask product parts to remain rigid, and move light or environment instead of the core identity anchor.
Sequence State
When sequence state is present, inherit the observed action phase, open motion vector, current clip scope, continuity locks, exact reference tags, and reserved future beats. Do not replay actions marked already happened or completed. Do not perform a reserved beat early; carry unfinished motion from the accepted end state into the next clip.
Output Contract
Return the motion phrase, timing pattern, reference role map if any, and repaired prompt language.
Gives 0 of the 12 instructions most css styling skills give in 895 tokens
Counted across 586 of the 596 authors here whose files we hold, read 2026-08-06
- avoid excessive centered layoutsin 55 of 586, across 12 files
- bundle code into single HTML filein 54 of 586, across 14 files
- Respect prefers-reduced-motion user settingsin 52 of 586, across 35 files
- avoid purple gradientsin 51 of 586, across 11 files
- avoid uniform rounded cornersin 51 of 586, across 11 files
- avoid Inter fontin 51 of 586, across 11 files
- edit generated files to develop artifactin 50 of 586, across 10 files
- animate only transform and opacity propertiesin 43 of 586
- Make touch targets at least 44x44 pixelsin 41 of 586, across 15 files
- Ensure minimum color contrast of 4.5:1in 39 of 586, across 10 files
- use tailwind cssin 39 of 586, across 24 files
- Use SVG icons instead of emojisin 38 of 586, across 11 files
Said here and by no other author read
- state actor, action, force, timing, consequence, and endpoint
- use physical verbs and consequences
- prefer one strong action with a visible endpoint
- write causes and let the model compute consequences
- use a three-beat timing structure for short clips
- pair each visible change with one beat or SFX
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.