se-browser-automation

What This Skill Does

The se-browser-automation skill is a specialized toolkit for controlling web browsers within the OpenClaw ecosystem. It provides robust patterns for navigating modern web applications, particularly Single Page Applications (SPAs) like GoHighLevel (GHL) and Lovable. This skill abstracts the complexity of headless browser management, allowing the AI to interact with complex DOM structures, handle iframes, manage authentication flows, and extract data efficiently using snapshot and screenshot techniques.

Installation

To integrate this capability into your OpenClaw environment, execute the following command in your terminal or command-line interface: clawhub install openclaw/skills/skills/boris148/se-browser-automation

Use Cases

• Automated Data Extraction: Scrape lead data or analytics from password-protected dashboards that require login steps.
• Form Submission: Automate repetitive inputs into complex web forms, including multi-step flows and 2FA authentication.
• SPA Navigation: Seamlessly traverse platform interfaces that do not perform full page reloads, using direct URL injection to bypass menu bottlenecks.
• UI Verification: Utilize visual screenshots to verify that dynamic content has rendered correctly before proceeding with data interaction.

Example Prompts

1. "Navigate to the GHL dashboard, log in using my stored credentials, and extract the latest lead count from the CRM tab."
2. "Open the project in Lovable, take a screenshot of the main preview window, and check if the 'Submit' button is visible."
3. "Refresh the analytics page and wait for the chart to load, then snapshot the page to find the export button ref."

Tips & Limitations

• Iframe Awareness: If the DOM appears empty, the content is likely inside an iframe. Always use the frame parameter during snapshots.
• Asynchronous Loading: SPAs require time to render. Always include a 4-6 second sleep period after navigation to ensure content availability.
• Code Restrictions: When evaluating custom JavaScript, remember to avoid arrow functions or modern 'const/let' declarations; stick to ES5 standards with 'var' and 'function' syntax.
• State Persistence: If the browser UI gets stuck due to SPA state caching, utilize a forced refresh or direct URL navigation to reset the page environment.