opencli

name	opencli
description	Agent Skill for OpenCLI. Use when the user wants to control websites through the `opencli` CLI, run or inspect OpenCLI site/app/external adapters, use the OpenCLI browser bridge/CDP automation
compatibility	Requires the OpenCLI command `opencli`.

OpenCLI

OpenCLI makes websites available as CLI commands through adapters and browser bridge automation.

Prerequisites

The opencli binary must be on $PATH.

Public Internet access is usually required for live website and adapter commands. Browser bridge commands also require OpenCLI's daemon and browser extension/CDP connection to be healthy.

Initial Checks

Check at least once: command -v opencli or where.exe opencli on Windows to confirm opencli is available.

If the command is missing, stop and ask the user to install or expose opencli on $PATH.

Then run the browser bridge diagnostic for every OpenCLI task:

opencli doctor

If opencli doctor reports missing daemon, missing extension, or failed connectivity, summarize the failing checks. First try again without the sandbox (for codex). If still failed, treat doctor failures as blocking for browser-backed adapters and opencli browser commands; for non-browser read-only commands, continue only when the requested command does not depend on browser bridge health.

You may inspect daemon state when useful:

opencli daemon status

Ask before restarting or stopping the daemon.

Command Discovery

Do not assume adapter names, command names, arguments, or flags. Discover the current CLI surface from help output:

opencli --help
opencli list -f yaml
opencli <site-or-adapter> --help -f yaml
opencli <site-or-adapter> <command> --help -f yaml
opencli browser --help

Prefer -f yaml or -f json when available so command arguments, options, access level, browser requirements, and output columns are structured.

Common Workflows

For site/app/external adapters:

1. Use opencli list -f yaml to find relevant adapters.
2. Inspect the adapter with opencli <adapter> --help -f yaml.
3. Inspect the exact command with opencli <adapter> <command> --help -f yaml.
4. Choose output format intentionally, usually -f yaml or -f json for downstream reasoning.

For direct browser control:

1. Make sure opencli doctor runs successfully once before proceeding.
2. Read opencli browser --help and the relevant subcommand help.
3. Pick a descriptive browser session name and reuse it across related calls.
4. Use opencli browser <session> state to inspect interactive element indices before clicking, typing, selecting, uploading, or dragging.

For adapter development or verification:

opencli validate <target>
opencli verify <target>
opencli convention-audit <target>

Inspect each command's help before passing flags.

Safety Rules

• Confirm with the user before commands that log in, post, send, purchase, subscribe, create, update, delete, upload, download private data, change profile/session defaults, install/uninstall plugins, or control daemon lifecycle.
• Treat browser-backed interactions as remote side effects when they click, type, submit, authenticate, or change page state.
• Do not print secrets, tokens, cookies, credentials, session exports, or private browser data. Summarize only what the task requires.
• Prefer read-only adapter commands and structured output first. Use browser automation only when adapters cannot satisfy the task.
• If a command fails because OpenCLI's daemon, extension, profile, or browser session is not ready, report the specific failed check and the next user-visible setup step.