skills.rest
krishna-cyber
krishna-cyberCOMMUNITY
Explore all skills by this author →
GitHub

dev-browser

Connect to a persistent Chrome instance for fallback browser automation.

Updated Jul 2, 2026
Search Tags:#debugging#browser automation#web scraping#fallback solution#persistent Chrome
One-click install
npx skills add https://github.com/krishna-cyber/plate_js_rich_text_editor --skill dev-browser-krishna-cyber
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-browser
Source: https://github.com/krishna-cyber/plate_js_rich_text_editor/tree/main/.agents/skills/dev-browser
Command: npx skills add https://github.com/krishna-cyber/plate_js_rich_text_editor --skill dev-browser-krishna-cyber

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The dev-browser Skill unit provides a persistent Chrome state for fallback browser automation, offering an alternative when standard browser tools are unavailable or blocked.

Core Features & Use Cases

  • Persistent Chrome State: Utilizes a dedicated Chrome profile with persistent data for efficient browser automation.
  • Fallback Automation: Serves as a backup when other browser automation tools like Puppeteer or Playwright are not available.
  • Use Case: When encountering issues with standard browser automation, dev-browser can be used to connect to a persistent Chrome instance and continue tasks like debugging or scraping.

Quick Start

To initiate the fallback browser automation with dev-browser, run the command: dev-browser --connect http://127.0.0.1:9222

Frequently Asked Questions about dev-browser

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

FAQPage Schema
How do I automate web scraping when standard browser automation tools are blocked?▼

Web scraping fallback automation is achievable by connecting to a persistent Chrome instance using a dedicated profile. This ensures continuous browser operation and allows scraping tasks to proceed when standard tools are unavailable.

What is persistent Chrome state for browser automation?▼

Persistent Chrome state utilizes a dedicated profile with persistent data to maintain continuous browser operation. It provides a stable environment for debugging and web scraping across sessions without losing state.

Can I use a persistent Chrome instance for debugging instead of Puppeteer?▼

Yes, you can use a persistent Chrome instance as a fallback for debugging when Puppeteer or other standard automation tools are unavailable. It connects via a dedicated profile to maintain browser state.

How do I connect to a persistent Chrome instance for fallback browser automation?▼

To connect to a persistent Chrome instance for fallback browser automation, run the command `dev-browser --connect http://127.0.0.1:9222`. This establishes a connection to the dedicated profile.

Does fallback browser automation require any external dependencies?▼

No external dependencies are required for fallback browser automation. The mechanism operates independently using a dedicated Chrome profile with persistent state to ensure continuous operation.

Related Skills

Explore More Software Engineering Skills→
udecodeudecode
434

browser-debug-setup

Set up a persistent Chrome debugging environment with a dedicated profile.

Official
Intermediate
AgentComputerAIAgentComputerAI
5

stackoverflow

Scrape StackOverflow tag pages with Puppeteer and Cheerio.

Official
Advanced
serkan-ozalserkan-ozal
7

api-testing

Mock API responses and intercept HTTP requests in browser automation.

Community
Intermediate
VoDaiLoczVoDaiLocz
24

chrome-devtools

Automate browser tasks with Puppeteer CLI scripts for navigation, screenshots, and performance analysis.

Community
Advanced