PlugWiki

find-animation-opportunities Skill: Where Your UI Should (and Should Not) Animate

Makes your agent scan an interface for the few places that should animate, and reject the many that should not.

Installs
225.2K
on skills.sh
Stars
52.7K
on GitHub
Updated
Oct 2026
last repo commit

Every candidate has to pass four questions in order: how often users see it, what purpose the motion serves, whether it fits inside the time budget, and whether motion helps or hurts there. Anything used 100 or more times a day, such as keyboard shortcuts or a command palette, is rejected.

The report has three parts: a table of at most 5 to 7 suggestions with exact curves, durations and properties, a required list of 2 to 5 rejected candidates, and a verdict. The skill is read-only and does not edit code. Invoked with no question, it answers with one line and waits.

Good for

  • Front-end developers asking "what could be animated here?"
  • Designers who want restraint, not a wishlist of effects
  • Teams that want exact easing and timing values for each suggestion

Install find-animation-opportunities

Claude Code

  1. 1

    Copy this prompt.

    Install the find-animation-opportunities skill in Claude Code. Run this command:

npx skills add https://github.com/emilkowalski/skills --skill find-animation-opportunities

Then check that it loaded and tell me how to use it.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Requires Node.js.

From its listing on skills.sh. Source.

What's in the skill

When it loads

Search a codebase or UI for places that don't animate but should, and reject everything that shouldn't. Read-only; it proposes motion with exact values, it does not implement it. Use when the user asks "what could be animated here?" or wants to "make this feel more alive". For fixing existing animations, use improve-animations or review-animations instead.

Sections in SKILL.md

  1. Initial Response
  2. Operating Posture
  3. Hard Rules
  4. The Gate
  5. 1. Frequency — how often will a user see this?
  6. 2. Purpose — why does this animate?
  7. 3. Speed — can it stay inside budget?
  8. 4. Function — does motion help or hinder here?
  9. Where to Hunt
  10. Workflow
  11. Required Output Format
  12. Part 1 — Opportunities table
  13. Part 2 — Rejected candidates (REQUIRED)
  14. Part 3 — Verdict
  15. Tone

Key facts

Author
Emil Kowalski
License
MIT, from the crawl of the repo
Installs on skills.sh
225,195 (Nov 2, 2026)
GitHub stars
52,705 for the emilkowalski/skills repo (Nov 2, 2026)
Last repo commit
Oct 28, 2026
What installs
One SKILL.md; no bundled scripts or reference files
Needs
Access to your code or UI to read

What it includes

  • Finds the stack, motion libraries, easing tokens and product personality

    New suggestions must extend existing tokens.

    Files · Recon

  • Looks at 6 seams, from feedback gaps to gesture seams and the delight budget

    Seams: feedback gaps, teleporting state, missing spatial story, group entrances, gesture seams, delight budget.

    Files · Sweep the hunt list

  • Four questions: frequency, purpose, speed, function

    A suggestion that fails any question is dropped.

    The Gate

  • Up to 5 to 7 rows with location, purpose, frequency and exact motion values

    Values include curve, duration and properties.

    Part 1: Opportunities table

  • Lists 2 to 5 places deliberately not animated, with the gate question that failed

    Required in every report.

    Part 2: Rejected candidates

  • Says how much motion the UI needs and names the single best suggestion

    Points to improve-animations plan for turning a row into an implementation plan.

    Part 3: Verdict

From the official docs

Questions

What does find-animation-opportunities do?

It looks through your code or UI for moments that would benefit from motion and gives a precise recipe for each. It also tells you what it rejected and why.

How do I install it in Claude Code, the Claude app or Codex?

Use the install box above. The skill is one text file. The author does not list specific clients.

Does it change my code?

No. It is read-only and tells you to hand any suggestion to improve-animations or another agent to build.

Does it need an API key?

SKILL.md mentions no key.

Is it safe?

It bundles no scripts and its rules say never to modify source code. It does read your repository, and its rules treat file contents as data, not instructions.

How is it different from improve-animations and review-animations?

This skill finds places that should animate but do not. The SKILL.md says improve-animations audits and plans fixes to existing motion, and review-animations reviews a single diff.

Information

updated Nov 2, 2026

Repository
emilkowalski/skills
Folder
skills/find-animation-opportunities

emilkowalski/skillsskills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 3
  1. emilkowalski/skills find-animation-opportunities SKILL.md · github.com
  2. improve-animations SKILL.md · github.com
  3. review-animations SKILL.md · github.com

Updated Nov 2, 2026.