CtrlK
BlogDocsLog inGet started
Tessl Logo

gsap-scrolltrigger-storytelling

Build cinematic sticky product storytelling with GSAP ScrollTrigger, progressive UI reveals, scroll-synced animation, smooth interpolation, and immersive section transitions.

60

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./agent-skills/web-design/gsap-scrolltrigger-storytelling/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

The content is concise, well-organized, and appropriately self-contained for a short skill, but it stops short of executable code examples and leaves the Workflow section empty rather than providing a sequenced, checkpointed process.

Suggestions

Fill the '## Workflow' section with an explicit ordered sequence — e.g., wrap in gsap.context() → build the scrubbed ScrollTrigger timeline → pin scenes with labels → refresh after asset load → revert context on unmount.

Add at least one minimal copy-paste-ready GSAP timeline/ScrollTrigger code block so the concrete API names become immediately executable.

Add a validation/checkpoint step such as 'verify pinned section heights after refresh and on matchMedia changes' to catch fragile scroll-layout regressions.

DimensionReasoningScore

Conciseness

The body is lean, well-sectioned, and assumes Claude's competence — it never explains what GSAP or ScrollTrigger is, and every bullet earns its place without padding.

3 / 3

Actionability

It names concrete APIs and techniques ('pin: true', 'gsap.context()', 'matchMedia()', 'quickSetter/quickTo', 'scrub'), but provides no complete, copy-paste-ready code examples, leaving the guidance more instructive than executable.

2 / 3

Workflow Clarity

The '## Workflow' header is empty and implementation guidance reads as a technique list rather than a sequenced process, so an explicit ordered workflow with checkpoints (setup context → build timeline → pin scenes → refresh → cleanup) is missing.

2 / 3

Progressive Disclosure

At ~40 lines with no external references needed and clean section organization, the single-file structure satisfies the rubric's allowance for short skills to score 3 on well-organized sections alone.

3 / 3

Total

10

/

12

Passed

Description

67%

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

The description is specific and occupies a distinct niche, but it omits an explicit use-trigger in the frontmatter and relies on somewhat technical/buzzword language rather than the full range of natural terms a user would say.

Suggestions

Add an explicit 'Use when...' trigger clause to the frontmatter description (e.g., 'Use when the user wants a scroll-driven product story, sticky/pinned scroll sections, or GSAP ScrollTrigger choreography').

Include more natural-language variations users would say ('scroll animation', 'sticky scroll sections', 'pinned sections') alongside the technical GSAP terms.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'sticky product storytelling', 'progressive UI reveals', 'scroll-synced animation', 'smooth interpolation', and 'section transitions' — matching the anchor for several specific concrete actions rather than a partial domain-plus-action listing.

3 / 3

Completeness

It clearly states what the skill does, but the frontmatter description lacks an explicit 'Use when...' trigger clause (that guidance lives only in the body), which per the rubric caps completeness at 2.

2 / 3

Trigger Term Quality

It includes relevant terms like 'GSAP ScrollTrigger' and 'sticky product storytelling', but leans technical and leans on buzzwords ('cinematic', 'immersive') while missing common plain-language variations a user might say, so it stops short of full natural-term coverage.

2 / 3

Distinctiveness Conflict Risk

'GSAP ScrollTrigger' pins the skill to a clear, narrow niche that is unlikely to overlap with unrelated skills or trigger for the wrong one.

3 / 3

Total

10

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
MengTo/Skills
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.