opencli-browser

Drive live Chrome sessions for web interactions, form filling, and data extraction.

7|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/carl10086/ys-powers --skill opencli-browser-carl10086
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opencli-browser
Source: https://github.com/carl10086/ys-powers/tree/main/external/opencli/skills/opencli-browser
Command: npx skills add https://github.com/carl10086/ys-powers --skill opencli-browser-carl10086

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the challenge of reliably interacting with complex, dynamic web applications that require authentication, multi-step flows, or real-time data inspection, which standard scraping tools cannot handle.

Core Features & Use Cases

  • Live Browser Control: Drive a real Chrome instance to click, type, select, and navigate through authenticated sessions.
  • Resilient Interaction: Uses a selector-first contract with numeric refs to handle DOM drift and UI re-renders automatically.
  • Network Inspection: Capture and inspect API responses directly to bypass complex DOM scraping for data-heavy tasks.
  • Use Case: Automate a multi-step login and data entry process on a legacy internal portal that requires specific browser state and session persistence.

Quick Start

Use the opencli-browser skill to open a new session named work, navigate to the target URL, and extract the main content.

Frequently Asked Questions about opencli-browser

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

FAQPage Schema
How do I automate web scraping on sites that require authentication and multi-step login?

Automate authenticated web scraping by driving a live Chrome browser session that maintains session persistence, handles login flows, and performs DOM manipulation to extract data. It applies a selector-first contract with numeric refs to handle dynamic UI re-renders automatically.

Can I inspect network traffic and capture API responses directly during browser automation?

You can inspect network traffic and capture API responses directly during browser automation, bypassing complex DOM scraping for data-heavy tasks. It uses the Chrome DevTools Protocol to capture and inspect API responses for structured data extraction.

What is the best way to handle dynamic DOM drift when automating web interactions?

Handle dynamic DOM drift by using a selector-first contract with numeric refs that automatically adjusts to UI re-renders and structural changes. This approach ensures resilient interaction when driving live Chrome sessions for complex web tasks.

Does this browser automation approach work with legacy internal portals requiring specific browser state?

Yes, it works with legacy internal portals by driving a real Chrome instance that maintains specific browser state and session persistence. It automates multi-step login and data entry processes on complex web applications standard scraping tools cannot handle.

Why use live Chrome sessions for agentic web tasks instead of standard HTML scraping tools?

Live Chrome sessions are required for agentic web tasks involving authentication, multi-step flows, or real-time data inspection that standard HTML scraping tools cannot handle. It drives a real browser to click, type, select, and navigate through authenticated sessions reliably.

What are the limitations of using Chrome browser automation for web data extraction?

Limitations include relying on a live Chrome instance which requires more resources than lightweight HTTP scraping. It is not suited for simple static page extraction, but targets complex dynamic web applications needing session persistence and network traffic inspection.