test-browsy-flow

Validate browsy CLI page parsing and classification for login, search, and form pages.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/GhostPeony/browsyclaw --skill test-browsy-flow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-browsy-flow
Source: https://github.com/GhostPeony/browsyclaw/tree/main/claude-code-plugin/skills/test-browsy-flow
Command: npx skills add https://github.com/GhostPeony/browsyclaw --skill test-browsy-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps ensure that the browsy CLI can accurately parse and interact with specific web pages, preventing agent failures due to unexpected site structures or dynamic content.

Core Features & Use Cases

  • Page Parsing Validation: Fetches a URL and reports on browsy's Spatial DOM conversion, including element counts and types.
  • Page Classification Accuracy: Checks if browsy correctly identifies the page type (e.g., Login, Search, Form).
  • Suggested Actions Verification: Validates that browsy suggests appropriate actions for the detected page type.
  • Use Case: Before deploying an agent to automate a complex login process, use this Skill to test the login page and confirm browsy can identify the correct input fields and buttons.

Quick Start

Run /test-browsy-flow https://example.com/login to test the browsy CLI against the specified URL.

Frequently Asked Questions about test-browsy-flow

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

FAQPage Schema
How do I test web page parsing and classification with a CLI agent?

Verify browsy CLI page classification by fetching a URL and checking if the tool accurately identifies page types like Login, Search, or Form and suggests appropriate interactions for automated agents.

Do I need to install the browsy CLI before validating page parsing?

Yes, the browsy CLI must be installed and accessible in your system's PATH environment variable before you can validate page parsing and interaction classification.

What's the best way to confirm a login page is compatible with browsy Spatial DOM?

Validate login page compatibility by running a browsy CLI test flow against the URL to confirm it correctly identifies input fields, buttons, and suggested actions within the Spatial DOM.

Can I check suggested actions for dynamic web forms before deploying an automation agent?

Yes, you can verify suggested actions by testing web forms with browsy to ensure the CLI detects the correct elements and recommends appropriate interactions before agent deployment.

Why does my agent fail to interact with unexpected site structures during web scraping?

Agents fail when browsy cannot accurately parse unexpected site structures or dynamic content, making page parsing validation necessary to confirm Spatial DOM compatibility beforehand.