skills.rest
Steffen025
Steffen025COMMUNITY
Explore all skills by this author →
WebsiteGitHub

Browser

Automate browser UI testing with direct Playwright API calls.

186|24|Updated Jan 1, 2026
Search Tags:#automation#debugging#screenshots#verification#playwright#ui-testing#browser
One-click install
npx skills add https://github.com/Steffen025/pai-opencode --skill browser-steffen025
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Browser
Source: https://github.com/Steffen025/pai-opencode/tree/main/.opencode/skills/Browser
Command: npx skills add https://github.com/Steffen025/pai-opencode --skill browser-steffen025

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Browser automation with built-in debugging visibility for UI testing, page capture, and verification, removing guesswork and manual steps from web interactions.

Core Features & Use Cases

  • Code-first control: Direct Playwright operations without token-heavy MCP layers.
  • Always-on diagnostics: Console, network, and page-title capture by default for reliable verification.
  • Use Case: Verify a login flow by navigating to a URL, performing actions, taking a screenshot, and collecting diagnostic data in one command.

Quick Start

Install the dependencies with bun install, then run a sample command to navigate and capture diagnostics: bun run ~/.opencode/skills/Browser/Tools/Browse.ts https://example.com

Frequently Asked Questions about Browser

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

FAQPage Schema
How do I automate browser workflows for UI testing while capturing console and network diagnostics?▼

Browser automation for UI testing with built-in diagnostics is handled through direct Playwright API operations, capturing console logs, network traffic, and page titles by default. This removes manual verification steps and guesswork.

How do I take a screenshot and verify page state in Playwright without token-heavy MCP layers?▼

Taking a screenshot and verifying page state is achieved through a code-first interface that bypasses token-heavy MCP tooling. It allows direct Playwright API usage to navigate, perform actions, and capture diagnostic data in one command.

Can I run Playwright UI testing scripts using Bun or Node without external services?▼

Playwright UI testing scripts are fully compatible with Bun and Node environments without requiring external services. You can install dependencies with bun install and run the script directly for headless diagnostic data capture.

What is the best way to debug a login flow and capture web page diagnostics?▼

Debugging a login flow is best handled by navigating to the target URL, performing authentication actions, taking a screenshot, and collecting always-on diagnostic data. This provides reliable verification of the complete web interaction.

Are there limitations when using code-first browser automation for page verification?▼

Limitations of code-first browser automation include the requirement for a Bun or Node environment and the need to write code for direct Playwright operations. It targets diagnostic workflows rather than zero-code visual testing platforms.

Related Skills

Explore More Software Engineering Skills→
hoodinihoodini
262

bun

Automate JavaScript workflows using Bun commands and built-in APIs.

Community
Advanced
webmaxruwebmaxru

webapp-testing

Automate Playwright testing and debugging of local web applications in Node.js.

Community
Intermediate
LincyawLincyaw
2

web-debug

Automate headless Chromium browser tests for web UI regressions.

Community
Intermediate
nonputtipongnonputtipong

playwright-mcp

Automate live browser interactions via Playwright MCP server tools.

Community
Intermediate