gsap-timeline
greensock/gsap-skills · Agent Skill
Official GSAP timeline guidance for sequencing, position parameters, labels, nesting, and playback control with gsap.timeline().
Jump to install ↓Overview
| Publisher | |
|---|---|
| Repository | greensock/gsap-skills ↗ |
| Skill folder | gsap-timeline |
| Stars | 17,196 |
| Forks | 1,046 |
| Bundled files | 1 |
| License | MIT |
| Last updated | July 29, 2026 |
| Links | Skill source ↗ · Repository ↗ |
Mozgi check
What we found in the skill files. Details come with a subscription.
Installation
A skill is a folder with a SKILL.md file. Pick your agent and run the commands in a terminal (macOS, Linux or Git Bash on Windows) from your project root.
Copy the prompt into Claude, Codex or another assistant: it will review the skill and install it for you.
Install the “gsap-timeline” skill from mozgi.io (https://mozgi.io/skills/greensock-gsap-timeline/) for me. 1. Download the archive: https://mozgi.io/skills/greensock-gsap-timeline/download If it fails, take the skill folder from the source: https://github.com/greensock/gsap-skills/tree/main/skills/gsap-timeline 2. Read SKILL.md and the other files. Check the skill is safe: no hidden commands, no sending data elsewhere, no scripts doing something other than described. If anything looks suspicious, stop and tell me. 3. Put the “gsap-timeline” folder into your agent's skills folder: .claude/skills/ for Claude Code, .agents/skills/ for Codex, .cursor/skills/ for Cursor, .gemini/skills/ for Gemini CLI. Inside the project if we are in one, otherwise in the home folder (~/.claude/skills/ etc.). 4. Make sure <skills folder>/gsap-timeline/SKILL.md exists. 5. Briefly tell me what this skill does and offer to try it on my task. If you cannot do a step yourself, tell me what to click or type.
git clone --depth 1 --branch main https://github.com/greensock/gsap-skills.git /tmp/gsap-skills mkdir -p .claude/skills cp -r /tmp/gsap-skills/skills/gsap-timeline .claude/skills/gsap-timeline
Restart Claude Code — the skill appears in the list; call it manually with /gsap-timeline. For all projects use ~/.claude/skills.
git clone --depth 1 --branch main https://github.com/greensock/gsap-skills.git /tmp/gsap-skills mkdir -p .agents/skills cp -r /tmp/gsap-skills/skills/gsap-timeline .agents/skills/gsap-timeline
Codex looks for skills in .agents/skills from the current folder up to the repo root; call one with /skills or $gsap-timeline. For all projects use ~/.agents/skills.
git clone --depth 1 --branch main https://github.com/greensock/gsap-skills.git /tmp/gsap-skills mkdir -p .cursor/skills cp -r /tmp/gsap-skills/skills/gsap-timeline .cursor/skills/gsap-timeline
Cursor picks the skill up on start; call it with “/” in Agent chat. Cursor also reads .claude/skills and .agents/skills. For all projects use ~/.cursor/skills.
git clone --depth 1 --branch main https://github.com/greensock/gsap-skills.git /tmp/gsap-skills mkdir -p .gemini/skills cp -r /tmp/gsap-skills/skills/gsap-timeline .gemini/skills/gsap-timeline
Gemini CLI offers to activate the skill when a task matches — you approve it. For all projects use ~/.gemini/skills.
Read SKILL.md and any companion files before deciding whether to install. Click a file to preview it.
SKILL.md contents
Original author text · read-onlyGSAP Timeline
When to Use This Skill
Apply when building multi-step animations, coordinating several tweens in sequence or parallel, or when the user asks about timelines, sequencing, or keyframe-style animation in GSAP.
Related skills: For single tweens and eases use gsap-core; for scroll-driven timelines use gsap-scrolltrigger; for React use gsap-react.
Creating a Timeline
const tl = gsap.timeline();
tl.to(".a", { x: 100, duration: 1 })
.to(".b", { y: 50, duration: 0.5 })
.to(".c", { opacity: 0, duration: 0.3 });
By default, tweens are appended one after another. Use the position parameter to place tweens at specific times or relative to other tweens.
Position Parameter
Third argument (or position property in vars) controls placement:
- Absolute:
1— start at 1 second. - Relative (default):
"+=0.5"— 0.5s after end;"-=0.2"— 0.2s before end. - Label:
"labelName"— at that label;"labelName+=0.3"— 0.3s after label. - Placement:
"<"— start when recently-added animation starts;">"— start when recently-added animation ends (default);"<0.2"— 0.2s after recently-added animation start.
Examples:
tl.to(".a", { x: 100 }, 0); // at 0
tl.to(".b", { y: 50 }, "+=0.5"); // 0.5s after last end
tl.to(".c", { opacity: 0 }, "<"); // same start as previous
tl.to(".d", { scale: 2 }, "<0.2"); // 0.2s after previous start
Timeline Defaults
Pass defaults into the timeline so all child tweens inherit:
const tl = gsap.timeline({ defaults: { duration: 0.5, ease: "power2.out" } });
tl.to(".a", { x: 100 }).to(".b", { y: 50 }); // both use 0.5s and power2.out
Timeline Options (constructor)
- paused: true — create paused; call
.play()to start. - repeat, yoyo — same as tweens; apply to whole timeline.
- onComplete, onStart, onUpdate — timeline-level callbacks.
- defaults — vars merged into every child tween.
Labels
Add and use labels for readable, maintainable sequencing:
tl.addLabel("intro", 0);
tl.to(".a", { x: 100 }, "intro");
tl.addLabel("outro", "+=0.5");
tl.to(".b", { opacity: 0 }, "outro");
tl.play("outro"); // start from "outro"
tl.tweenFromTo("intro", "outro"); // pauses the timeline and returns a new Tween that animates the timeline's playhead from intro to outro with no ease.
Nesting Timelines
Timelines can contain other timelines.
const master = gsap.timeline();
const child = gsap.timeline();
child.to(".a", { x: 100 }).to(".b", { y: 50 });
master.add(child, 0);
master.to(".c", { opacity: 0 }, "+=0.2");
Controlling Playback
- tl.play() / tl.pause()
- tl.reverse() / tl.progress(1) then tl.reverse()
- tl.restart() — from start.
- tl.time(2) — seek to 2 seconds.
- tl.progress(0.5) — seek to 50%.
- tl.kill() — kill timeline and (by default) its children.
Official GSAP Best practices
- ✅ Prefer timelines for sequencing
- ✅ Use the position parameter (third argument) to place tweens at specific times or relative to labels.
- ✅ Add labels with
addLabel()for readable, maintainable sequencing. - ✅ Pass defaults into the timeline constructor so child tweens inherit duration, ease, etc.
- ✅ Put ScrollTrigger on the timeline (or top-level tween), not on tweens inside a timeline.
Do Not
- ❌ Chain animations with delay when a timeline can sequence them; prefer
gsap.timeline()and the position parameter for multi-step animation. - ❌ Forget to pass defaults (e.g.
defaults: { duration: 0.5, ease: "power2.out" }) when many child tweens share the same duration or ease. - ❌ Forget that duration on the timeline constructor is not the same as tween duration; timeline “duration” is determined by its children.
- ❌ Nest animations that contain a ScrollTrigger; ScrollTriggers should only be on top-level Tweens/Timelines.
Frequently asked questions
What does the gsap-timeline skill do?
Official GSAP timeline guidance for sequencing, position parameters, labels, nesting, and playback control with gsap.timeline().
How do I install gsap-timeline?
Open the “Installation” block on this page and pick your agent — Claude Code, Codex, Cursor or Gemini CLI — for ready-made commands that copy the skill folder to the right place. Or copy the prompt from the “Via assistant” tab and let the assistant review and install the skill.
Which AI models work with gsap-timeline?
Skills are plain Markdown instructions (the Agent Skills format), so gsap-timeline works with any agent that reads SKILL.md: Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and more. The model loads the instructions only when a task matches the skill's description.
Is gsap-timeline free?
The skill is published openly by greensock under the MIT license. The skill itself costs nothing — you only pay your AI provider for the tokens you use.
Is it safe to install skills?
A skill is a set of instructions your agent will follow, so read SKILL.md and its companion files before installing. Scripts in the skill folder only run if your agent runs them — keep an eye on what it does and do not grant unnecessary permissions.
How is a skill different from an MCP server or a plugin?
An MCP server or plugin gives the model new tools — code that runs and returns a result. A skill gives it knowledge and process: how to approach a task, which steps to follow and what good output looks like. It needs no server or API key.