CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

animation-performance

Keep web animations inside the frame budget — animate composite-only properties, keep motion off the main thread when the page is busy, and find the cause when an animation drops frames. Covers the layout/paint/composite pipeline, cheaper property swaps, CSS vs WAAPI vs requestAnimationFrame, Motion's hardware-accelerated path, React re-rendering per frame, inherited CSS variable recalculation, blur cost, and when `will-change` actually helps. Use when an animation is janky, choppy, stutters, or drops frames; when choosing which property to animate; when deciding between CSS and JS animation on performance grounds; or when reaching for `will-change` or GPU layers. For choosing easing, duration, or whether to animate at all use animate; for reviewing motion as a whole use review-animations.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is animation-performance in emilkowalski/skills

SKILL.md
Quality
Evals
Security

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A strong diagnostic body with exceptional actionability — symptom tables, concrete thresholds, executable snippets, and a validated three-phase workflow. Its main weakness is token efficiency: persona framing, an anecdote section, a scripted greeting, and re-explanations of rendering basics Claude already knows dilute genuinely non-obvious material such as the Motion version behavior and inherited CSS variable trap.

Suggestions

Remove the 'Initial Response' scripted greeting, the 'Why This Matters' anecdote, and the 'Operating Posture' persona narrative, keeping only the operative bar (mid-range phone as the target device, 8ms budget on 120Hz).

Cut explanations of rendering fundamentals Claude already knows (layout/paint/composite definitions, why transform avoids re-measurement, CSS variable inheritance, rAF running on the main thread) and keep only the non-obvious specifics: motion 14.2 shorthand acceleration, the inherited CSS variable trap, the sub-20px blur limit in Safari, and the box-shadow to drop-shadow swap.

Move the case studies (Vercel's tab indicator, Vaul's drawer drag, Sonner) and the Motion version-compatibility details into a references/ file linked from the relevant sections, shortening SKILL.md and adding well-signaled one-level-deep references.

DimensionReasoningScore

Conciseness

Mostly efficient — the symptom table, tier/swap tables, and version-specific Motion details are dense and non-obvious — but there is more than minor over-explanation: a scripted 'Initial Response' greeting, the 'Why This Matters' anecdote, the 'Operating Posture' persona framing, and re-teachings of concepts Claude already knows ('Layout: calculate the size and position of every element', 'CSS variables inherit, so changing one on a parent triggers style recalculation for every child', 'JavaScript always runs on the main thread'). Fits the 3 anchor ('mostly efficient but includes some unnecessary explanation or could be tightened') better than 4, where over-explanation would be only minor.

3 / 5

Actionability

Fully executable guidance throughout: a nine-row symptom-to-fix table, a concrete property-swap table (width/height to scale(), box-shadow to filter: drop-shadow()), copy-paste-ready jsx/js/css snippets, hard thresholds (16.7ms/8ms budget, blur under 20px, motion 14.2+), named tooling (DevTools Performance and Animations panels, remote debugging), and a structured report format with file:line examples. Specific examples cover the common cases, matching the 5 anchor.

5 / 5

Workflow Clarity

A clear three-phase workflow (inventory animations in a table, diagnose via a likelihood-ordered checklist, report via a template) with explicit validation: 'Confirm with a recording, not by feel', Hard Rule 3 requiring findings to state code-verified vs device-recording-needed, and a 'Verified:' field in the report format. The checklist's final item ('Still shifting or stuttering? Now add will-change') acts as a fallback iteration. This is a read-only diagnostic skill, so the destructive/batch validation cap does not apply; the sequence matches the 5 anchor.

5 / 5

Progressive Disclosure

No bundle files exist and the single body is well-sectioned, with the symptom table acting as an internal index ('Start here. Match what the user is seeing, then read the matching section'). However, at roughly 217 lines it exceeds the under-50-line simple-skill exception for scoring 5 on sections alone, and content such as the Vercel/Vaul/Sonner case studies and Motion version specifics could live in a one-level-deep reference file. Good structure with minor organization gaps fits the 4 anchor; not 3 since nothing is buried or clearly misplaced.

4 / 5

Total

17

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: concrete actions, a comprehensive and current topic list, natural multi-synonym trigger phrases, and explicit boundary delegation to sibling skills. It is dense rather than padded — every clause carries scope or trigger information.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('animate composite-only properties, keep motion off the main thread when the page is busy, and find the cause when an animation drops frames') plus a comprehensive topic list (layout/paint/composite pipeline, CSS vs WAAPI vs requestAnimationFrame, Motion's hardware-accelerated path, React re-rendering per frame, inherited CSS variable recalculation, blur cost, will-change). Coverage is comprehensive for the domain with no evident gaps, matching the 5 anchor rather than the 4 anchor's 'minor gaps in coverage'.

5 / 5

Completeness

Explicitly answers 'what' (three named actions plus a detailed coverage list) and 'when' with a concrete 'Use when...' clause naming specific trigger phrases — the exact shape of the 5-anchor example. Not 4, because the 'when' clause is already fully explicit and specific rather than needing more detail.

5 / 5

Trigger Term Quality

'Use when an animation is janky, choppy, stutters, or drops frames' provides four natural synonyms for the core symptom, and the remaining triggers ('choosing which property to animate', 'deciding between CSS and JS animation on performance grounds', 'reaching for will-change or GPU layers') name the exact decision moments a user would voice. This matches the 5 anchor's comprehensive synonym coverage; nothing common is missing.

5 / 5

Distinctiveness Conflict Risk

The skill carves a clear niche (animation frame performance) and explicitly delegates to the nearest siblings: 'For choosing easing, duration, or whether to animate at all use animate; for reviewing motion as a whole use review-animations.' Minimal conflict risk, matching the 5 anchor's clear niche with distinct triggers.

5 / 5

Total

20

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

englishstreetventures/osn

Path

.agents/skills/animation-performance/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.