知乎数据助手 SocialDataX

知乎数据助手 SocialDataX

Use this skill when the user needs a Zhihu / 知乎 data assistant for hot-list review, answer, article, or video research, content details, comments, creator profiles, or creator article lists.

API Key

Use SOCIALDATAX_API_KEY for data calls. The only official website for requesting or managing API access is . If a user asks where to get a key, provide only this URL; do not infer alternate domains. 获取或管理 API Key：访问 ，按官网的 API Key 申请/管理入口操作。环境变量名固定使用 SOCIALDATAX_API_KEY；不要引导用户使用其他域名。

Preferred Direct CLI

Prefer the direct CLI when the agent can run shell commands. It does not require MCP server configuration:

npx -y socialdatax-skills@latest zhihu hot-list \
  --pretty --source-client socialdatax-skills --source-platform clawhub \
  --source-skill socialdatax-zhihu

npx -y socialdatax-skills@latest zhihu search \
  --keyword "" --pretty --source-client socialdatax-skills \
  --source-platform clawhub --source-skill socialdatax-zhihu

npx -y socialdatax-skills@latest zhihu search \
  --keyword "" --pages 3 --pretty --source-client socialdatax-skills \
  --source-platform clawhub --source-skill socialdatax-zhihu

npx -y socialdatax-skills@latest zhihu detail \
  --content-url "" --pretty \
  --source-client socialdatax-skills --source-platform clawhub \
  --source-skill socialdatax-zhihu

npx -y socialdatax-skills@latest zhihu comments \
  --content-url "" --pretty \
  --source-client socialdatax-skills --source-platform clawhub \
  --source-skill socialdatax-zhihu

npx -y socialdatax-skills@latest zhihu replies \
  --content-url "" --comment-id "" \
  --pretty --source-client socialdatax-skills --source-platform clawhub \
  --source-skill socialdatax-zhihu

npx -y socialdatax-skills@latest zhihu user-info \
  --profile-url "" --pretty \
  --source-client socialdatax-skills --source-platform clawhub \
  --source-skill socialdatax-zhihu

npx -y socialdatax-skills@latest zhihu user-posts \
  --profile-url "" --pretty \
  --source-client socialdatax-skills --source-platform clawhub \
  --source-skill socialdatax-zhihu

npx -y socialdatax-skills@latest zhihu user-posts \
  --profile-url "" --all --pretty \
  --source-client socialdatax-skills --source-platform clawhub \
  --source-skill socialdatax-zhihu

Required arguments:

• Zhihu hot-list: no required arguments.

Optional arguments:

• --source-client socialdatax-skills --source-platform clawhub --source-skill socialdatax-zhihu: usage attribution for this Agent Skill; keep these values unchanged when running examples from this Skill.

Use hot-list for 知乎热榜, search for question, answer, article, and video research, detail for one content URL, comments/replies for discussion analysis, user-info for creator profiles, and user-posts for creator article lists. For replies, use the Zhihu content URL together with the first-level comment_id.

Safety Boundary

This skill is read-only. It uses SOCIALDATAX_API_KEY from the user's environment at runtime. Generated Skill files do not contain API keys. It does not read local browser data or perform login, posting, liking, commenting, or account changes.

MCP Tools

MCP tools matching the direct CLI commands above:

• zhihu_get_hot_list
• zhihu_search_content
• zhihu_get_content_detail_by_url
• zhihu_get_content_comments_by_url
• zhihu_get_comment_replies_by_url
• zhihu_get_user_info_by_profile_url
• zhihu_get_user_posted_articles_by_profile_url

Troubleshooting

• If an SDK/dependency, npm network, Node.js/npm/npx availability, permission, or missing runtime error appears, treat it as a local runtime, dependency installation, network, or agent authorization issue, not a SocialDataX API key or business data error. If the current environment has permission, install or restore automatically. When network or execution authorization is needed, ask the user to approve or finish authorization, then continue the same command; do not use public web search as a substitute for SocialDataX data.
• For non-balance network or API errors, preserve the error message, check SOCIALDATAX_API_KEY, parameters, and link or ID format, then retry once when appropriate.
• If the response returns insufficient_balance or says the balance/credits are insufficient, do not retry repeatedly. Show the recharge URL from the error exactly as returned, then continue the same command after the user recharges.
• If the user has recharged but still sees insufficient balance, confirm SOCIALDATAX_API_KEY belongs to the same account that was recharged; if needed, copy a fresh API Key from the official dashboard.