rune-browser-pilot

Automates browser navigation, UI interaction, and screenshot capture using Playwright MCP tools.

1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/dangvu008/VietTruyen --skill rune-browser-pilot-dangvu008
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rune-browser-pilot
Source: https://github.com/dangvu008/VietTruyen/tree/main/.agents/skills/rune-browser-pilot
Command: npx skills add https://github.com/dangvu008/VietTruyen --skill rune-browser-pilot-dangvu008

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manual browser testing and visual verification is slow and error-prone. This Skill automates navigating URLs, interacting with page elements, capturing screenshots, and collecting console errors so testing and deployment verification produce consistent, documented evidence. ## Core Features & Use Cases - Playwright MCP Automation: Navigate URLs, capture accessibility tree snapshots, click elements, type text, and fill forms through structured MCP tool calls. - Visual Evidence Capture: Take viewport or full-page screenshots to back up every visual finding in the report. - Structured Browser Reports: Emit a standardized report covering page status, accessibility findings, interaction logs, console errors, and screenshots. - Use Case: After deploying a landing page, invoke this Skill to load the live URL, verify key buttons and forms work, capture a full-page screenshot, and report any console errors before announcing the launch. ## Quick Start Ask the agent to open a URL with the browser-pilot skill, fill out the signup form, take a full-page screenshot, and report any console errors.

Frequently Asked Questions about rune-browser-pilot

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

FAQPage Schema
How do I automate browser testing with Playwright MCP tools?

Provide a target URL and a task such as screenshot, check_elements, fill_form, test_flow, or console_errors. The skill navigates to the page, captures an accessibility snapshot, performs the requested interactions, takes screenshots, and returns a structured report.

How to capture full-page screenshots of a website?

Use the browser_take_screenshot tool with type png and fullPage set to true. This captures the entire scrollable page, which is useful for landing pages and long-form content verification.

Can Playwright automation fill forms and click buttons?

Yes. The skill uses browser_click, browser_type, browser_fill_form, and browser_select_option tools, referencing elements from the accessibility snapshot. Each interaction is verified with a new snapshot before proceeding.

What are the limitations of automated browser interaction sessions?

Sessions are limited to 20 interactions; beyond that the skill stops and reports partial results. Credentials must never be stored in logs, and the browser must always be closed when the session ends, even on failure.

Why does browser automation fail to reach a page?

Navigation can fail due to timeouts, network errors, or unreachable hosts. When this happens the skill reports the URL as UNREACHABLE with the load outcome and stops rather than attempting further interactions.