skills.rest
yulonghe97
yulonghe97COMMUNITY
Explore all skills by this author →
𝕏@yulong_97GitHub

browse

Control a Chromium session to navigate, interact, and validate UI behavior.

8|1|Updated Apr 8, 2026
Search Tags:#automation#ui-testing#web-testing#browse#browser-automation#playwright-mcp#qa-testing
One-click install
npx skills add https://github.com/yulonghe97/ystack --skill browse-yulonghe97
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/yulonghe97/ystack/tree/main/skills/browse
Command: npx skills add https://github.com/yulonghe97/ystack --skill browse-yulonghe97

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates browser-based QA tasks to validate UI behavior and surface runtime issues, reducing manual testing time.

Core Features & Use Cases

  • Navigate to pages and manage browser sessions.
  • Snapshot and inspect page state, including accessibility tree.
  • Interact with elements via click, type, and fill.
  • Take screenshots and log console messages for visual QA.
  • Verify network requests and API calls.
  • Resize viewport for responsive checks.
  • Supports authentication patterns and multi-mode runs.

Quick Start

Launch a browser-enabled QA session and begin validating a page by navigating to it and performing basic interactions.

Frequently Asked Questions about browse

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

FAQPage Schema
How do I automate UI testing with Playwright MCP?▼

To automate UI testing with Playwright MCP, you control a real Chromium session to validate UI behavior by navigating pages, interacting with elements, capturing screenshots, and monitoring console and network activity.

What is browser automation for QA workflows?▼

Browser automation for QA workflows involves controlling a real Chromium session to validate UI behavior, reducing manual testing time by automating page navigation, element interaction, and responsive viewport checks.

Do I need Playwright MCP registered to run browser automation tasks?▼

Yes, you need Playwright MCP registered and access to browser tools like browser_navigate, browser_snapshot, browser_click, browser_type, and browser_take_screenshot to automate QA browser tasks.

Can I perform responsive checks across desktop and mobile viewports?▼

Yes, you can perform responsive checks across desktop and mobile viewports by resizing the browser viewport during your automated web-testing session to validate UI behavior at different dimensions.

How do I capture screenshots and monitor network requests during web testing?▼

You capture screenshots and monitor network requests during web testing by utilizing browser tools within the Playwright MCP session to log console messages, verify API calls, and take visual screenshots.

Does this browser automation approach support authentication patterns?▼

Yes, this browser automation approach supports authentication patterns and multi-mode runs, allowing you to manage complex browser sessions and validate authenticated user workflows.

Related Skills

Explore More Software Engineering Skills→
achmfachmf

webapp-testing

Automate end-to-end browser testing and accessibility audits with Playwright.

Community
Intermediate
harishgovardhandamodarharishgovardhandamodar

browser-testing-with-devtools

Inspect live web applications with Chrome DevTools MCP for debugging.

Community
Advanced
AndrewLi0420AndrewLi0420

gstack

Drive a headless browser with Playwright to capture diffs and screenshots.

Community
Intermediate
billydeeii136billydeeii136

setup-browser-cookies

Import cookies from a Chromium browser into a headless browser session.

Community
Intermediate