pixel2motion
Turn a raster logo (PNG/JPG/WebP/screenshot) into a clean minimal SVG with edge smoothness as the primary hard gate and IoU optimized as high as reasonably possible without a fixed global threshold, then into a choreographed logo animation delivered as standalone JS-rendered HTML, applying Disney's…
Install / Use
npx skills add vibe-motion/skills --skill pixel2motionInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of pixel2motion
pixel2motion scores 91/100 on our quality scale, 1082nd of 4,698 Development & Engineering skills we index (top 24%).
Its SKILL.md is 28 KB long, well organised into 33 sections with 2 code examples: a thorough specification that gives an agent plenty to work with.
With 1,266 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so pixel2motion is actively maintained.
- Our last check on 2026-10-29 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
pixel2motion compared with similar skills
All 4 of these similar skills score higher than pixel2motion; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| pixel2motion (this skill)by vibe-motion | 91 | 1.3k | 2mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.6k | today | MCP Server |
Frequently asked questions
- How do I install pixel2motion?
- Run
npx skills add vibe-motion/skills --skill pixel2motion. The install tabs above show the steps for each supported agent. - Which AI agents does pixel2motion work with?
- It is written for Zed, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is pixel2motion safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/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 pixel2motion still maintained?
- The repository was last updated about 2 months ago, so pixel2motion is actively maintained.
Skill content
View source on GitHubname: pixel2motion description: Turn a raster logo (PNG/JPG/WebP/screenshot) into a clean minimal SVG with edge smoothness as the primary hard gate and IoU optimized as high as reasonably possible without a fixed global threshold, then into a choreographed logo animation delivered as standalone JS-rendered HTML, applying Disney's 12 animation principles. Use when asked to animate a logo, build a logo reveal / splash screen / brand intro, convert a logo image into animated SVG or HTML, add motion to a vectorized mark, or create loading/idle/hover motion for a brand mark. v2: also handles self-crossing draw-on choreography (split-fill, exact easing subdivision, tip glint), closed variable-width ribbon fitting, and quantitative motion QA (easing probe, ink-delta continuity sweep).
Pixel2Motion (v2)
Pixel → Vector → Motion. This skill fuses two disciplines:
- Vectorization discipline (from logo-vectorizer-minimal-smooth): fit the raster source with the lowest-complexity editable geometry that passes visual QA.
- Motion discipline (from Disney's 12 Principles of Animation): choreograph that geometry into brand-appropriate motion with evidence-based timing and easing.
The fusion rests on one insight: minimal smooth geometry IS animatable geometry. A logo built from 3 semantic parts animates cleanly; a logo built from 400 pixel-stair traced points cannot be choreographed or accepted as a professional logo vector. Phase 2 therefore does not merely vectorize — it structures for motion. And the animation must always land exactly on the QA-verified static vector (the Final Frame Contract).
Deliverables
logo.svg— final static vector (motion-ready structure)logo_motion.html— showcase-style standalone HTML with the main animation, atomic motion studies, replay/slow/speed controls, and QA hooksmotion_spec.md— personality words, principles applied, timeline table, easing tokens, atomic motions, tunable controlsoutputs/fit_iterations/*.png+overlay_progress_strip.png— geometry QA evidenceoutputs/motion_frames/*.png+motion_strip.png— motion QA evidencefinal_render.png,html_render.png— static renders; path audit artifacts when smoothness was a concern
Phase 1 — PIXEL: Read the source, write the brief
- Analyze the raster source. Record image size, mode, alpha, foreground colors, background (transparent/solid). Identify the semantic parts: mark vs wordmark, individual letters, dots, swooshes, containers, negative space. Each part is a future actor in the animation.
- Write the motion brief before touching geometry:
- Personality: 3 brand motion words (e.g. "swift, precise, confident"). Derive from the logo's own visual language (geometric = engineered motion, organic = flowing motion, rounded = soft/bouncy) plus any user-stated brand context. See
references/motion-personality.mdto map words → timing scale, easing tokens, principle emphasis. - Usage context: splash/intro (deliberate 1200–2000ms), header reveal (300–800ms), loading state (continuous loop), hover micro-interaction (150–300ms). Ask the user only if genuinely ambiguous; default to a splash-style reveal plus a static end state.
- Choreography sketch: which parts move, in what order, using which reveal pattern (see
references/reveal-patterns.md).
- Personality: 3 brand motion words (e.g. "swift, precise, confident"). Derive from the logo's own visual language (geometric = engineered motion, organic = flowing motion, rounded = soft/bouncy) plus any user-stated brand context. See
- Record the brief in
motion_spec.md. Every later parameter must trace back to it.
Phase 2 — VECTOR: Fit minimal geometry, structured for motion
Follow the lowest-complexity-first workflow. Do not maximize pixel-fit by default; start with the simplest editable geometry that can explain the mark, escalating only when an overlay shows a structural mismatch.
Complexity Ladder
Use the first level that matches the source well enough:
- Primitives: circles, ellipses, rects, lines, simple arcs, transforms.
- Primitive composites: boolean-like combinations of a few primitives or masks.
- Few-curve analytic paths: a small number of cubic segments for smooth ribbons, swooshes, C-marks, leaves, waves, shields. For closed and/or self-intersecting variable-width ribbons (∞ marks, scripts) use the centerline-scaffold recipe —
references/ribbon-fitting.md+scripts/fit_ribbon_centerline.py; its report also emits each crossing's arc fractions, which Phase 3's split draw-on needs. - Smoothed outline paths: more knots only where the source has real shape changes; preserve G1 tangent continuity, no noisy handle flips.
- Trace-derived paths: only for irregular silhouettes where simpler geometry fails (
scripts/raster_logo_trace.pyfor measurement/starter masks). Trace output is a measurement aid, never automatically final art. Smooth or refit the trace before delivery.
If a higher-complexity version improves only pixel antialiasing, keep the lower one. If a lower-complexity version has wrong endpoints, width profile, center, silhouette, negative space, or visibly stair-stepped edges, move up one level or refit with smooth curves. Prefer live SVG <text> for wordmarks unless exact letterforms are required. Decide the provisional complexity from the source itself and record the reason in motion_spec.md.
Smoothness Gate (hard requirement)
IoU is not allowed to hide bad vector craft. A smooth logo source must ship as smooth vector geometry. The final SVG fails geometry acceptance if any intended smooth edge visibly stair-steps, chatters, has pixel-grid orthogonal runs, contains noisy trace knots, or looks like a bitmap mask at 200-400% zoom, even when IoU is numerically high.
- Pixel-grid contours from threshold masks are acceptable only as starter measurements or for genuinely pixel-art logos. For ordinary logos, refit them into primitives, arcs, ellipses, or cubic paths before Phase 3.
- A path made mostly of 1px horizontal/vertical line segments is a failed smoothness gate for curves, swooshes, ellipses, circles, letters, and rounded shapes.
- Smooth parts must be represented by the lowest number of curve segments that preserves silhouette, width profile, extrema, and negative space. Do not chase antialiasing with hundreds of line segments.
- When replacing a high-IoU jagged trace with a smoother curve slightly lowers IoU, prefer the smooth version if structural landmarks still match. The smooth result may pass with a lower IoU when the residuals are explainable, visually minor, and caused by deliberate smoothing, antialiasing, font substitution, or raster-source artifacts. Record the tradeoff in
motion_spec.md. - Inspect a zoomed render (
final_render.pngor a dedicated zoom crop) before accepting. If the user would notice stair-stepping in a screenshot or browser zoom, the vector is not accepted.
Motion-Ready Structure (the fusion layer)
The SVG is a cast of actors, not just a picture. While fitting geometry, enforce:
- One element (or
<g>) per semantic part, with stable ids:#mark,#wordmark,#letter-a,#dot,#swoosh. Animation targets ids/classes — never structural selectors likepath:nth-child(3). - Split paths along animation seams. If the choreography sketch animates the swoosh separately from the dot, they must be separate elements even if one compound path could render both.
- Transform origins: parts that scale/rotate get
transform-box: fill-box; transform-origin: center(or a deliberate origin) — set via CSS in Phase 3, but verify each part's bounding box makes that origin sensible now. - Draw-on readiness: any stroke that will be drawn on gets
pathLength="1"so dash animation isstroke-dasharray: 1; stroke-dashoffset: 1 → 0regardless of true length. Confirm the path's start point and direction match the intended draw direction; reverse the path if not. - Wordmark letters: if letters will stagger, give each its own element/
<text>span; a single<text>cannot cascade. - No baked transforms that fight choreography: keep part-local coordinates simple so animated transforms compose predictably.
Geometry QA (evidence required)
- Write SVG with a correct
viewBox; render to PNG; generate a cyan overlay over the source; save every overlay underoutputs/fit_iterations/NN_name_overlay.png. - Inspect overlays with multimodal vision: centers, radii, endpoints, width profile, extrema, negative space, silhouette.
- Compute and record IoU every iteration, but do not use a fixed global IoU threshold. Optimize IoU as high as reasonably possible after smoothness and structural correctness are protected. A slightly lower IoU can pass when the overlay is visually faithful and residuals are documented; a high-IoU fit still fails if it has structural mismatches, noisy handles, visible bumps, wrong negative space, pixel-stair edges, or path-audit failures.
- Iterate one complexity level at a time; prefer moving/retuning a few knots before adding knots; add local complexity only where the overlay proves failure. If a path looks bumpy, reduce knots and re-fit macro curves — do not add points.
- For complex smooth paths or any hand-fitted curve that feels uneven, run
scripts/svg_path_audit.py(noisy handles, tangent jumps, tiny alternating segments, and stair-step trace runs are failures even at high IoU). - Save at least one smoothness evidence image when the source has curves: a zoomed crop, path audit artifact, or render that makes edge quality inspectable. Record the visual verdict in
motion_spec.md. - Finish with
scripts/overlay_progress_strip.py(source + current-run overlays + final render only).
Iteration budget: smooth accepted fit or best-of-10
Fitting loops rabbit-hole easily. Default budget: 10 geometry iterations per run (one iteration = one geometry change + render + overlay inspection). The loop stops when either one arrives first: accepted fit (smoothness, structural, and visual checks pass, with IoU pushed as high as practical) or 10 iterations attempted.
- Number every iteration's artifacts (
NN_name_overlay.png) and record metrics per iteration (IoU,src_only_px,render_only_px, boundary RMS / local residuals, audit warnings, smoothness verdict, visual verdict). Persist the fitting scripts and parameters underoutputs/fit_work/so any iteration can be resumed later — never leave them in throwaway temp paths. - Reaching accepted fit early ends the loop early; proceed to Phase 3 immediately.
- When the 10-iteration budget is exhausted: stop refining and select the best candidate. Ranking for "best": (1) smoothness gate pass, (2) no structural mismatch, (3) IoU and pixel deltas, (4) boundary RMS / local residuals, (5) fewest audit kinks and tangent issues, (6) visual overlay verdict, (7) lowest editable complexity. A clean-but-slightly-loose fit generally beats a tighter fit with a visible tangent kink; an invisible kink may ride along only as a disclosed known issue.
- If the shipped candidate has a lower IoU than another rejected candidate, report why it still passes or why it is only a preview (e.g. "IoU is lower because jagged threshold artifacts were smoothed; endpoints and silhouette landmarks match"). Geometry-only refinement does not require redoing the choreography — part ids and the centerline survive, so
motion.cssis reusable and only re-packaging (animate_svg_showcase.py) plus the Final Frame Contract re-check are needed.
Phase 3 — MOTION: Choreograph with the 12 principles
Choreograph against references/twelve-principles-for-logos.md. Minimum bar: every animation consciously applies Staging, Slow In/Slow Out, Timing, Follow Through, and Appeal; the rest as personality demands.
Structure the timeline with the Golden Ratio
Anticipation : Action : Follow-through = 20% : 50% : 30%
For a 1500ms reveal: ~300ms anticipation, ~750ms main action, ~450ms settle. Stagger overlapping parts by 10–20% of the part's own duration; never let all parts start or stop on the same
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe 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.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.6k🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
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.
