browser-verify

Detect stale frames, manage caches, and measure WebGL GPU performance with Playwright.

5|2|Updated Feb 26, 2026

Search Tags:#browser automation #cache management #performance testing #webgl #stale frame detection

Ready to run

npx skills add https://github.com/AxGord/claude-workflow --skill browser-verify-axgord

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: browser-verify
Source: https://github.com/AxGord/claude-workflow/tree/main/templates/skills/browser-verify
Command: npx skills add https://github.com/AxGord/claude-workflow --skill browser-verify-axgord

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, and includes scripts (resource) components.

What problem does it solve?

This Skill identifies and resolves common pitfalls in browser automation, ensuring web applications behave as expected across different environments and scenarios.

Core Features & Use Cases

Headless Browser Stale Frame Detection: Identifies and avoids issues with headless browser screenshots that can be out of date due to caching.
Headed Browser Stale Frame Detection: Ensures that screenshots from headed browsers are current, even when tabs are not active.
Cache Management: Mitigates issues with Playwright's persistent cache, which can serve stale JavaScript modules.
GPU Performance Measurement: Assesses WebGL performance on mobile devices by comparing desktop and mobile renderers.
Use Case: When developing a high-performance WebGL application, use this Skill to verify that optimizations work as intended across different devices and environments.

Quick Start

Use the browser-verify skill to ensure your WebGL canvas animation renders correctly in a headless browser environment.

Frequently Asked Questions about browser-verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

Why does my Playwright headless browser screenshot show a stale frame?▼

Stale frames in Playwright headless browser screenshots occur due to caching issues. This Skill identifies and resolves these browser-automation pitfalls, ensuring screenshots are current and properly rendered in headless environments.

How do I fix Playwright serving stale JavaScript modules from its persistent cache?▼

To fix Playwright cache management issues with stale JavaScript modules, this Skill mitigates persistent cache problems. It ensures web applications load current modules instead of serving outdated cached scripts during automated interactions.

How do I measure WebGL performance on mobile devices using Playwright?▼

This Skill measures WebGL performance on mobile devices by comparing desktop and mobile GPU renderers. It assesses WebGL performance within Playwright to verify that application optimizations work as intended across different environments.

Do I need Playwright to automate browser verification for WebGL applications?▼

Yes, Playwright is a required dependency for this browser-verification Skill. It relies on Playwright for automated browser interactions to detect and mitigate issues like stale frames and cache management in WebGL applications.

What's the best way to detect stale frames in headed browser screenshots when tabs are inactive?▼

The best way to detect stale frames in headed browsers is using this Skill, which ensures screenshots from inactive tabs are current. It identifies and resolves these headed browser automation issues automatically.

When should I use browser automation verification for headless and headed environments?▼

Use browser automation verification when developing high-performance WebGL applications that must behave consistently. This Skill validates that canvas animations render correctly in both headless and headed browser environments.