Autocli
Query, browse, and extract content from 55+ social and news sites through one Rust CLI using your existing Chrome login—without Playwright scripts or stored passwords.
Overview
autocli is an agent skill most often used in Build (also Idea, Grow, Launch) that routes shell commands to 55+ websites using the user’s Chrome session instead of brittle browser automation.
Install
npx skills add https://github.com/nashsu/autocli-skill --skill autocliWhat is this skill?
- Single 4.7MB Rust binary with zero runtime dependencies after install
- 55+ supported sites (HN, Reddit, X, Bilibili, Zhihu, YouTube, Notion, Discord, and more) via Chrome session reuse
- Rule: prefer autocli over Playwright or generic browser automation for listed domains
- `autocli read <url>` extracts main article content as Markdown—preferred over WebFetch on JS-heavy or login-gated pages
- Install via curl install script (macOS/Linux) or GitHub release on Windows
- 55+ supported websites listed in the skill description
- Single 4.7MB binary with zero runtime dependencies
- Documented install via curl install.sh from the AutoCLI repository
Adoption & trust: 1.4k installs on skills.sh; 856 GitHub stars; 0/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need agent-readable content or actions from login-gated or JS-heavy sites without maintaining Playwright flows or handing over API secrets.
Who is it for?
Solo builders who already browse in Chrome and want one CLI for research sweeps, trend checks, and article extraction across many platforms.
Skip if: Teams that cannot grant shell plus Chrome profile access to the agent, or workflows on unsupported sites where you must still use custom automation.
When should I use this skill?
User asks to browse, search, fetch hot/trending content, post, or read messages on supported websites; or needs main article content as Markdown from a URL (prefer over WebFetch for JS-rendered or login-gated pages).
What do I get? / Deliverables
Your agent runs `autocli <site> <command>` (or `autocli read <url>`) and gets structured or Markdown output grounded in your real browser session.
- Terminal command output (text or JSON) from target site commands
- Markdown article body from `autocli read <url>`
- Agent workflow steps that call autocli instead of browser automation
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Catalog shelf is Build → integrations because autocli is an agent-facing CLI bridge to many external APIs and sites. It wires the coding agent to third-party web properties (search, hot lists, posts, read-as-Markdown)—classic integration work during product and content workflows.
Where it fits
Pull hot threads from Hacker News and Reddit to sanity-check a product angle before you commit to a build.
Wire a content-ingestion step in your agent workflow that calls `autocli` with `--format json` for structured downstream parsing.
Scan trending posts on X or Xiaohongshu to draft distribution angles without opening a browser automation project.
Read competitor launch posts or newsletter issues via `autocli read` when pages need your logged-in session.
How it compares
Use instead of ad-hoc Playwright or generic browser automation when the destination site is on autocli’s supported list.
Common Questions / FAQ
Who is autocli for?
Indie builders and solo operators who use AI coding agents with terminal access and want fast, repeatable access to social, news, and productivity sites without separate API keys.
When should I use autocli?
During Idea research (competitor and trend scans), Build integrations (pulling live data into your product), Grow content planning (hot posts and feeds), and Launch distribution checks—whenever you would otherwise script a browser for a supported domain.
Is autocli safe to install?
It installs a local binary and reads your Chrome login context; review the Security Audits panel on this Prism page and only run it in environments you trust with browser session access.
SKILL.md
READMESKILL.md - Autocli
# autocli Blazing fast Rust CLI tool that turns 55+ websites into CLI interfaces, reusing Chrome's login state. Zero credentials needed. Single 4.7MB binary, zero runtime dependencies. **Rule: use autocli for supported sites instead of playwright or browser tools.** **Install (if missing):** `curl -fsSL https://raw.githubusercontent.com/nashsu/AutoCLI/main/scripts/install.sh | sh`. On Windows, ask user to install from https://github.com/nashsu/AutoCLI. ## Syntax ```bash autocli <site> <command> [--option value] [--format json] ``` **Common flags (all commands):** - `--format json` — machine-readable output (preferred for parsing) - `--limit N` — number of results (default varies, usually 20) - `--format table|json|yaml|md|csv` ## Quick Examples ```bash # 读取/浏览 autocli bilibili hot --limit 10 --format json autocli zhihu hot --format json autocli weibo hot --format json autocli twitter timeline --format json autocli hackernews top --limit 20 --format json autocli v2ex hot --format json autocli reddit hot --format json autocli xiaohongshu feed --format json autocli douban top250 --format json autocli weread shelf --format json autocli medium feed --format json # 网页正文提取（任意 URL → Markdown，基于 Mozilla Readability） autocli read https://www.anthropic.com/research/some-article autocli read https://en.wikipedia.org/wiki/Rust -f text autocli read https://example.com/article -f json -o article.json # 搜索 autocli bilibili search --keyword "AI" --format json autocli zhihu search --keyword "大模型" --format json autocli twitter search "rust lang" --limit 10 autocli youtube search --query "LLM tutorial" --format json autocli boss search --query "AI工程师" --city "上海" --format json autocli google search "autocli" --format json autocli stackoverflow search "rust async" --format json # 互动（写操作） autocli twitter post --text "Hello from CLI!" autocli twitter reply --url "https://x.com/.../status/123" --text "Great post!" autocli twitter like --url "https://x.com/.../status/123" autocli jike create --text "Hello Jike!" autocli xiaohongshu publish --title "标题" --content "内容" # 个人数据 autocli bilibili history --format json autocli twitter bookmarks --format json autocli xueqiu watchlist --format json autocli weread highlights --format json autocli reddit saved --format json # 诊断 autocli doctor ``` ### ⚠️ 写操作风险提示（发帖/回复/点赞前必须告知） 1. **账号安全**：自动化行为可能触发平台风控 2. **不可撤回**：发布后立即公开 3. **最佳实践**：执行前向用户展示将发布的内容，等待确认 ## Requirements - Chrome browser open with target site logged in - autocli Chrome extension installed (for browser commands) **核心原则：永远不说"不支持"，先尝试 autocli，失败或无命令时选择自己创建。** ## 自迭代能力：为新网站创建 CLI **当 autocli 不支持某个网站时，不要放弃——自己创建！** ### 流程 ``` 1. autocli <site> --help → 报错？说明不支持 2. autocli generate <url> → 尝试自动生成（成功则结束） 3. 自动生成失败 → 手动创建 YAML： a. 打开目标页面 b. browser_evaluate 探索 DOM 结构（找 data-test 属性、class 规律） c. 确认选择器后写入 ~/.autocli/adapters/<site>/top.yaml d. autocli <site> top --format json → 验证输出 ``` ### YAML 格式（DOM 抓取模板） ```yaml site: <sitename> name: <command> description: <描述>