headless-fallback

Scrape JavaScript-heavy web pages using headless-Chrome as a fallback.

26|2|Updated Jun 8, 2026
One-click install
npx skills add https://github.com/xberg-io/plugins --skill headless-fallback
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: headless-fallback
Source: https://github.com/xberg-io/plugins/tree/main/plugins/crawlberg/.cursor-plugin/skills/headless-fallback
Command: npx skills add https://github.com/xberg-io/plugins --skill headless-fallback

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the issue of scraping web pages that rely heavily on JavaScript, which can't be rendered with a static fetch. It automates the process using headless-Chrome as a fallback.

Core Features & Use Cases

  • Headless-Chrome Fallback: Handles JavaScript-only pages that static scraping can't process.
  • Custom Browser Modes: Supports 'auto', 'always', and 'never' modes for different scraping scenarios.
  • External CDP Endpoint: Allows pointing to an existing headless-Chrome instance for more control and performance.
  • Performance Optimization: Provides wait strategies and browser profile persistence for better resource management.
  • Use Case: When scraping a dynamic web page with complex JavaScript rendering, this Skill ensures complete data extraction by automatically falling back to headless-Chrome.

Quick Start

Run the crawlberg scrape command with the '--browser-mode always' option for pages requiring headless-Chrome.

Frequently Asked Questions about headless-fallback

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

FAQPage Schema
How do I scrape JavaScript-rendered web pages that return empty content with static fetch?

To scrape JavaScript-rendered web pages, you need headless-Chrome to execute and render the page scripts. This Skill automates web scraping by falling back to headless-Chrome, ensuring complete data extraction from dynamic pages that static fetching cannot process.

What's the best way to force headless-Chrome for browser automation on heavily dynamic sites?

The best way to force headless-Chrome for browser automation is using the 'always' browser mode. You can run your scraping command with the '--browser-mode always' option to ensure the headless-Chrome fallback is actively engaged for complex JavaScript rendering.

Does this web scraping tool support connecting to an external headless-Chrome instance?

Yes, this web scraping tool supports connecting to an external headless-Chrome instance. By pointing to an external CDP endpoint, you gain more control over the browser environment and achieve better performance optimization for your scraping tasks.

Can I optimize web scraping performance when extracting data from JavaScript-heavy pages?

You can optimize web scraping performance by utilizing wait strategies and browser profile persistence. These features manage resources efficiently during JavaScript rendering, while the 'auto' browser mode selectively triggers headless-Chrome only when needed.

When should I not use headless-Chrome for web scraping and data extraction?

You should not use headless-Chrome for web scraping when targeting static pages, as it introduces unnecessary overhead. Use the 'never' browser mode to restrict the fallback and rely solely on static fetching for simpler data extraction tasks without JavaScript dependencies.