Tessl • The package manager for agent skills

SkillPublic

gsap-performance

Official GSAP skill for performance — prefer transforms, avoid layout thrashing, will-change, batching. Use when optimizing GSAP animations, reducing jank, or when the user asks about animation performance, FPS, or smooth 60fps.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

67%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.

The body is a tight, scenario-organized set of performance directives with executable snippets for quickTo and will-change, and it appropriately lives in a single file with no external references. Its main flaw is redundancy: the closing 'Best practices' and 'Do Not' sections restate earlier sections almost word-for-word, and the central transform guidance lacks a code example.

Suggestions

Merge the 'Best practices' and 'Do Not' recap sections into the topic sections they duplicate — every bullet in them restates guidance already given verbatim in 'Prefer Transform and Opacity', 'Many Elements', and 'ScrollTrigger and Performance'.

Add a minimal executable transform example alongside the quickTo one (e.g. gsap.to('.el', { x: 100, duration: 0.3 })) so the skill's core recommendation has copy-paste code too.

Consider a brief diagnostic ordering at the top (identify the jank source — layout, paint, or too many active tweens — then apply the matching section) to give the scenario sections a clear sequence.

Dimension	Reasoning	Score
Conciseness	The topic sections are lean and imperative with no concept-explanation padding, but the 'Best practices' and 'Do Not' sections recap earlier sections nearly verbatim (~15 of 75 lines of pure duplication: 'Animate transform and opacity; use will-change...', 'Use stagger instead of many separate tweens...', 'Animate width/height/top/left...'), which could be trimmed.	3 / 5
Actionability	Concrete ✅/❌ property lists, copy-paste-ready quickTo and will-change: transform snippets, and specific API calls (stagger, scrub: 1, ScrollTrigger.refresh(), pin: true). Minor gaps: the core transform recommendation and stagger have guidance but no executable code example, unlike quickTo.	4 / 5
Workflow Clarity	This is a guidance/reference skill rather than a multi-step process, and each section is unambiguously organized by scenario (movement, mouse followers, lists, scroll) with clear do/don't directives and no risky operations needing validation. It falls short of 5 because there is no diagnostic ordering (e.g., identify the jank source first, then apply the matching fix).	4 / 5
Progressive Disclosure	A well-sectioned single-file body with no external file references — and none are needed at this size (the sibling-skill mentions gsap-core/gsap-timeline/gsap-scrolltrigger are cross-skill pointers, not broken paths). The duplicated recap sections are the only organization gap keeping it below 5.	4 / 5
	Total	15 / 20 Passed

Description

87%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.

A strong description: it states concrete techniques for what the skill covers, gives an explicit 'Use when...' clause with natural trigger phrases, and is tightly scoped to GSAP performance. The only weaknesses are minor — two techniques are named as keywords rather than actions, and a few common synonyms (laggy, stutter) are absent.

Dimension	Reasoning	Score
Specificity	Names the domain (GSAP animation performance) and lists several concrete techniques — 'prefer transforms, avoid layout thrashing, will-change, batching' — though 'will-change' and 'batching' are noun fragments rather than stated actions, leaving minor coverage gaps versus the comprehensive 5 anchor.	4 / 5
Completeness	Explicitly answers both what ('prefer transforms, avoid layout thrashing, will-change, batching') and when ('Use when optimizing GSAP animations, reducing jank, or when the user asks about animation performance, FPS, or smooth 60fps') with concrete trigger phrases. Third-person voice is maintained throughout.	5 / 5
Trigger Term Quality	Natural phrases users would say are present: 'optimizing GSAP animations', 'reducing jank', 'animation performance', 'FPS', 'smooth 60fps'. A few common synonyms like 'laggy', 'stutter', or 'slow animation' are missing, so it falls just short of the comprehensive 5.	4 / 5
Distinctiveness Conflict Risk	A clear niche (GSAP performance specifically) with distinct triggers — GSAP, jank, 60fps, layout thrashing — anchored by the GSAP name, so conflict with generic animation or CSS-performance skills is minimal.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nexu-io/open-design
Path: skills/gsap-performance/SKILL.md
Revision: 78d5637

Reviewed: 5 days ago

Discovery Implementation Validation

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.

gsap-performance

Table of Contents

Is this your skill?