Browser Visibility & Debug

Capture screenshots, inspect DOM elements, and test selectors in browser automation.

2|Updated May 16, 2026
One-click install
npx skills add https://github.com/atomeam/Aether --skill browser-visibility-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Browser Visibility & Debug
Source: https://github.com/atomeam/Aether/tree/main/.devin/skills/browser-visibility-debug
Command: npx skills add https://github.com/atomeam/Aether --skill browser-visibility-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the "flying blind" problem in browser automation, where lack of visibility into page state, DOM structure, and interaction outcomes leads to failed actions, wasted debugging time, and unreliable automation workflows.

Core Features & Use Cases

  • 100+ Visibility Techniques: Capture screenshots (before/after actions, error states, multiple viewports, dark mode), log full page HTML, DOM elements, console messages, and network requests.
  • Element Discovery & Selector Testing: List all visible/hidden elements, buttons, inputs, links, test selector matches, and use fallback selectors for robust interaction.
  • State Validation & Error Recovery: Validate page load state, element visibility/clickability, auto-retry failed actions, rollback to previous page states, and run in headful mode for interactive debugging.
  • Use Case: For example, when automating a login flow, use this Skill to capture a screenshot before entering credentials, validate the username field is visible, auto-retry if the submit button is not found, and capture a success screenshot after login completes.

Quick Start

Use the browser-visibility-debug skill to take a full-page screenshot of the current browser page and log all visible clickable elements to the debug log.

Frequently Asked Questions about Browser Visibility & Debug

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

FAQPage Schema
How do I debug browser automation when page interactions fail silently?

Debug browser automation failures by capturing screenshots of page states before and after actions, logging full DOM structure, and inspecting console messages. This visibility eliminates silent failures by revealing why element interactions or page loads failed.

What's the best way to test Playwright selectors during automated web scraping?

Test Playwright selectors by listing all visible and hidden elements, validating selector matches against the current DOM, and applying fallback selectors. This ensures robust element interaction and reduces scraping failures caused by dynamic page updates.

Why does my automated login flow fail to find the submit button?

Automated login flows fail when the submit button is hidden, disabled, or wrapped in a dynamic container. Resolve this by validating element clickability, using fallback selectors, and enabling auto-retry mechanisms to handle delayed page rendering.

Can I capture screenshots in multiple viewports during robotic process automation?

Yes, capture screenshots across multiple viewports and visual modes like dark mode during robotic process automation. This validates responsive layout states and ensures automated UI interactions succeed across different display configurations.

Does this browser debugging approach work for recovering from error states in automation workflows?

Yes, recover from error states in automation workflows by auto-retrying failed actions and rolling back to previous page states. This error recovery mechanism reduces debugging time and improves overall workflow reliability without manual intervention.