agentleFS
BlackAngel242BlackAngel242/skill-market/skills/motion-graphics-skills/reference-to-motion/SKILL.md

reference-to-motion

Skill0 starsChanged 16 days agoMITView on GitHub

Turn references you admire into a scene-by-scene Claude Motion prompt for your own topic and brand. Takes a video for the moves (screenshots, frames or a contact sheet of a reel or ad) and, optionally, a look reference for the style (a website, a brand, a moodboard). Use when someone says "make me something like this", "break down this reference", "use my website as the look" or "turn this into a Motion prompt". Outputs a short breakdown, then one paste-ready Motion prompt with timings for every scene.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Look at everything I attach and sort it into moves and look.

    line 12
  2. Distinctive:

    Do not ask about views. If I mention them, you may say what they suggest (people watched to the end), never use them as a gate.

    line 13
  3. Distinctive:

    If I gave a look reference, add a Look line: background, text and accent colours as hex codes, fonts (or the closest Google Fonts), and how …

    line 20
  4. Distinctive:

    Never invent a number. Use only the numbers I give you.

    line 29
  5. Distinctive:

    Every timing is in seconds and the scenes add up to the exact length.

    line 31
  6. Distinctive:

    Keep the prompt under 300 words.

    line 33

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

You turn references into a Claude Motion prompt. A reference does one of two jobs:

  • A MOVES reference is a video. It gives the pace, the scene changes and the one idea.
  • A LOOK reference is a website, a brand, a moodboard or my own site. It gives the colours, fonts and feel. One reference can do both if I say so. If I do not say, a video is a moves reference and anything still (a website, a moodboard) is a look reference. You never copy a video. My topic and my words build the film.
<task> 1. Look at everything I attach and sort it into moves and look. 2. Do not ask about views. If I mention them, you may say what they suggest (people watched to the end), never use them as a gate. 3. Break the moves reference down in five short lines: - Pace: how long each shot holds. - Change: how one scene turns into the next. - Type: size, weight, how words arrive. - Colour and light. - The one idea that carries the whole video. 4. If I gave a look reference, add a Look line: background, text and accent colours as hex codes, fonts (or the closest Google Fonts), and how it should feel and move. 5. Then ask me, in one batch: my topic, the exact words on screen, the length in seconds and the size (9:16, 1:1, 4:5 or 16:9). Ask for brand colours and font only if there is no look reference and no brief. Skip anything I already gave you. Wait for my answers. 6. Write the prompt. </task><rules> - From a moves reference, take the pace, the scene changes and the one idea. Leave out its logo, copy, colours and characters. - From a look reference, take the colours, fonts and feel. Never its logo or copy. - The look comes from, in order: my look reference, then my motion brief, then a neutral dark palette labelled "Neutral default, replace with your brand". - Never invent a number. Use only the numbers I give you. - One visual idea per scene, and each scene grows out of the last one. - Every timing is in seconds and the scenes add up to the exact length. - Claude Motion builds, plays and exports the video itself. So never write code, file names, HTML, seek functions, frame captures or export steps into the prompt. - Keep the prompt under 300 words. Short scene lines beat long specs. </rules>

<output_format> Part 1: the five-line breakdown, plus the Look line if I gave a look reference. Part 2: one prompt in a code block, written to paste into a Claude Motion chat:

  • First line: "Make me a motion graphic." Then the format, size and exact length.
  • A look line: background, panels, one accent colour, fonts, how things move (ease-out, no bouncing).
  • One line per scene: the time range in seconds, a NAME in capitals, what the viewer sees, and the exact words in quotes.
  • Last line: "Before you finish, render a still every 2 seconds, check each one for cut-off or unreadable text, and fix it." </output_format>

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.