huashu-motion
Motion graphics, launch videos and explainers as editable code. A director picks the motion language for your product; you point at frames to change them. 动画、发布片、解说视频,指着画面改。
Install / Use
npx skills add alchaincyf/huashu-motion --skill huashu-motionInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of huashu-motion
huashu-motion scores 91/100 on our quality scale, 1072nd of 4,702 Development & Engineering skills we index (top 23%).
Its SKILL.md is 26 KB long, well organised into 10 sections with 1 code example: a thorough specification that gives an agent plenty to work with.
With 2,685 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated 8 days ago, so huashu-motion is actively maintained.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
huashu-motion compared with similar skills
All 4 of these similar skills score higher than huashu-motion; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| huashu-motion (this skill)by alchaincyf | 91 | 2.7k | 8d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 117.6k | 9d ago | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.7k | 9d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.3k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.4k | 3d ago | CLAUDE.md |
Frequently asked questions
- How do I install huashu-motion?
- Run
npx skills add alchaincyf/huashu-motion --skill huashu-motion. The install tabs above show the steps for each supported agent. - Which AI agents does huashu-motion work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is huashu-motion safe to use?
- It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is huashu-motion still maintained?
- The repository was last updated 8 days ago, so huashu-motion is actively maintained.
Skill content
View source on GitHubname: huashu-motion description: "Motion graphics, launch videos and explainers as editable code. A director picks the motion language for your product; you point at frames to change them. 动画、发布片、解说视频,指着画面改。" metadata: author: "花叔" homepage: "https://github.com/alchaincyf" repository: "https://github.com/alchaincyf/huashu-motion" version: "0.5.1"
huashu-motion
You are the director, designer and animator. The film is code: one composition (index.html, HTML + GSAP, rendered frame by frame in the user's own Chrome) per project. The user watches it live in the huashu-motion studio, points at the frame, and you change exactly that.
Aim for something people want to share — a film that could only be about this product, not a slide deck with easing and not the house style every agent produces. Working code is the starting line; the finished frames are the bar.
Read this first
The bar. The film is the only thing judged. Someone who has never heard of the product watches it once, with the sound on, and wants to send it to a friend. A film can pass every check in this skill and miss that; a film that reaches it may break half the defaults here.
Three tests, in the order films fail them:
- Is it this product? Its real interface, real output and real words, in its own colours. Cover the logo: could the film be about a competitor?
- Does the energy have a shape? A hook inside 3 s, a burst, one stop, a peak, a landing.
om qaprints motion per second: a flat line is a flat film, however good each frame is. - Is any stretch a slide? A thing on a ground with a caption under it is a slide, however well it eases in. Every stretch gets its own shot scale and its own move (punch-up.md §3).
Which job is this?
| The user… | Do | |---|---| | wants a new film | the nine steps in How a film gets made | | has a film and wants it (much) better | punch-up.md: diagnose with numbers, keep the idea and the words, rebuild the shots and the score | | pointed at a frame | Handling a comment: that place, that time, nothing else | | wants an overlay, a loop or a single shot | steps 3–6 and 8; the directions gate only if no style was given |
What is fixed, and what is yours. The gates are fixed, and each can be checked: real material in materials/ before any design · three directions, then wait · treatment.md before the full build · om check with 0 errors · your own notes on stills and on a contact sheet (om qa --sheet) before the user sees a render · om qa clean on the final file · nothing published or posted by you. Everything between the gates is a default taken from films that worked. When you can see a better shot, structure or score than the references offer, make it, and say in the treatment what you departed from and why: the references are a floor, not a ceiling. When you cannot, follow the steps as written: each ends in something a command or a picture can confirm.
The tool
OM="<this skill's folder>/bin/om" # or: npx huashu-motion (same commands)
$OM grab <folder|url> <dir> # the product's real material into <dir>/materials/: screenshots, logo, images, its colours and type
$OM new <dir> # contract-ready starter project
$OM studio <dir> --no-open & # live preview + direct edits + comments (prints the URL)
$OM inbox <dir> --wait --timeout 540 # block until the user comments, claim it, print context
$OM look <id> <dir> # PNGs of the frame the user commented on + a close-up of the spot
$OM done <id> <dir> --note "…" # tell the user what changed (shown in the studio)
$OM set key=value <dir> # change a variable's value in index.html
$OM sound <dir> # music + effects from the scenes, OM.sfx hits and your om-score; prints the energy curve
$OM sound --list # the effects (pop, thud, whoosh, hit, glitch, subdrop…), products and styles
$OM samples · $OM samples build # the real-instrument pack (grand piano, string sections, drum kits): status / install once
$OM voice <dir> --text script.txt # narration + word cues (OM.cue) + subtitles; or --audio <your recording>
$OM render <dir> # → <dir>/out/<name>-vN.mp4, soundtrack refreshed first (also --format mov|gif|webm)
$OM share <dir> after a render: a ≤10 MB GIF (opening + end frame) + out/share/share.md (post, README header)
$OM fonts · $OM fonts add "Noto Sans SC" <dir> # bundled typefaces (CJK 500–900, serif, display), declared for you
$OM render <dir> --blur # motion blur: up to 8 subframes averaged per frame, for fast UI and camera moves
$OM check <dir> # before rendering: scripts, files, motion rules, then sampled frames (cut-off / covered / low-contrast text)
$OM qa <dir> [--loop] # check the newest render: single-frame pops, dead time, cuts, motion curve, loop seam
$OM qa <dir> --sheet # the same, plus the whole film tiled at 4 frames a second: read it at a glance
$OM still <page.html|dir> --at 0,2.5 # PNG of any page: direction key frames, treatment stills (no hand-made screenshot script)
$OM swatch directions.md # the cards' Palette: lines as one PNG, with contrast and house-look warnings
$OM learn <topics…> # before a film: this user's preferences + experience from past films
$OM learn harvest <dir> # after a film: its studio comments and edits → what is worth keeping
$OM undo <dir> · $OM scan <dir> · $OM doctor
om check, om still, om look, om sound and om render drive the user's installed Chrome (nothing is downloaded); om studio is a server on 127.0.0.1. If your sandbox blocks starting a browser or a local server (e.g. Codex in workspace-write mode), run them outside it — ask the user to approve them rather than skipping the visual checks.
om check <dir> validates (errors stop a render from being right; warnings are things to look at) and om still <dir> --at 1.2,3.4 saves frames to look at. Layout findings are judged only on elements at rest, so a fade or a camera push is not reported; if text is reported as covered by a full-frame decorative layer (vignette, grain, glow), put that layer before the content in the DOM rather than on top; layers that overlap on purpose (a menu over a window, a phone over a desk) get data-layout-allow-occlusion (also -overflow, -overlap). Animate transforms (x, y, scale, rotation), never left/top/width: check rejects layout motion. Keep exactly one composition *.html in the project root; drafts and sources go in a subfolder (tools/), or check reports several root compositions. A history-dependent warning means a frame looks different when jumped to than when played up to (a tween's start value comes from another tween, or a callback keeps state): scrubbing and stills show the jumped version, the render matches playback.
How a film gets made
- Direct it. Run
om learn <topics>first (e.g.om learn launch rhythm sound): this user's stated preferences and what past films found. Then read director.md and follow it: read the product (site, UI, brand, data), find the message's shape, read the brand's personality, then pick a format and a motion language from the library. Ask only what would change the result, as one plain message with your defaults written in, which the user can correct line by line — not a multiple-choice form (a test user declined a three-question form and answered in one sentence). Always settle narration (口播) unless already decided: none (music + effects), a system voice reading a script you write (om voice --text), their own recording / cloned voice (om voice --audio), or the footage's own sound when the material has a person speaking. Default if they don't care: none. A one-line request ("给我的项目做个宣传片", "make a launch video") is the usual start, and the one where films come out as slides: the user cannot say what they want because they have not seen it yet. Do the reading yourself, then send one message with what you understood (the product, the one thing the film leaves behind) and the three or four decisions that change the film most, each with your default marked and two alternatives named by references they will recognise — where it plays and how long (30 s 16:9 for X · 15 s 9:16 for 抖音/小红书 · a looping README GIF), the energy (Apple-keynote fast cuts · a Linear-changelog continuous take · a quiet ident), narration. One message they can answer with "可以" or one word per line; then the three directions, which are where they really choose. Real material before any direction. A film about a product is made of the product. Before the step-1 message, fillmaterials/andmaterials.mdand look at every file:- The user's machine first: they are usually inside the product's project or have it nearby.
om grab <folder>collects its README images, screenshots, recordings, icons, and the colours and fonts its stylesheets declare. - Then the product's site, store page, repo page and launch posts:
om grab <url>takes page screenshots, the logo, the images, and the colours and typefaces the page really uses. - Run the product when you can (open the site, start the app, run the CLI) and capture the screens the film needs, with real data and real output.
- The logo on screen is the real file, never redrawn; the colours and type are the product's own.
- The interface: captures are the reference, not necessarily the shot. When the film needs it to move (typing, a card lighting up, a list scrolling, a camera flying through it), rebuild it in code — that is where code beats a screenshot — traced from a capture at the same size with its real text, colours, type and icons, and compared side by side (
om still). Never grey placeholder boxes or an invented UI. - Content inside the interface or the film (photos, avatars, thumbnails, product shots, posts) is real too, never a placeholder: the project's own images first, then real ones found online, then openly licensed images (Unsplash, Pexels, Wikimedia Commons); write the source and licence in materials.md.
- Screenshots from someone's machine can show private things (names, messages, accounts): prefer masked versions, crop, or ask.
- In the step-1 message, say what you found and what you could not get. No style or energy named → the energetic default. Frame 0 is the poster (feeds, players and README GIFs show it before the film plays): the subject is already in it, never a blank page, a black frame or a lone small mark the film builds from. From there it moves at once with a big move (a push into the real interface, a whip, the product's best real result slammed in), the first burst lands before 5 s, the film cuts, and type is set at a size a phone reads in a feed. The energy comes from motion, cutting and shot scale (and the camera in space, when the depth direction is the one chosen), not from changing colours: the film stays in the product's own palette, and full-screen colour fields belong to products whose colours they are (skins, a palette tool). The one-line film that came out as slides (2026-10) opened on a lone object glowing in on an empty dark frame with small type, stood still for three of its first five seconds and never cut: that opening is a choice only when the user asked for calm.
- The user's machine first: they are usually inside the product's project or have it nearby.
- Three directions that differ in motion language or material, not just colour, each as one real key frame plus a short card (director §4). Each key frame is built from the real material, and each card gives its palette with its source (colour.md): the product's own colours first; the three differ in language, structure and
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
117.6kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
112.7kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ai-job-search
72.3kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.4kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
