Skill
Zhihu Automation Skill
知乎内容辅助工具。支持查看文章、搜索问题、提取热榜/用户数据。 提供浏览器操作辅助,Cookie 加密存储。
When to use Zhihu Automation Skill
Choose if
You need an agent to operate Zhihu — publish articles/thoughts/answers, search questions, perform likes/comments/follows, extract trending lists or user profiles — with encrypted cookie persistence and human-confirmation gates on publishing actions. Picks over generic browser automation when you want Zhihu-aware selectors and rate-limit defaults baked in.
Avoid if
You want unattended Zhihu posting at scale — the README requires explicit user confirmation before publish, and enforces 200-500ms HTTP / 5-10s browser intervals. Also avoid if you cannot maintain cookies (~30-day expiry per README) or run Playwright + Python 3 in your environment. Selector breakage on Zhihu UI updates is a known risk.
Risk Flags
- MEDIUM rate_limit README documents frequency limits — 200-500ms between HTTP calls and 5-10s between browser actions; agents on heavy workloads must throttle.
- MEDIUM auth README states Zhihu cookies expire after roughly 30 days and require manual re-login. ZHIHU_COOKIE_KEY (32-char hex) is mandatory for encrypted cookie storage.
- MEDIUM scope README requires AI to display a preview and wait for explicit user confirmation before any publishing action ("所有发布操作前 AI 必须展示预览并等待用户明确确认"). Not safe for fully unattended posting.
- LOW scope Selector brittleness — README acknowledges Zhihu UI updates ("知乎改版") can break selectors; auto-recovery exists for browser crashes but is not guaranteed.
Cost
Type: Unknown
Dependencies
Minimum runtime: Node.js with Playwright (Chromium) plus Python 3 per README
Distribution
- ClawHub
zhihu-auto-skill- License
- MIT-0