Agent skill

Qiaomu Opencli Browser

by joeseesun in joeseesun/qiaomu-opencli-skills

Make websites accessible for AI agents. An agent skill from joeseesun/qiaomu-opencli-skills.

MITAuto-check passedAI & LLM Engineering

Install Qiaomu Opencli Browser

skills CLI
$ npx skills add joeseesun/qiaomu-opencli-skills --skill qiaomu-opencli-browser -a claude-code

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

GitHub CLI
$ gh skill install joeseesun/qiaomu-opencli-skills qiaomu-opencli-browser --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/joeseesun/qiaomu-opencli-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/qiaomu-opencli-browser .claude/skills/qiaomu-opencli-browser && 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
qiaomu-opencli-browser
GitHub stars
993
Token cost
~3.4k tokens
SKILL.md length
879 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
MIT

At a glance

Make websites accessible for AI agents. An agent skill from joeseesun/qiaomu-opencli-skills.

  • Works in 8 steps: ALWAYS use state to inspect the page,… → ALWAYS use click/type/select for… → Verify inputs with get value, not… → …
  • Tasks that involve LLM API integration
  • SKILL.md covers Prerequisites, Critical Rules, Command Cost Guide and Action Chaining Rules, plus 8 more sections
  • Reaches news.ycombinator.com and hacker-news.firebaseio.com

What it does

Qiaomu Opencli Browser is an agent skill from joeseesun/qiaomu-opencli-skills. Make websites accessible for AI agents. Navigate, click, type, extract, wait — using Chrome with existing login sessions. No LLM API key needed.

Its SKILL.md is about 3.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in AI & LLM Engineering, covering LLM API integration. The repository describes itself as: Use opencli CLI to interact with social/content websites (Bilibili, Zhihu, Twitter/X, YouTube, Weibo, 小红书, V2EX, Reddit, HackerNews, 雪球, BOSS直聘 etc.). The licence is MIT.

When your agent uses it

  • Tasks that involve LLM API integration

Example prompts

  • “/qiaomu-opencli-browser”

Requirements

  • Pre-approved tools (allowed-tools): Bash(opencli:*), Read, Edit, Write

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. ALWAYS use state to inspect the page, NEVER use screenshot — state returns structured DOM with [N] element indices, is instant and costs…
  2. ALWAYS use click/type/select for interaction, NEVER use eval to click or type — eval "el.click()" bypasses scrollIntoView and CDP click…
  3. Verify inputs with get value, not screenshots — after type, run get value to confirm.
  4. Run state after every page change — after open, click (on links), scroll, always run state to see the new elements and their indices…
  5. Chain commands aggressively with && — combine open + state, multiple type calls, and type + get value into single && chains. Each tool…
  6. eval is read-only — use eval ONLY for data extraction (JSON.stringify(...)), never for clicking, typing, or navigating. Always wrap in…
  7. Minimize total tool calls — plan your sequence before acting. A good task completion uses 3-5 tool calls, not 15-20. Combine open + state…
  8. Prefer network to discover APIs — most sites have JSON APIs. API-based adapters are more reliable than DOM scraping.

What it can do on your machine

Read from SKILL.md and the folder at commit 4d9a08e. 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
    • Edit
    • Write

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash and typescript).

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

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • news.ycombinator.com
    • hacker-news.firebaseio.com
    • httpbin.org
    • github.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

Qiaomu Opencli Browser loads about 3.4k tokens when it runs. Until then it costs about 42 tokens; SKILL.md has 879 words of instructions outside code blocks.

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

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 joeseesun/qiaomu-opencli-skills at commit 4d9a08e, republished under its MIT licence (© joeseesun). 879 words, ~3,367 tokens.

Download SKILL.mdSave it as .claude/skills/qiaomu-opencli-browser/SKILL.md (or your agent's skills folder).
name
qiaomu-opencli-browser
description
Make websites accessible for AI agents. Navigate, click, type, extract, wait — using Chrome with existing login sessions. No LLM API key needed.
allowed-tools
Bash(opencli:*), Read, Edit, Write
author
joeseesun
upstream
jackwener/opencli

OpenCLI Browser — Browser Automation for AI Agents

Control Chrome step-by-step via CLI. Reuses existing login sessions — no passwords needed.

Prerequisites

bash
opencli doctor    # Verify extension + daemon connectivity

Requires: Chrome running + OpenCLI Browser Bridge extension installed.

Critical Rules

  1. ALWAYS use state to inspect the page, NEVER use screenshot — state returns structured DOM with [N] element indices, is instant and costs zero tokens. screenshot requires vision processing and is slow. Only use screenshot when the user explicitly asks to save a visual.
  2. ALWAYS use click/type/select for interaction, NEVER use eval to click or type — eval "el.click()" bypasses scrollIntoView and CDP click pipeline, causing failures on off-screen elements. Use state to find the [N] index, then click <N>.
  3. Verify inputs with get value, not screenshots — after type, run get value <index> to confirm.
  4. Run state after every page change — after open, click (on links), scroll, always run state to see the new elements and their indices. Never guess indices.
  5. Chain commands aggressively with && — combine open + state, multiple type calls, and type + get value into single && chains. Each tool call has overhead; chaining cuts it.
  6. eval is read-only — use eval ONLY for data extraction (JSON.stringify(...)), never for clicking, typing, or navigating. Always wrap in IIFE to avoid variable conflicts: eval "(function(){ const x = ...; return JSON.stringify(x); })()".
  7. Minimize total tool calls — plan your sequence before acting. A good task completion uses 3-5 tool calls, not 15-20. Combine open + state as one call. Combine type + type + click as one call. Only run state separately when you need to discover new indices.
  8. Prefer network to discover APIs — most sites have JSON APIs. API-based adapters are more reliable than DOM scraping.

Command Cost Guide

CostCommandsWhen to use
Free & instantstate, get *, eval, network, scroll, keysDefault — use these
Free but changes pageopen, click, type, select, backInteraction — run state after
Expensive (vision tokens)screenshotONLY when user needs a saved image

Action Chaining Rules

Commands can be chained with &&. The browser persists via daemon, so chaining is safe.

Always chain when possible — fewer tool calls = faster completion:

bash
# GOOD: open + inspect in one call (saves 1 round trip)
opencli browser open https://example.com && opencli browser state

# GOOD: fill form in one call (saves 2 round trips)
opencli browser type 3 "hello" && opencli browser type 4 "world" && opencli browser click 7

# GOOD: type + verify in one call
opencli browser type 5 "test@example.com" && opencli browser get value 5

# GOOD: click + wait + state in one call (for page-changing clicks)
opencli browser click 12 && opencli browser wait time 1 && opencli browser state

# BAD: separate calls for each action (wasteful)
opencli browser type 3 "hello"    # Don't do this
opencli browser type 4 "world"    # when you can chain
opencli browser click 7            # all three together

Page-changing — always put last in a chain (subsequent commands see stale indices):

  • open <url>, back, click <link/button that navigates>

Rule: Chain when you already know the indices. Run state separately when you need to discover indices first.

Core Workflow

  1. Navigate: opencli browser open <url>
  2. Inspect: opencli browser state → elements with [N] indices
  3. Interact: use indices — click, type, select, keys
  4. Wait (if needed): opencli browser wait selector ".loaded" or wait text "Success"
  5. Verify: opencli browser state or opencli browser get value <N>
  6. Repeat: browser stays open between commands
  7. Save: write a TS adapter to ~/.opencli/clis/<site>/<command>.ts

Commands

Navigation
bash
opencli browser open <url>              # Open URL (page-changing)
opencli browser back                    # Go back (page-changing)
opencli browser scroll down             # Scroll (up/down, --amount N)
opencli browser scroll up --amount 1000
Inspect (free & instant)
bash
opencli browser state                   # Structured DOM with [N] indices — PRIMARY tool
opencli browser screenshot [path.png]   # Save visual to file — ONLY for user deliverables
Get (free & instant)
bash
opencli browser get title               # Page title
opencli browser get url                 # Current URL
opencli browser get text <index>        # Element text content
opencli browser get value <index>       # Input/textarea value (use to verify after type)
opencli browser get html                # Full page HTML
opencli browser get html --selector "h1" # Scoped HTML
opencli browser get attributes <index>  # Element attributes
Interact
bash
opencli browser click <index>           # Click element [N]
opencli browser type <index> "text"     # Type into element [N]
opencli browser select <index> "option" # Select dropdown
opencli browser keys "Enter"            # Press key (Enter, Escape, Tab, Control+a)
Wait

Three variants — use the right one for the situation:

bash
opencli browser wait time 3                       # Wait N seconds (fixed delay)
opencli browser wait selector ".loaded"            # Wait until element appears in DOM
opencli browser wait selector ".spinner" --timeout 5000  # With timeout (default 30s)
opencli browser wait text "Success"                # Wait until text appears on page

When to wait: After open on SPAs, after click that triggers async loading, before eval on dynamically rendered content.

Extract (free & instant, read-only)

Use eval ONLY for reading data. Never use it to click, type, or navigate.

bash
opencli browser eval "document.title"
opencli browser eval "JSON.stringify([...document.querySelectorAll('h2')].map(e => e.textContent))"

# IMPORTANT: wrap complex logic in IIFE to avoid "already declared" errors
opencli browser eval "(function(){ const items = [...document.querySelectorAll('.item')]; return JSON.stringify(items.map(e => e.textContent)); })()"

Selector safety: Always use fallback selectors — querySelector returns null on miss:

bash
# BAD: crashes if selector misses
opencli browser eval "document.querySelector('.title').textContent"

# GOOD: fallback with || or ?.
opencli browser eval "(document.querySelector('.title') || document.querySelector('h1') || {textContent:''}).textContent"
opencli browser eval "document.querySelector('.title')?.textContent ?? 'not found'"
Network (API Discovery)
bash
opencli browser network                  # Show captured API requests (auto-captured since open)
opencli browser network --detail 3       # Show full response body of request #3
opencli browser network --all            # Include static resources
Sedimentation (Save as CLI)
bash
opencli browser init hn/top              # Generate adapter scaffold at ~/.opencli/clis/hn/top.ts
opencli browser verify hn/top            # Test the adapter (adds --limit 3 only if `limit` arg is defined)
  • init auto-detects the domain from the active browser session (no need to specify it)
  • init creates the file + populates site, name, domain, and columns from current page
  • verify runs the adapter end-to-end and prints output; if no limit arg exists in the adapter, it won't pass --limit 3
Show full SKILL.md (352 more words)Show less
Session
bash
opencli browser close                   # Close automation window

Example: Extract HN Stories

bash
opencli browser open https://news.ycombinator.com
opencli browser state                   # See [1] a "Story 1", [2] a "Story 2"...
opencli browser eval "JSON.stringify([...document.querySelectorAll('.titleline a')].slice(0,5).map(a => ({title: a.textContent, url: a.href})))"
opencli browser close

Example: Fill a Form

bash
opencli browser open https://httpbin.org/forms/post
opencli browser state                   # See [3] input "Customer Name", [4] input "Telephone"
opencli browser type 3 "OpenCLI" && opencli browser type 4 "555-0100"
opencli browser get value 3             # Verify: "OpenCLI"
opencli browser close

Saving as Reusable CLI — Complete Workflow

Step-by-step sedimentation flow:
bash
# 1. Explore the website
opencli browser open https://news.ycombinator.com
opencli browser state                          # Understand DOM structure

# 2. Discover APIs (crucial for high-quality adapters)
opencli browser eval "fetch('/api/...').then(r=>r.json())"   # Trigger API calls
opencli browser network                        # See captured API requests
opencli browser network --detail 0             # Inspect response body

# 3. Generate scaffold
opencli browser init hn/top                    # Creates ~/.opencli/clis/hn/top.ts

# 4. Edit the adapter (fill in func logic)
# - If API found: use fetch() directly (Strategy.PUBLIC or COOKIE)
# - If no API: use page.evaluate() for DOM extraction (Strategy.UI)

# 5. Verify
opencli browser verify hn/top                  # Runs the adapter and shows output

# 6. If verify fails, edit and retry
# 7. Close when done
opencli browser close
Example adapter:
typescript
// ~/.opencli/clis/hn/top.ts
import { cli, Strategy } from '@jackwener/opencli/registry';

cli({
  site: 'hn',
  name: 'top',
  description: 'Top Hacker News stories',
  domain: 'news.ycombinator.com',
  strategy: Strategy.PUBLIC,
  browser: false,
  args: [{ name: 'limit', type: 'int', default: 5 }],
  columns: ['rank', 'title', 'score', 'url'],
  func: async (_page, kwargs) => {
    const limit = Math.min(Math.max(1, kwargs.limit ?? 5), 50);
    const resp = await fetch('https://hacker-news.firebaseio.com/v0/topstories.json');
    const ids = await resp.json();
    return Promise.all(
      ids.slice(0, limit).map(async (id: number, i: number) => {
        const item = await (await fetch(`https://hacker-news.firebaseio.com/v0/item/${id}.json`)).json();
        return { rank: i + 1, title: item.title, score: item.score, url: item.url ?? '' };
      })
    );
  },
});

Save to ~/.opencli/clis/<site>/<command>.ts → immediately available as opencli <site> <command>.

Strategy Guide
StrategyWhenbrowser:
Strategy.PUBLICPublic API, no authfalse
Strategy.COOKIENeeds login cookiestrue
Strategy.UIDirect DOM interactiontrue

Always prefer API over UI — if you discovered an API during browsing, use fetch() directly.

Tips

  1. Always state first — never guess element indices, always inspect first
  2. Sessions persist — browser stays open between commands, no need to re-open
  3. Use eval for data extraction — eval "JSON.stringify(...)" is faster than multiple get calls
  4. Use network to find APIs — JSON APIs are more reliable than DOM scraping
  5. Alias: opencli op is shorthand for opencli browser

Common Pitfalls

  1. form.submit() fails in automation — Don't use form.submit() or eval to submit forms. Navigate directly to the search URL instead:

    bash
    # BAD: form.submit() often silently fails
    opencli browser eval "document.querySelector('form').submit()"
    # GOOD: construct the URL and navigate
    opencli browser open "https://github.com/search?q=opencli&type=repositories"
  2. GitHub DOM changes frequently — Prefer data-testid attributes when available; they are more stable than class names or tag structure.

  3. SPA pages need wait before extraction — After open or click on single-page apps, the DOM isn't ready immediately. Always wait selector or wait text before eval.

  4. Use state before clicking — Run opencli browser state to inspect available interactive elements and their indices. Never guess indices from memory.

  5. evaluate runs in browser context — page.evaluate() in adapters executes inside the browser. Node.js APIs (fs, path, process) are NOT available. Use fetch() for network calls, DOM APIs for page data.

  6. Backticks in page.evaluate break JSON storage — When writing adapters that will be stored/transported as JSON, avoid template literals inside page.evaluate. Use string concatenation or function-style evaluate:

    typescript
    // BAD: template literal backticks break when adapter is in JSON
    page.evaluate(`document.querySelector("${selector}")`)
    // GOOD: function-style evaluate
    page.evaluate((sel) => document.querySelector(sel), selector)

Troubleshooting

ErrorFix
"Browser not connected"Run opencli doctor
"attach failed: chrome-extension://"Disable 1Password temporarily
Element not foundopencli browser scroll down && opencli browser state
Stale indices after page changeRun opencli browser state again to get fresh indices

© joeseesun, MIT. 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 qiaomu-opencli-browser of joeseesun/qiaomu-opencli-skills.

Open the folder on GitHubat commit 4d9a08e

Compare with similar skills

Qiaomu Opencli Browser 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.

Qiaomu Opencli Browser compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Qiaomu Opencli Browser this skilljoeseesun/qiaomu-opencli-skills993—~3.4kAutomated safety check: PassMIT
Dingo VerifyMigoXLab/dingo757—~833Automated safety check: PassApache-2.0
Agnes Free Textkangarooking/agnes-free-model-skills199—~630Automated safety check: PassMIT
Openai Docstheowenyoung/home1151 repos~1.4kAutomated safety check: PassApache-2.0
AIbutterbase-ai/butterbase-skills534—~1.1kAutomated safety check: PassMIT
Building Streamlit Chat UIiusztinpaul/designing-real-world-ai-agents-workshop512—~1.4kAutomated safety check: PassApache-2.0

Similar skills

  • Dingo Verify

    MigoXLab/dingo

    A skill your agent uses when the user wants to fact-check an article or verify factual claims in a document.

    757 GitHub stars~833 tokensUpdated 11 days ago
    AI & LLM EngineeringAuto-check passed
  • Agnes Free Text

    kangarooking/agnes-free-model-skills

    Call the free Agnes text model API for chat completions, streaming answers, coding help, tool-calling experiments, and OpenAI-compatible text generation.

    199 GitHub stars~630 tokensUpdated 4 mo ago
    AI & LLM EngineeringAuto-check passed
  • Openai Docs

    theowenyoung/home

    A skill your agent uses for Codex models/pricing, scheduled tasks, skills, settings, setup, troubleshooting, customization, automations, and self-knowledge—including 'you,' 'your,' 'this app,' or…

    115 GitHub starsUsed in 1 repo~1.4k tokens
    AI & LLM EngineeringAuto-check passed
  • AI

    butterbase-ai/butterbase-skills

    A skill your agent uses when calling the app's AI gateway from agent tools — chat completions, embeddings, listing models, configuring defaults or BYOK, reading token/cost usage

    534 GitHub stars~1.1k tokensUpdated 4 days ago
    AI & LLM EngineeringAuto-check passed
  • Building Streamlit Chat UI

    iusztinpaul/designing-real-world-ai-agents-workshop

    Building chat interfaces in Streamlit. An agent skill from iusztinpaul/designing-real-world-ai-agents-workshop.

    512 GitHub stars~1.4k tokensUpdated 4 mo ago
    AI & LLM EngineeringAuto-check passed
  • Instructor Structured LLM Outputs

    Orchestra-Research/AI-Research-SKILLs

    Shows how to pull validated, typed data out of LLM responses with Instructor and Pydantic models, including retries on failure and partial streaming.

    13k GitHub starsUsed in 6 repos~4.2k tokens
    AI & LLM EngineeringAuto-check passed

More from joeseesun/qiaomu-opencli-skills

  • Qiaomu Opencli Oneshot

    joeseesun/qiaomu-opencli-skills

    A skill your agent uses when quickly generating a single OpenCLI command from a specific URL and goal description.

    993 GitHub stars~1.4k tokensUpdated 6 mo ago
    Auto-check passed
  • Qiaomu Opencli Usage

    joeseesun/qiaomu-opencli-skills

    A skill your agent uses when running OpenCLI commands to interact with websites (Bilibili, Twitter, Reddit, Xiaohongshu, etc.), desktop apps (Cursor, Notion), or public APIs (HackerNews, arXiv).

    993 GitHub stars~3k tokensUpdated 6 mo ago
    Auto-check passed
  • Qiaomu Opencli Explorer

    joeseesun/qiaomu-opencli-skills

    A skill your agent uses when creating a new OpenCLI adapter from scratch, adding support for a new website or platform, exploring a site's API endpoints via browser DevTools, or when a user asks to…

    993 GitHub stars~6.4k tokensUpdated 6 mo ago
    Auto-check passed
  • Qiaomu Opencli Autofix

    joeseesun/qiaomu-opencli-skills

    Automatically fix broken OpenCLI adapters when commands fail.

    993 GitHub stars~2.4k tokensUpdated 6 mo ago
    Auto-check passed

Questions about Qiaomu Opencli Browser

What does Qiaomu Opencli Browser do?

Make websites accessible for AI agents. An agent skill from joeseesun/qiaomu-opencli-skills. Qiaomu Opencli Browser is an agent skill from joeseesun/qiaomu-opencli-skills. Make websites accessible for AI agents.

When should I use Qiaomu Opencli Browser?

Qiaomu Opencli Browser fits situations like: tasks that involve LLM API integration.

How do I install Qiaomu Opencli Browser in Claude Code?

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

How do I install Qiaomu Opencli Browser in Codex?

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

Can I use Qiaomu Opencli Browser 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 joeseesun/qiaomu-opencli-skills --skill qiaomu-opencli-browser -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/qiaomu-opencli-browser, .gemini/skills/qiaomu-opencli-browser, .github/skills/qiaomu-opencli-browser and .opencode/skills/qiaomu-opencli-browser in your project.

What does Qiaomu Opencli Browser need to run?

SKILL.md names no scripts, command-line tools or credentials: Qiaomu Opencli Browser is instructions for the agent only. Its frontmatter pre-approves these tools: Bash(opencli:*), Read, Edit, Write.

Does Qiaomu Opencli Browser access the network?

SKILL.md names 4 domains. In commands or code: news.ycombinator.com, hacker-news.firebaseio.com, httpbin.org and github.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Qiaomu Opencli Browser 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 Qiaomu Opencli Browser use?

Qiaomu Opencli Browser is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Qiaomu Opencli Browser use?

About 3.4k tokens (SKILL.md is roughly 13k 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 Qiaomu Opencli Browser?

Skills that share tags, products or a category with Qiaomu Opencli Browser: Dingo Verify (MigoXLab/dingo, 757 stars), Agnes Free Text (kangarooking/agnes-free-model-skills, 199 stars), Openai Docs (theowenyoung/home, 115 stars) and AI (butterbase-ai/butterbase-skills, 534 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Qiaomu Opencli Browser?

joeseesun (a GitHub user) maintains it in joeseesun/qiaomu-opencli-skills, which has 993 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on April 9, 2026.

Source: joeseesun/qiaomu-opencli-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.