opencli▌
joeseesun/opencli-skill · updated May 19, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
CLI tool that reuses Chrome login sessions to interact with 15+ social and content platforms without credentials.
- ›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
opencli
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.
Syntax
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
Quick Examples
# 读取/浏览
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
Output Formatting Rules
When displaying results to the user:
- Always show original title + Chinese translation + clickable link as separate columns
- Table format:
# | 原标题 | 中文翻译 | 链接 | 关键指标... - 原标题: plain text, no markdown link — do NOT use
[title](url)format - 中文翻译: plain Chinese translation text
- 链接:
[🔗](url)— compact clickable icon - Translate all English titles to Chinese — never show English-only output to the user
Example:
| # | 原标题 | 中文翻译 | 链接 | 分 | 评论 |
|---|--------|---------|------|-----|------|
| 1 | The 49MB web page | 那个 49MB 的网页 | [🔗](https://...) | 388 | 196 |
Fallback 策略:opencli 不支持时用 Playwright
核心原则:永远不说"不支持",先尝试 opencli,失败或无命令时自动切换 Playwright。
决策流程
用户请求
↓
opencli 有对应命令?
├─ 是 → 执行 opencli
└─ 否 → 直接用 Playwright MCP 打开对应页面完成任务
↓
Playwright 报错 / 无法连接?
└─ 引导用户安装桥接插件(见下方)
常见 opencli 不支持场景 → 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 |
Playwright 操作标准流程
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 已登录目标网站
- 重新告诉我你的需求,我来帮你完成"
Requirements
- Chrome browser open with target site logged in
- Playwright MCP Bridge extension installed in Chrome(未安装时见上方引导)
自迭代能力:为新网站创建 CLI
当 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 → 验证输出
YAML 格式(DOM 抓取模板)
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, ...]
已创建的自定义 CLI
| 站点 | 命令 | 文件 | 关键选择器 |
|---|---|---|---|
| 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('...').innerHTML- 找
data-test属性最稳定,其次 class 中的语义词 - tagline 通常是 name 的兄弟元素(
nameEl.parentElement.querySelector('span...')) - 去重用
seen = new Set(),防止重复产品
Full Command Reference
See references/commands.md for all 55 commands with complete argument details.
How to use opencli on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add opencli
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches opencli from GitHub repository joeseesun/opencli-skill and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate opencli. Access the skill through slash commands (e.g., /opencli) or your agent's skill management interface.
Security & Verification Notice
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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
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
Competitive Analysis
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
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
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
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ 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.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.7★★★★★53 reviews- ★★★★★Kiara Kim· Dec 28, 2024
opencli is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Shikha Mishra· Dec 16, 2024
We added opencli from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Nikhil Chen· Dec 16, 2024
opencli reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Kofi Gupta· Dec 12, 2024
Registry listing for opencli matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Zaid Mehta· Dec 4, 2024
opencli has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Chen Kapoor· Dec 4, 2024
Useful defaults in opencli — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Nia Johnson· Nov 23, 2024
I recommend opencli for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Kaira Garcia· Nov 19, 2024
Keeps context tight: opencli is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Sakshi Patil· Nov 15, 2024
opencli fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Yash Thakker· Nov 7, 2024
opencli reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 53