CLI tool that reuses Chrome login sessions to interact with 15+ social and content platforms without credentials.
Works with
Supports Bilibili, Zhihu, Twitter/X, YouTube, Weibo, 小红书, V2EX, Reddit, HackerNews, 雪球, BOSS直聘, and others with commands for browsing hot content, searching, posting, and reading messages
All commands accept -f json|table|yaml|md|csv for output formatting and --limit N to control result count
Falls back to Playwright browser automation for unsupported operations (DMs, not
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionopencliExecute the skills CLI command in your project's root directory to begin installation:
Fetches opencli from joeseesun/opencli-skill and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate opencli. Access via /opencli in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
6
total installs
6
this week
765
GitHub stars
0
upvotes
Run in your terminal
6
installs
6
this week
765
stars
CLI tool that turns websites into CLI interfaces, reusing Chrome's login state. Zero credentials needed.
Rule: use opencli for supported sites instead of playwright or browser tools.
opencli <site> <command> [--option value] [-f json]
Common flags (all commands):
-f json — machine-readable output (preferred for parsing)--limit N — number of results (default varies, usually 20)-f table|json|yaml|md|csv# 读取/浏览
opencli bilibili hot --limit 10 -f json
opencli zhihu hot -f json
opencli weibo hot -f json
opencli twitter timeline -f json
opencli hackernews top --limit 20 -f json
opencli v2ex hot -f json
opencli reddit hot -f json
opencli xiaohongshu feed -f json
# 搜索
opencli bilibili search --keyword "AI" -f json
opencli zhihu search --keyword "大模型" -f json
opencli twitter search --query "claude AI" -f json
opencli youtube search --query "LLM tutorial" -f json
opencli boss search --query "AI工程师" --city "上海" -f json
# 互动（写操作）
opencli twitter post --text "Hello from CLI!"
opencli twitter reply --url "https://x.com/.../status/123" --text "Great post!"
opencli twitter like --url "https://x.com/.../status/123"
# 个人数据
opencli bilibili history -f json
opencli twitter bookmarks -f json
opencli xueqiu watchlist -f json
When displaying results to the user:
# | 原标题 | 中文翻译 | 链接 | 关键指标...[title](url) format[🔗](url) — compact clickable iconExample:
| # | 原标题 | 中文翻译 | 链接 | 分 | 评论 |
|---|--------|---------|------|-----|------|
| 1 | The 49MB web page | 那个 49MB 的网页 | [🔗](https://...) | 388 | 196 |
核心原则：永远不说"不支持"，先尝试 opencli，失败或无命令时自动切换 Playwright。
用户请求
↓
opencli 有对应命令？
├─ 是 → 执行 opencli
└─ 否 → 直接用 Playwright MCP 打开对应页面完成任务
↓
Playwright 报错 / 无法连接？
└─ 引导用户安装桥接插件（见下方）
| 场景 | 网址 | Playwright 操作 |
|---|---|---|
| 知乎私信 | https://www.zhihu.com/messages |
navigate → snapshot 读取列表 |
| 知乎通知 | https://www.zhihu.com/notifications |
navigate → snapshot |
| 微博发帖 | https://weibo.com |
navigate → 点击输入框 → type → 发送 |
| 小红书私信 | https://www.xiaohongshu.com/im |
navigate → snapshot |
| B站私信 | https://message.bilibili.com |
navigate → snapshot |
| Twitter DM | https://x.com/messages |
navigate → snapshot |
1. mcp__playwright__browser_navigate → 目标 URL
2. mcp__playwright__browser_snapshot → 读取页面结构
3. 根据需要：browser_click / browser_type / browser_scroll
4. 将结果整理后呈现给用户
如果 Playwright 报错（连接失败 / 无法控制浏览器），告知用户：
"需要在 Chrome 安装 Playwright MCP Bridge 插件才能控制浏览器。 安装步骤：
- 打开 Chrome，访问 Chrome Web Store
- 搜索 "Playwright MCP" 或 "MCP Bridge"
- 点击「添加到 Chrome」
- 安装后确保 Chrome 已登录目标网站
- 重新告诉我你的需求，我来帮你完成"
当 opencli 不支持某个网站时，不要放弃——自己创建！
1. opencli <site> --help → 报错？说明不支持
2. opencli generate <url> → 尝试自动生成（成功则结束）
3. 自动生成失败 → 手动创建 YAML：
a. 用 Playwright 打开目标页面
b. browser_evaluate 探索 DOM 结构（找 data-test 属性、class 规律）
c. 确认选择器后写入 ~/.opencli/clis/<site>/top.yaml
d. opencli <site> top -f json → 验证输出
site: <sitename>
name: <command>
description: <描述>
domain: <domain>
strategy: public
browser: true
args:
limit:
type: int
default: 10
pipeline:
- navigate: https://<url>
- evaluate: |
(async () => {
const limit = ${{ args.limit }};
// DOM 抓取逻辑
return results;
})()
columns: [rank, name, ...]
| 站点 | 命令 | 文件 | 关键选择器 |
|---|---|---|---|
| producthunt | top |
~/.opencli/clis/producthunt/top.yaml |
button[data-test="vote-button"] → 父容器 → [data-test^="post-name-"]，tagline: nameEl.parentElement.querySelector('span.mt-0\\.5') |
browser_evaluate 先探结构：document.querySelector('...').innerHTMLdata-test 属性最稳定，其次 class 中的语义词nameEl.parentElement.querySelector('span...')）seen = new Set()，防止重复产品See references/commands.md for all 55 commands with complete argument details.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
jezweb/claude-skills
opencli is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
We added opencli from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
opencli reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for opencli matched our evaluation — installs cleanly and behaves as described in the markdown.
opencli has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in opencli — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend opencli for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: opencli is the kind of skill you can hand to a new teammate without a long onboarding doc.
opencli fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
opencli reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 53