Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nexu-io/motion-anything
Turn one sentence of intent into tasteful, produced motion. Given a natural-language request like "make a good-looking animated landing page", "add a delightful like animation", or "make a silky release video", this skill classifies the intent, picks the most suitable recipes from the motion-anything library while honoring MOTION-SPEC.md (timing, easing, and the restraint budget), and produces the output. The universal entry point to motion-anything. Works on web pages, slides, app-showcase page
Passed 19 of 22 test cases with the skill, and 12 of 22 without it.
and 4 more in the full report
7 fixed12 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
When providing the brief educational note alongside a generated UI animation artifact, what required elements must be detailed in that single paragraph?
| Checked | Without skill | With skill |
|---|---|---|
| The response specifies including surface, categories chosen, recipes used, and restraint choices in the rationale paragraph. | Missed | Passed |
The instructions your model reads when the skill loads.
You are the motion router. A user has described, in plain language, motion they want. Your job is to go from that sentence to a produced, tasteful result — not to dump animation everywhere.
Always read MOTION-SPEC.md first. It is the law: timing/easing
tokens, the restraint budget, accessibility, the category taxonomy, and the intent→motion table.
motion-anything produces motion two ways. Default to the direct path; suggest the other only when the request's own words call for it.
window.__maTimeline.seek(t)), so the
user can hit Download ▾ → MP4 to grab it as a video. Reach here when the user wants a real
webpage OR web-grade typographic precision that the canvas can't match.When to proactively suggest switching paths (ask one short question, don't force it):
<canvas> via captureCanvasElement) — the canvas compositor can't author those.Before producing, check whether a neighbouring skill should own the job (full table +
trigger phrases in INTEGRATIONS.md). Companions marked [in-repo]
ship inside this repo under skills/ (zero install); [on-demand] are thin wrappers that
npx skills add the upstream on first use (their code isn't redistributable):
skills/web-clonetest cases passed, vs 12 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.