verify-page-loaded

Detect page readiness via DOM state and loading indicators.

8|Updated May 13, 2026
One-click install
npx skills add https://github.com/bettyguo/browser-skills --skill verify-page-loaded
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-page-loaded
Source: https://github.com/bettyguo/browser-skills/tree/main/skills/verify-page-loaded
Command: npx skills add https://github.com/bettyguo/browser-skills --skill verify-page-loaded

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Confirms that the current page has finished loading and is ready for interaction, by detecting loading spinners, skeleton screens, and placeholders. Run before extraction or interaction skills.

Core Features & Use Cases

  • Deterministic readiness checks using DOM readiness, body visibility, and absence of loading indicators.
  • Applicable after navigation or content changes on general websites, SPAs, or dynamic pages before data extraction or interactions.
  • Guidance for integration with common automation hooks (e.g., wait_for_dom_ready, wait_for_selector, assert) to ensure reliable downstream steps.

Quick Start

Invoke this skill after navigation to ensure the page is fully ready before proceeding with extraction or interaction steps.

Frequently Asked Questions about verify-page-loaded

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

FAQPage Schema
How do I verify a web page is fully loaded before automating interactions?

To verify a web page is fully loaded, check DOM readiness, body visibility, and the absence of loading indicators or skeleton screens using deterministic hooks like wait_for_dom_ready and assert.

What is the best way to handle loading spinners and skeleton screens in web automation?

Handling loading spinners and skeleton screens involves waiting for DOM readiness and asserting that placeholder elements are gone. This ensures dynamic content has fully rendered before proceeding.

Does DOM readiness guarantee a dynamic SPA page is ready for interaction?

DOM readiness alone does not guarantee a dynamic SPA page is ready for interaction. You must also verify body visibility and use wait_for_selector to ensure loading indicators and skeleton screens are completely absent.

When do I need to verify page load status during web automation workflows?

You need to verify page load status after any navigation or content changes on general websites and SPAs, serving as a prerequisite step before executing any data extraction or UI interaction steps.

Why does my data extraction fail on dynamic pages before they finish loading?

Data extraction fails on dynamic pages when skeleton screens or loading spinners are still present. Verifying DOM readiness and asserting the absence of loading indicators before extraction prevents these errors.