Agent skill

OpenCLI Usage Map

by jackwener in jackwener/OpenCLI

Orients an agent on OpenCLI, which turns websites and Electron apps into opencli site-command calls, covering adapters, strategies, install and which skill to load next.

Apache-2.0Auto-check passedProductivity & Automation

Install OpenCLI Usage Map

skills CLI
$ npx skills add jackwener/OpenCLI --skill opencli-usage -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jackwener/OpenCLI opencli-usage --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jackwener/OpenCLI.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/opencli-usage .claude/skills/opencli-usage && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
opencli-usage
GitHub stars
30k
Used in
1 other repo
Token cost
~2.3k tokens
SKILL.md length
930 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
Apache-2.0

At a glance

Orients an agent on OpenCLI, which turns websites and Electron apps into opencli site-command calls, covering adapters, strategies, install and which skill to load next.

  • Starting an OpenCLI session and finding the right adapter command
  • SKILL.md covers Main capabilities, Install, Prerequisites by command type and Discover what's installed —…, plus 10 more sections
  • Calls npm, git and npx
  • Deciding whether a command needs a logged-in Chrome session

What it does

OpenCLI exposes websites and Electron desktop apps as a uniform opencli site-and-command surface that agents can drive without screen-scraping. This skill is the orientation layer: it explains adapter commands (built-in ones in clis/, user ones in ~/.opencli/clis/), browser driving through opencli browser subcommands for ad-hoc work, and current-tab binding that attaches a Chrome tab you already logged into to a session.

Each adapter has a strategy tag shown by opencli list: PUBLIC needs nothing but HTTP, COOKIE reuses a logged-in Chrome session through the OpenCLI extension, INTERCEPT adds an automation window to capture a signed request, UI does full DOM interaction, and LOCAL talks to a local endpoint. Install is through a global npm package (Node 20.18.1 or newer), and opencli doctor diagnoses the browser bridge, which only the cookie, intercept, UI and browser commands need.

When your agent uses it

  • Starting an OpenCLI session and finding the right adapter command
  • Deciding whether a command needs a logged-in Chrome session
  • Diagnosing the browser bridge with opencli doctor
  • Choosing which specialized OpenCLI skill to load next

Example prompts

  • “What can opencli do? Show me how to list the available adapters.”
  • “Run opencli doctor and tell me whether my Chrome extension is connected.”
  • “Which opencli commands work without a logged-in browser?”

Requirements

  • Node.js 20.18.1 or newer and the opencli npm package
  • The OpenCLI Chrome extension for cookie, intercept and UI adapters
  • Pre-approved tools (allowed-tools): Bash(opencli:*), Read

What it can do on your machine

Read from SKILL.md and the folder at commit 2413694. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash(opencli:*)
    • Read

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npm
    • git
    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • chromewebstore.google.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

OpenCLI Usage Map loads about 2.3k tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 930 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~78
When it runs · the whole SKILL.md, loaded when a task matches
~2.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jackwener/OpenCLI at commit 2413694, republished under its Apache-2.0 licence (© jackwener). 930 words, ~2,319 tokens.

Download SKILL.mdSave it as .claude/skills/opencli-usage/SKILL.md (or your agent's skills folder).
name
opencli-usage
description
Use at the start of any OpenCLI session — this is the top-level map of what `opencli` can do, how to discover adapters, what flags and output formats are universal, and which specialized skill to load next. Point here when an agent asks "what can opencli do?" or "how do I find the right command?".
allowed-tools
Bash(opencli:*), Read

opencli-usage

OpenCLI turns websites and Electron desktop apps into a uniform opencli <site> <command> surface that agents can drive without screen-scraping. This skill is the orientation layer — once you know what you want to do, load one of the specialized skills below.

Main capabilities

  • Adapter commands — opencli <site> <command> [...]. Built-in adapters live in clis/, user adapters in ~/.opencli/clis/. Each is backed by a strategy (PUBLIC | COOKIE | INTERCEPT | UI | LOCAL) that tells you whether a Chrome session is needed.
  • Browser driving — opencli browser * subcommands (open, state, click, type, select, find, extract, network, …) for ad-hoc interaction and scraping when no adapter covers the task. See opencli-browser.
  • Current-tab binding — opencli browser <session> bind attaches the Chrome tab the user already opened/logged into to that browser session. Follow-up commands use opencli browser <session> .... See opencli-browser before using it; bound sessions still block tab mutation.

Install

bash
# npm global
npm install -g @jackwener/opencli          # binary: opencli, requires Node >= 20.18.1
opencli doctor                              # run before browser-dependent work (see below)

# From source
git clone git@github.com:jackwener/OpenCLI.git
cd OpenCLI && npm install
npx tsx src/main.ts <command>               # same surface, no global install

opencli doctor prints a structured DoctorReport — daemon status, extension connection, version checks, and a live browser connectivity probe. Scope is narrow: it diagnoses the browser bridge (daemon + extension + Chrome wiring). PUBLIC / LOCAL adapters, opencli list, validate, verify, and plugin commands don't need it to be green — only COOKIE / INTERCEPT / UI adapters and the opencli browser * subcommands do. Flag: -v (verbose).

Prerequisites by command type

Strategy tag on opencli listWhat it needs
PUBLICNothing — pure HTTP, no browser.
COOKIEChrome logged into the target site + OpenCLI extension installed from the Chrome Web Store. Command captures the credential from your live session — no re-login.
INTERCEPTSame as COOKIE, plus opencli opens an automation window to capture a signed request.
UISame as COOKIE, full DOM interaction.
LOCALNo browser; talks to a local/dev endpoint.

Electron desktop apps (cursor, codex, chatwise, discord-app, doubao-app, antigravity, chatgpt-app) route through CDP against the running app — same cookie-less flow as a logged-in browser. Make sure the app is running before invoking.

Discover what's installed — don't read this file, run a command

bash
opencli list                    # table, grouped by site
opencli list -f json            # machine-readable; pipe to jq or your agent
opencli list | grep -i twitter  # find commands for a specific site
opencli <site> --help           # see that site's commands + flags
opencli <site> <command> --help # see positional args and command-specific flags

Do not hard-code adapter lists — there are 100+ sites and the count moves every week. opencli list -f json is the source of truth; it emits one entry per command with {site, name, aliases, description, strategy, browser, args, columns, ...}. For an agent, that is always better than grepping a doc.

Before falling back to raw opencli browser commands on high-change authenticated sites, check whether a site adapter already exposes the workflow. For example, ChatGPT web has higher-level commands for conversation reads and Deep Research result extraction; discover the current surface with opencli chatgpt --help or opencli list -f json.

Universal flags (work on every adapter command)

flageffect
-f, --format <fmt>table (default in TTY) · yaml (default in non-TTY) · json · plain · md · csv. Pass explicitly when you want a specific shape; agents almost always want -f json.
-v, --verboseDebug logs + stack traces on failure; also sets OPENCLI_VERBOSE=1 for the process.

Command-specific flags (--limit, --tab, --filter, …) are not universal — consult <site> <command> --help.

Output formats

  • json — pretty-printed, 2-space indent. Default choice for agents.
  • plain — prints a single primary field for chat-style commands (response/content/text/value). Useful for piping to another tool.
  • yaml — fallback when output is not a TTY and -f is not explicit.
  • table — color-coded, site-grouped; meant for humans.
  • md, csv — straightforward tabular dumps.

A few commands override the default via cmd.defaultFormat (e.g. chat commands default to plain), so don't assume without reading --help.

Show full SKILL.md (381 more words)Show less

Environment variables

variabledefaultpurpose
OPENCLI_BROWSER_CONNECT_TIMEOUT45Seconds to wait for the browser bridge.
OPENCLI_BROWSER_COMMAND_TIMEOUT60Per-command timeout.
OPENCLI_CDP_ENDPOINT—Manual CDP endpoint override (dev / remote Chrome / Electron).
OPENCLI_CACHE_DIR~/.opencli/cacheNetwork capture + browser-state cache.
OPENCLI_WINDOWcommand-specificforeground or background browser window mode.
OPENCLI_VERBOSEfalseVerbose logging (also triggered by -v).

Self-repair

When an adapter command fails because the site changed (selectors drifted, API rotated, response schema shifted), re-run with --trace retain-on-failure. The error envelope includes a trace block pointing at summary.md; patch only the adapterSourcePath from that summary and retry. Max 3 repair rounds. The full flow is in opencli-autofix.

Writing your own adapter

Two-path storage:

  • Private: ~/.opencli/clis/<site>/<command>.js — no build step, hot-available, not visible in the public package.
  • Public / PR: clis/<site>/<command>.js — for upstream contribution; requires build.

Scaffolding & verification:

bash
opencli browser init <site>/<command>   # generates a skeleton
opencli validate [target]               # semantic checks on the loaded registry (description, domain, pipeline step names, func|pipeline|_lazy presence, arg duplicates) — no network, no browser
opencli verify [target] [--smoke]       # run the command with synthetic args
opencli browser verify <site>/<command> # end-to-end smoke inside the bridge

Adapters import only @jackwener/opencli/registry and @jackwener/opencli/errors. columns must align 1:1 (in name and order) with keys of the object returned by func. For the full workflow see opencli-adapter-author.

Plugins

Plugins are third-party extensions pulled from git, separate from the main adapter registry:

bash
opencli plugin install github:user/repo    # install
opencli plugin list [-f json]              # see installed
opencli plugin update [name] | --all       # keep current
opencli plugin uninstall <name>
opencli plugin create <name>               # scaffold a new plugin

Shell completion

bash
opencli completion bash   # also: zsh, fish
# -> script on stdout; source or save per your shell's convention

Where to go next

If you're about to…Load this skill
Drive a live browser ad-hoc (no adapter available, or prototyping)opencli-browser
Write a new adapter, or add a command to an existing siteopencli-adapter-author
Fix a broken adapter after a command failureopencli-autofix
Route a search / lookup / research request to the right adaptersmart-search

Commands that used to exist

The following were removed in the PR #1094 consolidation — don't try to invoke them:

  • opencli explore <url> — superseded by opencli browser network + opencli browser find for live API discovery, and by the opencli-adapter-author workflow for capture.
  • opencli record <url> — removed; manual capture now lives in opencli browser network --detail.
  • opencli web read / opencli desktop * as top-level groups — folded into their respective adapters (opencli web read still exists as the web adapter's read command, but there is no standalone web / desktop top-level group command).

Don't

  • Don't paste this skill's command list into your plan; it will rot. Call opencli list -f json at the start of a task instead.
  • Don't assume every adapter needs a browser — strategy PUBLIC and LOCAL don't. Check the strategy field.
  • Don't silently fall back from a failing adapter to a hand-rolled fetch — --trace retain-on-failure gives you the browser evidence and adapter source path. Do that first.

© jackwener, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/opencli-usage of jackwener/OpenCLI.

Open the folder on GitHubat commit 2413694

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in jackwener/OpenCLI, which our catalogue first saw on October 7, 2026.

Compare with similar skills

OpenCLI Usage Map next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

OpenCLI Usage Map compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
OpenCLI Usage Map this skilljackwener/OpenCLI30k1 repos~2.3kAutomated safety check: PassApache-2.0
Chrome CDP Browser Controlzenstory-ai/oh-story-claudecode7.3k2 repos~1.2kAutomated safety check: PassMIT
Agent Browser Automationwithkynam/vibecode-pro-max-kit1.1k—~2.6kAutomated safety check: PassApache-2.0
Still2rig Psdshinshin86/still2rig-psd128—~1.4kAutomated safety check: PassMIT
Electron Devtools Testingankitvgupta/exo496—~2.4kAutomated safety check: PassCustom licence
Page AgentTommy-yw/RunbookHermes5463 repos~2.3kAutomated safety check: NotesMIT

Similar skills

  • Chrome CDP Browser Control

    zenstory-ai/oh-story-claudecode

    Drives a Chrome window over the DevTools Protocol with the agent-browser CLI, so the agent can reuse your logged-in sessions, read pages and pull tokens.

    7.3k GitHub starsUsed in 2 repos~1.2k tokens
    Productivity & AutomationAuto-check passed
  • Agent Browser Automation

    withkynam/vibecode-pro-max-kit

    Drives a browser through the agent-browser CLI, using compact snapshots with element refs to keep context small in long sessions, plus video recording and cloud browsers.

    1.1k GitHub stars~2.6k tokensUpdated 3 mo ago
    Productivity & AutomationAuto-check passed
  • Still2rig Psd

    shinshin86/still2rig-psd

    Convert a user-provided static anime character image into a verified rig-ready PSD by coordinating the Still2Rig PSD local job CLI with a user-approved Google Colab session through Colab MCP Go.

    128 GitHub stars~1.4k tokensUpdated 8 days ago
    Productivity & AutomationAuto-check passed
  • Test the Electron app interactively using Chrome DevTools Protocol.

    496 GitHub stars~2.4k tokensUpdated 1 mo ago
    Productivity & AutomationAuto-check passed
  • Page Agent

    Tommy-yw/RunbookHermes

    Embed alibaba/page-agent into your own web application — a pure-JavaScript in-page GUI agent that ships as a single <script tag or npm package and lets end-users of your site drive the UI with…

    546 GitHub starsUsed in 3 repos~2.3k tokens
    Productivity & AutomationAuto-check: notes
  • Reverse Browser Automation

    sickn33/agentic-awesome-skills

    Automate browsers (Playwright) and Windows desktop applications (UI automation) for reverse-engineering evidence collection, UI-driven workflows, and network observation during analysis.

    47k GitHub starsUsed in 1 repo~1.3k tokens
    Productivity & AutomationAuto-check passed

More from jackwener/OpenCLI

  • OpenCLI Adapter Author

    jackwener/OpenCLI

    Walks through writing an OpenCLI adapter for a new site or a new command on an existing one, from first recon and field decoding to coding and verification.

    30k GitHub starsUsed in 1 repo~3.4k tokens
    Auto-check passed
  • Routes a search question to the most suitable opencli source, normally one AI site plus up to two specialist sites, with call limits per question and a recap at the end.

    30k GitHub starsUsed in 2 repos~753 tokens
    Auto-check passed
  • OpenCLI Browser Control

    jackwener/OpenCLI

    Drives a real Chrome window through the opencli CLI to inspect pages, fill forms, click through logged-in flows and extract data from structured command responses.

    30k GitHub starsUsed in 2 repos~7.3k tokens
    Auto-check passed
  • OpenCLI Adapter Autofix

    jackwener/OpenCLI

    Repairs a broken OpenCLI site adapter after a command fails: collects a trace, patches only the adapter, retries, and files an upstream GitHub issue once fixed.

    30k GitHub starsUsed in 1 repo~3.2k tokens
    Auto-check passed

Works with

Questions about OpenCLI Usage Map

What does OpenCLI Usage Map do?

Orients an agent on OpenCLI, which turns websites and Electron apps into opencli site-command calls, covering adapters, strategies, install and which skill to load next. OpenCLI exposes websites and Electron desktop apps as a uniform opencli site-and-command surface that agents can drive without screen-scraping.opencli/clis/), browser driving through opencli browser subcommands for ad-hoc work, and current-tab binding that attaches a Chrome tab you already logged into to a session.

When should I use OpenCLI Usage Map?

OpenCLI Usage Map fits situations like: starting an OpenCLI session and finding the right adapter command; deciding whether a command needs a logged-in Chrome session; diagnosing the browser bridge with opencli doctor; choosing which specialized OpenCLI skill to load next.

How do I install OpenCLI Usage Map in Claude Code?

Run `npx skills add jackwener/OpenCLI --skill opencli-usage -a claude-code`. Or copy the skill folder (skills/opencli-usage in jackwener/OpenCLI) into .claude/skills/opencli-usage in your project. Claude Code loads it when a task matches its description.

How do I install OpenCLI Usage Map in Codex?

Run `npx skills add jackwener/OpenCLI --skill opencli-usage -a codex`. Or copy the skill folder (skills/opencli-usage in jackwener/OpenCLI) into .agents/skills/opencli-usage in your project. Codex loads it when a task matches its description.

Can I use OpenCLI Usage Map in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jackwener/OpenCLI --skill opencli-usage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/opencli-usage, .gemini/skills/opencli-usage, .github/skills/opencli-usage and .opencode/skills/opencli-usage in your project.

What does OpenCLI Usage Map need to run?

Going by SKILL.md and its folder, OpenCLI Usage Map needs the command-line tools its instructions call (npm, git and npx). Our summary lists: Node.js 20.18.1 or newer and the opencli npm package; The OpenCLI Chrome extension for cookie, intercept and UI adapters. Its frontmatter pre-approves these tools: Bash(opencli:*), Read.

Does OpenCLI Usage Map access the network?

SKILL.md names 1 domain. As links in the text: chromewebstore.google.com. This is read from the text; nothing was executed.

Is OpenCLI Usage Map safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does OpenCLI Usage Map use?

OpenCLI Usage Map is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does OpenCLI Usage Map use?

About 2.3k tokens (SKILL.md is roughly 9.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to OpenCLI Usage Map?

Skills that share tags, products or a category with OpenCLI Usage Map: Chrome CDP Browser Control (zenstory-ai/oh-story-claudecode, 7.3k stars), Agent Browser Automation (withkynam/vibecode-pro-max-kit, 1.1k stars), Still2rig Psd (shinshin86/still2rig-psd, 128 stars) and Electron Devtools Testing (ankitvgupta/exo, 496 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains OpenCLI Usage Map?

jackwener (a GitHub user) maintains it in jackwener/OpenCLI, which has 29,886 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on September 24, 2026.

Source: jackwener/OpenCLI on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.