playwright-bowser

Open Segmently UI screens, capture screenshots, and verify visible state.

Updated Jun 29, 2026
One-click install
npx skills add https://github.com/segmently-ai/segmently-support-plugins --skill playwright-bowser-segmently-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright-bowser
Source: https://github.com/segmently-ai/segmently-support-plugins/tree/main/plugins/segmently-launch-assistant/skills/playwright-bowser
Command: npx skills add https://github.com/segmently-ai/segmently-support-plugins --skill playwright-bowser-segmently-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you locate, verify, and document customer-facing Segmently UI states in a browser without guessing selectors or changing values unexpectedly.

Core Features & Use Cases

  • SHOW Walkthroughs: Open the right screen, inspect visible UI state, and capture screenshots when a user needs to find a control or setting.
  • Browser-Backed Verification: Confirm published funnel pages or editor views are actually loaded and readable in a live browser session.
  • Generated Action Contracts: Execute explicit browser tasks from Segmently Launch Assistant only when the owning skill, target, and verification steps are provided.
  • Use Case: A support agent can ask for a guided walkthrough of a Segmently page, receive the current URL and screenshot, and then continue with a safe next step.

Quick Start

Use the playwright-bowser skill to open the requested Segmently screen, verify what is visible, and return a screenshot and the current URL.

Frequently Asked Questions about playwright-bowser

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

FAQPage Schema
How do I capture browser screenshots for UI verification without guessing selectors?

Browser screenshots for UI verification are captured by opening the requested screen, inspecting visible state, and returning the current URL without inventing selectors or mutating values. This ensures safe, read-only walkthroughs.

What is the best way to guide automated browser walkthroughs for published funnel pages?

Automated browser walkthroughs for published funnel pages are guided by loading the live editor view, verifying the page is actually readable, and capturing a screenshot. The process confirms visible state without unexpected modifications.

Does browser automation require explicit verification steps to execute action contracts?

Browser automation requires explicit verification steps, the owning skill, and a defined target to execute action contracts safely. This prevents unintended side effects when running tasks generated by the launch assistant.

Can I use browser automation to inspect a live UI state and locate specific settings?

Browser automation can inspect live UI state to locate specific settings by opening the correct Segmently screen. It returns the visible controls and a screenshot to support safe next steps without altering values.

Do I need host browser tooling and authentication to run UI verification checks?

Host browser tooling and Segmently authentication are required to run UI verification checks. These prerequisites ensure the automation can securely access the correct environment and execute explicit verification reads.

Why does browser automation avoid mutating values during a UI walkthrough?

Browser automation avoids mutating values during a UI walkthrough to prevent unexpected changes to customer-facing states. It applies read-only verification reads to ensure the documented UI remains safe and unaltered.