open-app
Use OpenCLI as an app automation bridge for websites, logged-in Chrome sessions, Electron apps, and local CLIs, then return structured results; For: \"open this site and extract the table\", \"use my current Chrome login to operate the dashboard\", \"check whether this platform has an OpenCLI command\"; Triggers: open-app, OpenCLI, app automation, browser automation, Chrome session, website adapter, web scraping, form filling
What this skill does
Open App Automation
Use OpenCLI as an external CLI-backed automation layer for websites, logged-in browser sessions, Electron apps, and local command-line tools.
Prefer existing OpenCLI adapters first. Use browser control only when no stable adapter covers the requested action. Keep the user in control whenever an action can modify external state.
This skill does not install OpenCLI by itself, bypass login or CAPTCHA, access paid content, or run unknown third-party plugin code without user confirmation.
When to Use
- The user asks to operate a website, web app, Electron app, or local CLI through an app-like command interface.
- The user mentions OpenCLI,
opencli, app automation, browser automation, Chrome login state, web scraping, data extraction, form filling, or adapter-based site commands. - The user wants to reuse their current Chrome login state to read, extract, fill, click, or inspect a page.
- The user wants to check whether a platform already has an OpenCLI command, such as GitHub, Hacker News, Twitter/X, Reddit, Bilibili, Zhihu, or another site.
Do not use this skill for simple web search, ordinary page summarization, or one-off questions that do not need login state, browser control, or a command-oriented interface.
How to Call
- Check whether OpenCLI is available.
opencli --versionIf the command is missing, ask before installing @jackwener/opencli. Do not install dependencies silently.
- For browser or login-state work, diagnose the bridge first.
opencli doctorCOOKIE, INTERCEPT, UI, and opencli browser workflows need the browser bridge to be working. Public adapters, local CLI adapters, and opencli list may still work without browser bridge access.
- Discover available commands before choosing an adapter.
opencli list -f json
opencli <site> --help
opencli <site> <command> --helpUse opencli list -f json to find candidate adapters, then inspect the site-level and command-level help before running the command.
- Prefer an existing adapter.
opencli <site> <command> --limit 10 -f jsonFor agent-facing use, request JSON output by default when the command supports it. Use plain text only for conversational or generation-style commands where JSON is not useful.
- Use browser control only when adapters do not cover the task.
opencli browser <session> open <url>
opencli browser <session> state
opencli browser <session> click <target>
opencli browser <session> fill <target> "<text>"
opencli browser <session> get text <target>
opencli browser <session> network
opencli browser <session> closeRun state or a target-finding command before clicking, filling, selecting, or extracting. After navigation, form submission, route changes, or a visible page refresh, run state again and do not reuse stale references.
- Select an existing Chrome tab only when the user explicitly asks to use their current logged-in browser session.
opencli browser <session> tab list
opencli browser <session> tab select <targetId>
opencli browser <session> state --tab <targetId>The selected tab belongs to the user's real browser window. Do not close, switch away from, create, or disrupt the user's tabs unless the user specifically requests that action.
- When creating or repairing adapters, keep the change narrow.
opencli browser recon analyze <url>
opencli browser recon init <site>/<command>
opencli browser recon verify <site>/<command>If an existing adapter fails because a site changed, preserve the trace or error summary and fix only the affected adapter path. Avoid replacing a broken adapter with an unrelated temporary scraping script.
- Confirm before any irreversible or externally visible action.
Ask for confirmation before posting, messaging, submitting forms, purchasing, deleting, changing account settings, installing plugins, registering external CLIs, or executing unknown third-party code.
Return Format
In normal conversation, summarize the result briefly and include the key command that was run. Do not paste full JSON unless the user asks for machine-readable output.
Use this structure for successful results:
{
"ok": true,
"command": "opencli ...",
"summary": "What was done or found",
"data": "Key fields, table summary, or output path",
"warnings": []
}Use this structure for failures:
{
"ok": false,
"command": "opencli ...",
"error": "Specific failure reason",
"next_step": "How to fix or retry"
}Return JSON when the user asks for a machine-readable result. Otherwise, return a concise Markdown summary, a table when useful, and any necessary source links.
External Dependencies
- OpenCLI CLI: required to run the commands in this skill; install with
npm install -g @jackwener/opencliafter user approval. - Node.js >= 21: required for the standard OpenCLI npm install path.
- Chrome or Chromium: required for browser login state, browser bridge workflows, and UI-driven automation.
- OpenCLI Browser Bridge extension: required for browser bridge and logged-in page operations.
- User login state: required for private pages, account dashboards, social platforms, and authenticated data.
- Network access: required for website commands, plugin installation, adapter validation, and live content retrieval.
Limits and Safety
- Do not bypass login, authorization, CAPTCHA, paywalls, rate limits, or a site's terms of service.
- Browser references are reliable only for the current page snapshot. Refresh the state after any page change.
- Website adapters can break when page structure, API responses, fields, or anti-automation behavior changes.
- Treat logged-in browser sessions as sensitive because they may expose cookies, private data, or account permissions.
- Do not install third-party OpenCLI plugins or execute unknown plugin code without the user's explicit approval.
- Avoid storing scraped personal data…
Files in this skill
- SKILL.md
How to use in Orkas
Open the Orkas desktop app, go to the marketplace, and install this item with one click. Don't have Orkas yet? Download Orkas.
用 OpenCLI 把网站、已登录 Chrome、Electron 应用和本地 CLI 转成可由 agent 调用的应用操作能力,并返回结构化结果;适合\"打开这个网站并提取表格\"\"用我当前 Chrome 登录态操作后台\"\"看看某个平台有没有 OpenCLI 命令\";触发词:open-app、OpenCLI、应用自动化、浏览器自动化、Chrome 登录态、网站适配器、网页抓取、填表
该技能的功能
Open App Automation
Use OpenCLI as an external CLI-backed automation layer for websites, logged-in browser sessions, Electron apps, and local command-line tools.
Prefer existing OpenCLI adapters first. Use browser control only when no stable adapter covers the requested action. Keep the user in control whenever an action can modify external state.
This skill does not install OpenCLI by itself, bypass login or CAPTCHA, access paid content, or run unknown third-party plugin code without user confirmation.
When to Use
- The user asks to operate a website, web app, Electron app, or local CLI through an app-like command interface.
- The user mentions OpenCLI,
opencli, app automation, browser automation, Chrome login state, web scraping, data extraction, form filling, or adapter-based site commands. - The user wants to reuse their current Chrome login state to read, extract, fill, click, or inspect a page.
- The user wants to check whether a platform already has an OpenCLI command, such as GitHub, Hacker News, Twitter/X, Reddit, Bilibili, Zhihu, or another site.
Do not use this skill for simple web search, ordinary page summarization, or one-off questions that do not need login state, browser control, or a command-oriented interface.
How to Call
- Check whether OpenCLI is available.
opencli --versionIf the command is missing, ask before installing @jackwener/opencli. Do not install dependencies silently.
- For browser or login-state work, diagnose the bridge first.
opencli doctorCOOKIE, INTERCEPT, UI, and opencli browser workflows need the browser bridge to be working. Public adapters, local CLI adapters, and opencli list may still work without browser bridge access.
- Discover available commands before choosing an adapter.
opencli list -f json
opencli <site> --help
opencli <site> <command> --helpUse opencli list -f json to find candidate adapters, then inspect the site-level and command-level help before running the command.
- Prefer an existing adapter.
opencli <site> <command> --limit 10 -f jsonFor agent-facing use, request JSON output by default when the command supports it. Use plain text only for conversational or generation-style commands where JSON is not useful.
- Use browser control only when adapters do not cover the task.
opencli browser <session> open <url>
opencli browser <session> state
opencli browser <session> click <target>
opencli browser <session> fill <target> "<text>"
opencli browser <session> get text <target>
opencli browser <session> network
opencli browser <session> closeRun state or a target-finding command before clicking, filling, selecting, or extracting. After navigation, form submission, route changes, or a visible page refresh, run state again and do not reuse stale references.
- Select an existing Chrome tab only when the user explicitly asks to use their current logged-in browser session.
opencli browser <session> tab list
opencli browser <session> tab select <targetId>
opencli browser <session> state --tab <targetId>The selected tab belongs to the user's real browser window. Do not close, switch away from, create, or disrupt the user's tabs unless the user specifically requests that action.
- When creating or repairing adapters, keep the change narrow.
opencli browser recon analyze <url>
opencli browser recon init <site>/<command>
opencli browser recon verify <site>/<command>If an existing adapter fails because a site changed, preserve the trace or error summary and fix only the affected adapter path. Avoid replacing a broken adapter with an unrelated temporary scraping script.
- Confirm before any irreversible or externally visible action.
Ask for confirmation before posting, messaging, submitting forms, purchasing, deleting, changing account settings, installing plugins, registering external CLIs, or executing unknown third-party code.
Return Format
In normal conversation, summarize the result briefly and include the key command that was run. Do not paste full JSON unless the user asks for machine-readable output.
Use this structure for successful results:
{
"ok": true,
"command": "opencli ...",
"summary": "What was done or found",
"data": "Key fields, table summary, or output path",
"warnings": []
}Use this structure for failures:
{
"ok": false,
"command": "opencli ...",
"error": "Specific failure reason",
"next_step": "How to fix or retry"
}Return JSON when the user asks for a machine-readable result. Otherwise, return a concise Markdown summary, a table when useful, and any necessary source links.
External Dependencies
- OpenCLI CLI: required to run the commands in this skill; install with
npm install -g @jackwener/opencliafter user approval. - Node.js >= 21: required for the standard OpenCLI npm install path.
- Chrome or Chromium: required for browser login state, browser bridge workflows, and UI-driven automation.
- OpenCLI Browser Bridge extension: required for browser bridge and logged-in page operations.
- User login state: required for private pages, account dashboards, social platforms, and authenticated data.
- Network access: required for website commands, plugin installation, adapter validation, and live content retrieval.
Limits and Safety
- Do not bypass login, authorization, CAPTCHA, paywalls, rate limits, or a site's terms of service.
- Browser references are reliable only for the current page snapshot. Refresh the state after any page change.
- Website adapters can break when page structure, API responses, fields, or anti-automation behavior changes.
- Treat logged-in browser sessions as sensitive because they may expose cookies, private data, or account permissions.
- Do not install third-party OpenCLI plugins or execute unknown plugin code without the user's explicit approval.
- Avoid storing scraped personal data…
技能包含的文件
- SKILL.md
如何在 Orkas 中使用
打开 Orkas 桌面应用,进入市场,一键安装此项。还没有 Orkas? 下载 Orkas.