browse-live-site

Verify deployed websites in an authenticated Chromium browser with Playwright.

7|23|Updated Aug 9, 2015
One-click install
npx skills add https://github.com/gamedevpl/www.gamedev.pl --skill browse-live-site
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browse-live-site
Source: https://github.com/gamedevpl/www.gamedev.pl/tree/main/.claude/skills/browse-live-site
Command: npx skills add https://github.com/gamedevpl/www.gamedev.pl --skill browse-live-site

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps agents manually verify deployed websites in a real Chromium browser, including authenticated workflows that API requests or local tests cannot fully validate.

Core Features & Use Cases

  • Authenticated Browser Access: Exchange an agent access token for a signed-in browser session and preserve it with Playwright storage state.
  • Reliable Remote Browsing: Launch the pre-installed Chromium through the required HTTPS proxy with the TLS configuration needed for remote execution environments.
  • End-to-End Site Validation: Explore catalogs, play games, test multiplayer flows, inspect language and navigation behavior, validate error states, and check mobile overflow while collecting console, page, request, and response failures.
  • Use Case: After deploying a game platform change, use this Skill to sign in as the bot agent, play a real catalog game, test its mobile layout, and identify essential network or runtime failures.

Quick Start

Use the browse-live-site skill to sign in as the bot agent, open the live website, and verify the home page, a playable game, key navigation routes, and mobile behavior.

Frequently Asked Questions about browse-live-site

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

FAQPage Schema
How do I run end-to-end testing on a live site with authenticated user sessions?

End-to-end testing on a live site uses Playwright to launch a real Chromium browser, exchanging an agent access token for a signed-in session. This validates authenticated workflows that API requests or local tests cannot fully reach.

Can I test mobile responsive layouts and playable games using Playwright browser automation?

Playwright browser automation supports checking mobile overflow, validating playable games, and testing responsive layouts. It launches Chromium through an HTTPS proxy to manually exercise these real browser flows on deployed websites.

Does browser automation require an HTTPS proxy and TLS configuration for remote execution?

Browser automation requires an HTTPS proxy and TLS 1.2 compatibility for remote execution environments. The pre-installed Chromium launches through this proxy to ensure reliable remote browsing and session preservation.

What is the best way to verify game catalogs and multiplayer lobbies after deploying changes?

Verifying game catalogs and multiplayer lobbies after deployment involves signing in as a bot agent to explore catalogs, play games, and test multiplayer flows. It collects console, page, request, and response failures during validation.

How do I check error routes and signed-out behavior during live site validation?

Live site validation checks error routes and signed-out behavior by navigating through the deployed website in a real browser. The process inspects language behavior, navigation, and error states while collecting runtime problems.

What testing limitations exist when validating deployed websites with local tests instead of a real browser?

Local tests cannot fully validate authenticated workflows or end-to-end site behavior on deployed websites. A real Chromium browser is required to preserve signed-in session states and collect runtime network failures accurately.