back
loading skill details...
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 AutoFix — Automatic Adapter Self-Repair When an opencli command fails because a website changed its DOM, API, or response schema, automatically diagnose, fix the adapter, and retry — don't just report the error. Safety Boundaries Before starting any repair, check these hard stops: AUTH_REQUIRED (exit code 77) — STOP. Do not modify code. Tell the user to log into the site in Chrome. BROWSER_CONNECT (exit code 69) — STOP. Do not modify code. Tell the user to run opencli doctor. CAPTCHA / rate limiting — STOP. Not an adapter issue. Scope constraint: Only modify the file at RepairContext.adapter.sourcePath — this is the authoritative adapter location (may be clis/<site>/ in repo or ~/.opencli/clis/<site>/ for npm installs) Never modify src/, extension/, tests/, package.json, or tsconfig.json Retry budget: Max 3 repair rounds per failure. If 3 rounds of diagnose → fix → retry don't resolve it, stop and report what was tried. Prerequisites
don't have the plugin yet? install it then click "run inline in claude" again.