Opencli Web Automation
Wrap logged-in websites as CLI commands by reusing Chrome sessions and Playwright MCP instead of brittle one-off scrapers.
Overview
OpenCLI Web Automation is an agent skill most often used in Build (also Ship, Operate) that turns authenticated websites into CLI commands via Chrome session reuse and Playwright MCP.
Install
npx skills add https://github.com/aradotso/trending-skills --skill opencli-web-automationWhat is this skill?
- Ships with 19 built-in site adapters and 80+ commands out of the box
- Reuses Chrome’s logged-in session via Playwright MCP Bridge—no re-auth in headless stubs
- Add sites with TypeScript or YAML adapters dropped into the `clis/` folder
- `opencli setup` and `opencli doctor --live` for one-time MCP token discovery and health checks
- Trigger phrases cover explore/synthesize workflows and new adapter authoring
- 19 sites supported out of the box
- 80+ commands bundled
- Node.js >= 18.0.0 required
Adoption & trust: 1.3k installs on skills.sh; 31 GitHub stars; 1/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need reliable automation on logged-in web apps but do not want to maintain fragile scrapers or re-enter credentials in every agent run.
Who is it for?
Indie builders who already use Chrome daily and want agent-invokable commands for a handful of critical websites.
Skip if: Headless-only pipelines with no interactive browser, sites that forbid automation in ToS, or teams that need official vendor APIs instead of UI automation.
When should I use this skill?
When the user wants OpenCLI scraping, new site adapters, browser automation with session reuse, or CLI command synthesis for a website.
What do I get? / Deliverables
You install and verify OpenCLI, run or synthesize site-specific CLI commands, and optionally add adapters so agents can extract data or drive flows repeatably.
- Working OpenCLI setup and doctor verification
- New YAML or TypeScript CLI adapters
- Documented CLI commands for target websites
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Build/integrations is the primary shelf because the skill centers on installing OpenCLI, adapters, and browser-backed command synthesis. Integrations fits session-reuse automation and YAML/TypeScript adapters that connect agents to external web UIs.
Where it fits
Add a YAML adapter so `opencli` can pull orders from a vendor portal your API key cannot access.
Expose repeatable site commands your coding agent can invoke instead of free-form browser clicks.
Run `opencli doctor --live` before release to confirm MCP bridge and Chrome are wired for smoke flows.
Refresh CLI adapters when a SaaS UI changes without rewriting a full scraper repo.
How it compares
Skill-guided CLI packaging over raw Playwright scripts—not a hosted scraping SaaS or generic MCP server by itself.
Common Questions / FAQ
Who is opencli-web-automation for?
Solo developers wiring agents to real browser sessions who prefer CLI verbs and adapter files over ad-hoc navigation scripts.
When should I use opencli-web-automation?
Use it when triggers like “use opencli to scrape a website,” “make a CLI command for a website,” or “create yaml adapter for opencli” appear—typical in Build integrations, Ship testing against live UIs, and Operate data pulls from admin consoles.
Is opencli-web-automation safe to install?
It requires global npm install, browser extensions, and filesystem writes for adapters; review the Security Audits panel on this Prism page before granting shell and browser access.
SKILL.md
READMESKILL.md - Opencli Web Automation
# OpenCLI Web Automation > Skill by [ara.so](https://ara.so) — Daily 2026 Skills collection. OpenCLI turns any website into a command-line interface by reusing Chrome's logged-in browser session. It supports 19 sites and 80+ commands out of the box, and lets you add new adapters via TypeScript or YAML dropped into the `clis/` folder. --- ## Installation ```bash # Install globally via npm npm install -g @jackwener/opencli # One-time setup: discovers Playwright MCP token and distributes to all tools opencli setup # Verify everything is working opencli doctor --live ``` ### Prerequisites - Node.js >= 18.0.0 - Chrome browser **running and logged into the target site** - [Playwright MCP Bridge](https://chromewebstore.google.com/detail/playwright-mcp-bridge/mmlmfjhmonkocbjadbfplnigmagldckm) extension installed in Chrome ### Install from Source (Development) ```bash git clone git@github.com:jackwener/opencli.git cd opencli npm install npm run build npm link ``` --- ## Environment Configuration ```bash # Required: set in ~/.zshrc or ~/.bashrc after running opencli setup export PLAYWRIGHT_MCP_EXTENSION_TOKEN="<your-token-from-setup>" ``` MCP client config (Claude/Cursor/Codex `~/.config/*/config.json`): ```json { "mcpServers": { "playwright": { "command": "npx", "args": ["-y", "@playwright/mcp@latest", "--extension"], "env": { "PLAYWRIGHT_MCP_EXTENSION_TOKEN": "$PLAYWRIGHT_MCP_EXTENSION_TOKEN" } } } } ``` --- ## Key CLI Commands ### Discovery & Registry ```bash opencli list # Show all registered commands opencli list -f yaml # Output registry as YAML opencli list -f json # Output registry as JSON ``` ### Running Built-in Commands ```bash # Public API commands (no browser login needed) opencli hackernews top --limit 10 opencli github search "playwright automation" opencli bbc news # Browser commands (must be logged into site in Chrome) opencli bilibili hot --limit 5 opencli twitter trending opencli zhihu hot -f json opencli reddit frontpage --limit 20 opencli xiaohongshu search "TypeScript" opencli youtube search "browser automation" opencli linkedin search "senior engineer" ``` ### Output Formats All commands support `--format` / `-f`: ```bash opencli bilibili hot -f table # Rich terminal table (default) opencli bilibili hot -f json # JSON (pipe to jq) opencli bilibili hot -f yaml # YAML opencli bilibili hot -f md # Markdown opencli bilibili hot -f csv # CSV export opencli bilibili hot -v # Verbose: show pipeline debug steps ``` ### AI Agent Workflow (Creating New Commands) ```bash # 1. Deep explore a site — discovers APIs, auth, capabilities opencli explore https://example.com --site mysite # 2. Synthesize YAML adapters from explore artifacts opencli synthesize mysite # 3. One-shot: explore → synthesize → register in one command opencli generate https://example.com --goal "hot posts" # 4. Strategy cascade — auto-probes PUBLIC → COOKIE → HEADER auth opencli cascade https://api.example.com/data ``` Explore artifacts are saved to `.opencli/explore/<site>/`: - `manifest.json` — site metadata - `endpoints.json` — discovered API endpoints - `capabilities.json` — inferred command capabilities - `auth.json` — authentication strategy --- ## Adding a New Adapter ### Option 1: YAML Declarative Adapter Drop a `.yaml` file into `clis/` — auto-registered on next run: ```yaml # clis/producthunt.yaml site: producthunt commands: - name: