More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    ScrollProof

    0

    Audit GSAP, ScrollTrigger, and reveal animations for breakage, layout shifts, and performance jank.

    $2

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    ScrollProof

    ScrollProof

    Example session with this skill installed

    Audit my local Vite site at http://localhost:5173 for scroll jank and check why the hero section isn't pinning correctly.

    • Read your context and instructions
    • Compiled the scrollproof
    • Generated the document

    I have completed the scroll-driven animation audit for your local dev server.

    Summary: Score 74/100. Found 2 errors and 3 warnings. The hero section fails to pin because the end trigger is unreachable.

    Animation Audit Report

    #SeverityScrollElementIssueSource
    1ERROR0pxsection.heroBroken pin: trigger end precedes start/src/components/Hero.tsx:42
    2ERROR1450pxdiv.reveal-boxContent flash: opacity 1 before intro/src/styles/main.css:112
    3WARN800pximg.parallaxLayout shift: missing height/widthindex.html:22
    4WARN2200pxnav.stickyForced reflow during scroll event/src/hooks/useScroll.js:15
    5WARN-GSAP Engine2 stale ScrollTriggers detectedN/A

    Technical Analysis

    The error in Hero.tsx at line 42 is caused by a ScrollTrigger where the end value evaluates to a position above the start position. This usually happens when the trigger element has no height or the end marker is calculated before images load. In main.css, the reveal-box lacks an initial visibility: hidden or opacity: 0 in the base CSS, causing it to flicker before GSAP takes control.

    The performance trace shows significant jank (dropping to 42fps) at the 2200px mark due to a scroll listener in useScroll.js triggering a layout-heavy getBoundingClientRect() call.

    Next steps

    1. Add opacity: 0 to .reveal-box in src/styles/main.css to prevent FOUC.
    2. Review the end calculation in Hero.tsx line 42; ensure the trigger element has a defined height.
    3. Open .scrollproof/localhost-5173/report.html in your browser to view the frame-time chart.

    Hero.tsx

    PDF · document

    Generated

    Example file from a real run - the skill writes it into your workspace.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Scroll-driven animations often fail silently, causing layout shifts, broken pins, or elements that never reveal. This skill objectively audits your site in a headless browser to identify exactly where and why GSAP, ScrollTrigger, or native scroll effects break.

    What it does

    • Automated scrolling simulates user behavior across different viewport sizes and CPU speeds.
    • State capture records every animated element's properties at specific scroll intervals.
    • Performance tracing detects jank, forced reflows, and layout shifts during scroll.
    • Engine inspection probes GSAP and ScrollTrigger instances for stale or unreachable triggers.
    • Visual auditing captures annotated screenshots of broken pins and content flashes.

    How it works

    1. Environment check verifies the presence of Node.js and a Chromium-based engine.
    2. Audit execution runs the CLI against a local dev server or live URL with optional throttling.
    3. Data collection generates a performance trace and a detailed report in a local directory.
    4. Issue reporting summarizes errors by severity, scroll position, and source file line.

    Frameworks & tools

    This tool targets sites using GSAP, ScrollTrigger, Lenis, and standard CSS reveal-on-scroll effects. It requires Node.js 18.17+ and Playwright Chromium.

    Why this beats prompting it yourself

    Generic LLM prompts cannot see "invisible" animation states or feel frame-rate drops. This skill uses a real browser engine to track the DOM at specific scroll offsets, catching logic errors that don't trigger console logs.

    Use cases

    • Debugging GSAP ScrollTrigger pins that jump or overlap other content.
    • Identifying "invisible" sections caused by opacity tweens that never trigger.
    • Stress-testing scroll performance on simulated mid-range mobile devices.
    • Validating that reveal animations work correctly after a framework migration.

    Known limitations

    Requires a Chromium-based browser installed on the host. Does not support Safari-only WebKit bugs or Firefox-specific rendering issues.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Testing & Debugging.

    Requires local Chromium/Chrome. Only audits scroll-driven logic; cannot fix high-resolution asset loading delays. Best used on local dev servers providing source maps.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 19 days ago

    Software
    Node.jsPlaywright

    Permissions

    Terminal / Shell
    Browser
    Read Files
    Listed19 days ago

    What's inside

    Frequently Asked Questions

    This skill uses a headless Chromium browser to simulate real user scrolling, capturing the exact state of GSAP markers and CSS properties to identify invisible elements, broken pins, and performance-sapping layout shifts.

    While optimized for GSAP and ScrollTrigger, the skill effectively audits any scroll-driven logic, including Lenis smooth scrolling, CSS Intersection Observer effects, and standard reveal-on-scroll animations.

    You will receive the full skill package including the automated audit scripts, CLI integration tools, and documentation for generating localized performance reports.

    The skill requires Node.js 18.17 or higher and Playwright Chromium; it is designed to run against both local development servers and live production URLs.

    Yes, the skill allows you to simulate specific CPU throttling and viewport dimensions, making it easy to catch jank and layout shifts that only occur on mid-range mobile devices.

    Updates are periodically released to maintain compatibility with new GSAP versions and Playwright engine updates, ensuring the audit logic remains accurate as web standards evolve.

    New in Testing & Debugging