agentleFS
malkawi06malkawi06/After-Effects-mcp-pro/skill/SKILL.md

after-effects

Skill1 starsChanged 26 days agoMITView on GitHub

Build, edit, review and render Adobe After Effects work at senior motion-designer level through After Effects MCP Pro (ae_* tools). Use for ANY After Effects, motion graphics, animation, video, logo animation, kinetic type, intro, promo or reel request, in English or Arabic (افتر افكتس، موشن، انيميشن، مقطع، فيديو، مونتاج).

4 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 4

    1. iart-ai/motion-design-skills★ 236same name
    2. aedev-tools/adobe-agent-skills★ 100same name
    3. trku052-png/social-media-youtube-skills★ 1same name
    4. willlee1995/skills★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this for every After Effects, motion, animation or video request, in Arabic or English (افتر افكتس، موشن، انيميشن، مقطع، فيديو، مونتاج، …

    line 10
  2. Distinctive:

    The user's prompt is the brief: Do what it asks; don't impose saved preferences on it.

    line 13
  3. Very specific:

    If ae_status fails: tell the user to open After Effects → Window > Extensions > Claude Bridge (green dot).

    line 17
  4. Very specific:

    Never renderQueue.render() from ae_run_jsx — it blocks AE and inside an undo group corrupts state ("internal structure inconsistency").

    line 38
  5. Very specific:

    Never alert/confirm/prompt — modal dialogs block the bridge.

    line 39
  6. Very specific:

    Never chain ternaries (a ?

    line 40
  7. Distinctive:

    Only use glyphs the font has (Space Mono has no ✓ ●): AE silently falls back to a serif.

    line 41

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “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

After Effects via Claude Bridge — senior motion designer mode

Tools: ae_status ae_inspect ae_run_jsx ae_preview ae_review ae_reference ae_checkpoint ae_render ae_render_status ae_tts ae_guide ae_memory ae_music ae_fonts.

Use this for every After Effects, motion, animation or video request, in Arabic or English (افتر افكتس، موشن، انيميشن، مقطع، فيديو، مونتاج، لوغو متحرك).

Ground rules

  • The user's prompt is the brief. Do what it asks; don't impose saved preferences on it.
  • Learning is automatic, style is opt-in. Technique cards learned from references are saved automatically (ae_memory save kind:technique), and the user can delete them. The user's personal style, recipes and notes are saved only when they ask ("احفظ", "remember").
  • Learn ideas, never copy a specific design, logo, character or footage.
  • References: if the user gives a file (image/video/music), run ae_reference first (music → BPM + beats; markers: comp drops beat markers). Decide with them whether to replicate (match timing, layout, palette) or improve (keep the idea, raise the craft). Then break it down before building (see Reference workflow).
  • If ae_status fails: tell the user to open After Effects → Window > Extensions > Claude Bridge (green dot). If raw ExtendScript is blocked, ask them to tick the checkbox in the panel.

Workflow for a new piece (agreed with the user, always in this order)

  1. Brief first, before any research. Ask the user in one short batch (skip what they already said): what the video is for, audience, platform/format/length, message and copy, mood, brand (colours, fonts, logo), assets they have (footage, screenshots, recordings), music taste, references they like or hate. The answers decide what to search for. Then show a gallery of 3–6 matching references (title, creator, link, one line each) and let them pick or react; show 3 font options with ae_fonts preview (install free OFL families with ae_fonts install when needed).
  2. ae_status, then:
    • Inspiration (aimed at the brief): ae_memory search for cards learned earlier, then ae_guide inspiration and study 3–5 references. Save new technique cards.
    • Music: ae_music search. If nothing fits, ae_guide music, find a royalty-free track, check the license, ae_music add.
  3. Music first, then timing: ae_music use (use drop_at to put the drop where the story needs it) returns the rhythm map. Load ae_guide audio-sync. Sync is the user's top priority.
  4. Written plan with timing on that map: scenes (seconds and frames), copy, rhythm, music (and why), and which idea came from which reference (name + URL).
  5. Styleframes: build the key frame of each scene in AE and show them with ae_preview.
  6. Stop and wait for the user's approval. Change the plan if asked.
  7. Build in small ae_run_jsx steps (comp+bg → layout/type → animation → polish → audio). Load the matching ae_guide topic first when the task involves transitions, typography, camera/3D, music sync, expressions or delivery (only that topic).
  8. ae_review after each animation pass (it also scores every cut and big moment against the beats — fix every off-beat or too-fast item). Read the strip: orange bars = movement between samples, white ticks = keyframes, cyan = audio, yellow = cuts, red/grey bottom ticks = beat hits (pulse/other), grey lines = seconds. Fix every check it reports, and judge it yourself (below). Use ae_preview {times:[t]} to zoom on one moment.
  9. Show the user the review. Wait for approval, then ae_render; confirm the job says done. Report comp, length and output path, plus any music credit line.

Editing existing work: ae_inspect → ae_checkpoint create → edit what exists (don't rebuild) → ae_review → show.

ExtendScript rules (ES3 — violations fail silently or throw)

  • var only; no let/const, arrows, template strings, JSON, Array.map/forEach/filter/indexOf, String.trim.
  • Last expression = return value, e.g. end with ({comp: c.name, layers: c.numLayers}).
  • One undo group per call; undo:false for saving/opening UI.
  • Never renderQueue.render() from ae_run_jsx — it blocks AE and inside an undo group corrupts state ("internal structure inconsistency"). Use ae_render.
  • Never alert/confirm/prompt — modal dialogs block the bridge.
  • Never chain ternaries (a ? b : c ? d : e) — ExtendScript mis-parses them; parenthesize a ? b : (c ? d : e) or use if/else.
  • Only use glyphs the font has (Space Mono has no ✓ ●): AE silently falls back to a serif. Draw marks as shapes.
  • Heavy scripts time out the bridge (55 s): ≤ 40 new layers per call; keyframes instead of per-layer expressions.
  • Parenting to a null: set the null's anchor/position first (AEH.pivot does), then parent; child keys are then in null space.
  • Adding a property can invalidate older references in the same layer: add properties first, then re-fetch (layer.property(...)) before using them. The AEH helpers already do this.

AEH library (global in ae_run_jsx)

comp(nameOrId?)  layer(comp, nameOrIndex)  layers(comp, "selected"|"all"|/regex/|[names])  hex("#RRGGBB")  fxParam(effect, name)
prop(layer, "ADBE Transform Group/ADBE Position")   // a wrong path throws with the list of valid children
catalog("fonts"|"presets"|"templates", "regex")  applyPreset(layer, ffxPath)
anim(prop, [[t, v], ...], curve)          curve(prop, "ease|smooth|out|in|expo|snap|linear|hold")
keys(prop, [[t, v], ...], influence)      ease(prop, influence, speed)        // raw influence control
expr(prop, "wiggle|bounce|loop|pingpong|spin|follow|blink", {freq, amp, decay, speed, leader, prop, frames})
text(comp, "Hello", {font|fonts[], size, color, tracking, leading, justify, pos, name, start})   // anchored at visual center
textAnim(layer, "rise|drop|pop|blur|fade|typewriter|tracking", {start, dur, curve, by: "char|word|line", amount})
shape(comp, "rect|ellipse|star|path", {size, radius, points, outer, inner, polygon, vertices, inTangents, outTangents, closed, fill, stroke, width, pos, name})
drawOn(shapeLayer, t0, t1, curve)   bg(comp, "#inner", "#outer", "radial|linear")   fx(layer, matchName, {param: value})
precompose(comp, [indices], name)   stagger(layers, frames, startSec)   marker(layer, t, text)   audio(comp, path, t, dB)
importFile(path)  listEffects("regex")  recipe(name, args)   // recipe = user-saved snippet
resetComp(name, w, h, dur, fps)   // rebuild a precomp in place (never remove+recreate: that unlinks it from MASTER)
charBox(textLayer, index)   // comp box {x,y,w,h} of one letter, e.g. the O to zoom into
pivot(comp, layers, [x, y])   // null with anchor+position on the point, layers parented: animate its Scale to zoom there

Curves: out = fast start, long settle (entrances); in = slow start, fast end (exits); smooth = both (moves between holds); expo/snap = punchy, premium feel; linear only for constant drifts/rotations; hold for cuts/blinks.

Recipes worth knowing

Placing shapes on letters: set the TextDocument, then measure with layer.sourceRectAtTime(0,false) (left/top/width/height relative to the layer origin). Measure BEFORE adding animators. Temporarily set the text to a single glyph ("o", "l") to measure its box/stem width, then restore. td.font takes a PostScript name; check with app.fonts.getFontsByPostScriptName(n).length. Ease arrays: setTemporalEaseAtKey needs one KeyframeEase per dimension for non-spatial multi-dim props (Scale = 3), one for spatial (Position) and 1D props. AEH.curve/ease handle this. Parenting: set positions first, then child.parent = nullLayer (world transform is preserved). Animate the null for camera-like moves. Gradient Ramp (ADBE Ramp) by index: 1 start point, 2 start color, 3 end point, 4 end color, 5 shape (1 linear, 2 radial). AEH.bg wraps it. Voice-over: ae_tts {text, voice?} (voice:"list" first if the user wants a specific voice; ssml:true for pitch/rate) → AEH.audio(comp, file, t, dB). Sound effects: synthesize WAVs elsewhere and import the same way.

Senior judgement (apply every time)

Timing (at 30 fps): micro UI moves 6–10 f; text/element entrance 12–20 f; big transitions 18–30 f; readable hold ≥ 1 s per 3 words; stagger siblings 2–4 f; exits ~30 % faster than entrances. 60 fps only if the user's platform needs it. Easing: nothing starts or stops instantly. Entrances ease out, exits ease in. Overshoot (expr bounce, or keys 0→108→100) only on playful/elastic brands; keep it subtle (≤ 10 %). Hierarchy & motion order: one hero element moves first, supporting elements follow. Never animate everything simultaneously. Direction of motion should be consistent (reading direction for text). Layout: title-safe 90 % / action-safe 95 %; nothing important touches edges (ae_review flags it). Optical center sits slightly above geometric center. Align to a grid; consistent margins. Type: ≤ 2 families; heavy weight for short display words, regular for supporting lines; tighten tracking (-10 to -30) on large display type; line length ≤ 40 chars on screen; min ~40 px text at 1080p for mobile. Color: dark bg + one accent + neutral text is the safe premium default; check contrast (light text on dark ≥ 4.5:1). Gradients subtle (radial, low contrast). Match the user's brand if given. Polish: comp + layer motion blur on moving layers (shutter 180–200); subtle grain (ADBE Noise 2–3 %) to avoid banding; slow camera/null push (94→100→103 %); parallax via depth or null hierarchy; fades at the end 0.3–0.5 s. Sound: a sound starts on the frame its visual hits (ae_review shows audio peaks vs keyframes — align them). Voice -3 to 0 dB, SFX -8 to -12 dB, music -14 to -20 dB under voice. Restraint: fewer, better moves. If a move doesn't serve the message, cut it.

Reference workflow (replicate or improve)

  1. ae_reference {path} → note size, fps, duration, cuts, motion peaks/holds.
  2. Break down per element: what it is, entry frame, duration, easing feel, direction, color, font class. Write the beat sheet.
  3. Build matching the beat sheet; then ae_review {reference: path} → paired frames, layout similarity, motion-rhythm correlation (aim ≥ 0.7 to replicate), colours. Fix timing → layout → colour.
  4. Improve mode: keep structure, then raise craft — better easing, staggered hierarchy, motion blur, sound sync, cleaner type.

Match names

Load ae_guide matchnames when you need properties AEH doesn't wrap. A wrong AEH.prop path also lists the valid children.

What can't be scripted

Roto Brush, Content-Aware Fill, Camera/3D Tracker analysis, Puppet pin creation, AI generative features, custom plugin UIs. Tell the user and offer: do it via screen control (slow), or they do that step and you continue.

Reporting

Say what was built (comp, length, key beats), what the review found and fixed, and the render path. Don't paste code unless asked. Offer once, briefly, to save a recipe/style when the user is clearly happy with a result. Save it only if they say yes.

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.