// Automatically fix broken OpenCLI adapters when commands fail. Load this skill when an opencli command fails — it guides you through diagnosing the failure via OPENCLI_DIAGNOSTIC, patching the adapter, retrying, and filing an upstream GitHub issue after a verified fix. Works with any AI agent.
Make websites accessible for AI agents. Navigate, click, type, extract, wait — using Chrome with existing login sessions. No LLM API key needed.
Use when creating a new OpenCLI adapter from scratch, adding support for a new website or platform, exploring a site's API endpoints via browser DevTools, or when a user asks to automatically generate a CLI for a website. Covers automated generation, API discovery workflow, authentication strategy selection, TS adapter writing, and testing.
Use when quickly generating a single OpenCLI command from a specific URL and goal description. 4-step process — open page, capture API, write TS adapter, test. For full site exploration, use opencli-explorer instead.
Use when running OpenCLI commands to interact with websites (Bilibili, Twitter, Reddit, Xiaohongshu, etc.), desktop apps (Cursor, Notion), or public APIs (HackerNews, arXiv). Covers installation, command reference, and output formats for 87+ adapters.
基于 opencli 命令的智能搜索路由器。当用户想要搜索、查询、查找或研究信息时，尤其是涉及指定网站、社交媒体、技术资料、新闻、购物、旅游、求职、金融或中文内容时，务必使用此 skill
| name | opencli-autofix |
| description | Automatically fix broken OpenCLI adapters when commands fail. Load this skill when an opencli command fails — it guides you through diagnosing the failure via OPENCLI_DIAGNOSTIC, patching the adapter, retrying, and filing an upstream GitHub issue after a verified fix. Works with any AI agent. |
| allowed-tools | Bash(opencli:*), Bash(gh:*), Read, Edit, Write |
When an opencli command fails because a website changed its DOM, API, or response schema, automatically diagnose, fix the adapter, and retry.
AUTH_REQUIRED (exit code 77) — STOP. Tell user to log into the site in Chrome.BROWSER_CONNECT (exit code 69) — STOP. Tell user to run opencli doctor.RepairContext.adapter.sourcePath — never modify src/, extension/, tests/OPENCLI_DIAGNOSTIC=1 opencli <site> <command> [args...] 2>diagnostic.json
| Error Code | Likely Cause | Repair Strategy |
|---|---|---|
| SELECTOR | DOM restructured | Explore current DOM → find new selector |
| EMPTY_RESULT | API response schema changed | Check network → find new response path |
| API_ERROR | Endpoint URL changed | Discover new API via network intercept |
| AUTH_REQUIRED | Login flow changed, cookies expired | STOP — tell user to log in |
| TIMEOUT | Page loads differently | Add/update wait conditions |
| PAGE_CHANGED | Major redesign | May need full adapter rewrite |
Use opencli browser to inspect the live website. Never use the broken adapter.
# DOM changed
opencli browser open https://example.com/target-page && opencli browser state
# API changed
opencli browser open https://example.com/target-page && opencli browser network
Read the adapter source file at RepairContext.adapter.sourcePath and make targeted fixes.
Selector update:
// Before: page.evaluate('document.querySelector(".old-class")...')
// After: page.evaluate('document.querySelector(".new-class")...')
API endpoint change:
// Before: fetch('/api/v1/old-endpoint')
// After: fetch('/api/v2/new-endpoint')
Response schema change:
// Before: const items = data.results
// After: const items = data.data.items
opencli <site> <command> [args...]
If still fails, go back to Step 1. Max 3 rounds.
Only after a verified local fix:
gh issue create --repo jackwener/OpenCLI \
--title "[autofix] <site>/<command>: <error_code>" \
--body "<fix summary>"
Ask the user before filing.