Skip to main content
skill CX Codex

opencli-usage — Claude Code skill: driving OpenCLI

Teaches an agent to find OpenCLI commands, read their schemas and parse results. Useful when site and Chrome work goes through adapters.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add jackwener/OpenCLI --skill opencli-usage -a claude-code
Open on GitHub

What opencli-usage does

The skill spells out how an agent should use OpenCLI: search commands by name and description, inspect their inputs through command help, interpret the output. Search covers built-ins and adapters at once, and results come back compact and paginated — continue with --offset <nextOffset>. The adapter catalog is not dumped into context.

Commands answer in JSON by default: {ok:true,data:...}. A failure returns a nonzero exit code plus an object with code, message and hint; logs go to stderr. The -f table|yaml|csv|md|plain exports exist where command help lists them. When a write outcome is unknown, inspect state before repeating the action.

Page work runs through opencli browser open|state|close with --session, while native Chrome methods need no session. --profile picks a connected Chrome profile, profile list discovers them, doctor diagnoses the connection. Adapters are created and checked with adapter init|check|test|status; adapter tests execute real commands and can write. The skill needs opencli on PATH — without it the Bash calls never run.

What it helps with

  • find an OpenCLI command for a task
  • check a command's inputs before running it
  • read a JSON result and an error code
  • choose between a site adapter and a Chrome tool
  • verify a local adapter before shipping it

Example prompts for the agent

  • Find the OpenCLI command for searching GitHub and show its help
  • Open https://example.com in session research and show the page state
  • Test the example/search adapter with query=hello

How to install opencli-usage

1Skills CLI (Vercel)

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

2Manually: put the files in place

~/.claude/skills/opencli-usage/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/opencli-usage/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about opencli-usage

How do I install opencli-usage in Claude Code?

Run npx skills add jackwener/OpenCLI --skill opencli-usage -a claude-code. The skill file lands at ~/.claude/skills/opencli-usage/SKILL.md.

What does opencli-usage do?

It shows the agent how to search OpenCLI commands, read their schemas and interpret results, including errors and paginated output.

What does the skill need to work?

opencli on PATH. The skill allows Bash(opencli:*) and Read, so without the CLI those calls fail.

Source text

SKILL.md · Apache-2.0
---
name: opencli-usage
description: Discover and invoke OpenCLI capabilities for websites and Chrome. Find commands, inspect schemas, interpret results and choose browser or adapter tools.
allowed-tools: Bash(opencli:*), Read
---

# OpenCLI

OpenCLI exposes reusable website adapters and direct Chrome tools to agents.

```sh
opencli list search
opencli list --site github --limit 20
opencli github search --help -f json
```

`list [query]` searches command names and descriptions across built-ins and adapters.
Results are compact and paginated: `{ok:true,data:{commands,total,nextOffset?}}`.
Pass `--offset <nextOffset>` to continue. Inspect exact inputs using command help.
Do not hard-code the adapter catalog or dump all commands into context.

## Results

Commands default to JSON: `{ok:true,data:...}`. Failures produce a nonzero exit
code and `{ok:false,error:{code,message,hint?,...}}` on stdout. Logs use stderr.
Explicit `-f table|yaml|csv|md|plain` exports are available where command help lists
them. Help, version, completion and explicit plain exports retain their own formats.
Browser follow modes stream one JSON envelope per line.

Use error codes and supplied candidates/keys to recover. Unknown write outcomes
require inspecting state before repeating an action. An empty successful result
is distinct from an execution failure.

## Browser

```sh
opencli browser open https://example.com --session research
opencli browser state --session research
opencli browser close --session research
opencli browser chrome describe
```

Page commands use `--session`; native Chrome methods need no session. `--profile`
selects a connected Chrome profile. `profile list` discovers profiles and
`profile use <name>` selects the default. Use `doctor` for connection diagnosis.
See `opencli-browser` for interaction, API evidence and tab/group management.

## Adapters and installation

```sh
opencli adapter init example/search
opencli adapter check example/search
opencli adapter test example/search --args '{"query":"hello"}'
opencli adapter status
```

See `opencli-adapter-author` for implementation. `adapter eject` makes an official
site editable locally; `adapter reset` removes that local override. Adapter tests
execute real commands and can perform writes.

`plugin list|install|update|uninstall|create` manages plugin packages. `auth status`
reports website login facts; `auth refresh` touches sessions. `daemon status|restart|stop`
manages the bridge process. Read help for the selected capability.

Bundled skill content is available through `skills list` and
`skills read opencli-browser -f plain` (omit `-f plain` for JSON).

© jackwener · Apache-2.0 · jackwener/OpenCLI

Similar skills

All skills for Agent setup: memory, context, orchestration →
troubleshooting ChromeDevTools Diagnoses connection failures and tool errors in Chrome DevTools MCP step by step. Helpful when the server refuses to launch or tab commands fail. CX Codex +1 3,200installs browser-use browser-use Hands the agent a real Chrome over CDP: clicks, typing, screenshots, and pages that need JS or your logged-in session. CX Codex +1 98,200installs model-usage openclaw Reads CodexBar local cost logs and breaks spending down by model for Codex or Claude. Useful when you want to see where the money goes. CX Codex +1 5,500installs setup-matt-pocock-skills Matt Pocock This skill configures a repository for Matt Pocock's engineering skills by setting its issue tracker, triage labels, and domain docs layout. Run it before using the other skills. 1,052,851installs ask-matt Matt Pocock Routes you to the right Matt Pocock skill or flow for the task at hand. Use it when you need a starting point for a feature, prototype, incoming issue, or hard bug. 766,587installs to-tickets Matt Pocock Turns a plan, spec, or conversation into small end-to-end tickets with explicit blockers. Use it to agree on the work breakdown before tickets go to a tracker. 711,230installs writing-plans Jesse Vincent This skill turns requirements for a multi-step task into an implementation plan before code changes begin. It helps when another engineer needs exact files, interfaces, and checks. CX Codex 282,859installs caveman-review JuliusBrussee Turns code review comments into one line per finding: location, problem, fix. Useful when a diff or PR needs a fast pass without the filler. CX Codex +1 411,800installs

From the same set4

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor