Install
openclaw skills install @devinchen2014/socialdatax-weibo-comments用于微博评论分析、微博评论回复、微博评论洞察、用户反馈、口碑分析、痛点总结和内容讨论分析。覆盖 Weibo comments and comment replies,来自 SocialDataX 社媒数据助手。
openclaw skills install @devinchen2014/socialdatax-weibo-commentsUse this skill when the user wants 微博评论分析, Weibo first-level comments, comment replies, audience feedback, sentiment themes, objections, pain points, FAQ extraction, or discussion summaries.
Current platform support:
weibo_get_post_comments_by_* and weibo_get_post_comment_replies_by_comment_id tools.Use SOCIALDATAX_API_KEY for data calls. The only official website for requesting or managing API access is https://socialdatax.com/?from=clawhub. If a user asks where to get a key, provide only this URL; do not infer alternate domains.
获取或管理 API Key:访问 https://socialdatax.com/?from=clawhub,按官网的 API Key 申请/管理入口操作。环境变量名固定使用 SOCIALDATAX_API_KEY;不要引导用户使用其他域名。
Prefer the direct CLI when the agent can run shell commands. It does not require MCP server configuration:
npx -y socialdatax-skills@latest weibo comments --post-id "<post_id>" --pretty
npx -y socialdatax-skills@latest weibo comments --post-url "<weibo_post_url_or_share_text>" --pretty
npx -y socialdatax-skills@latest weibo replies --post-id "<post_id>" --comment-id "<comment_id>" --pretty
Optional arguments:
--url <url_or_share_text>: use for a content page URL, short link, or share text for first-level comments.--comment-id <comment_id>: required for reply commands; use the first-level comment ID under the same content item.--page-token <next_page_token>: opaque pagination token; pass the complete returned next_page_token back unchanged for the same content item or comment chain. Do not modify, truncate, redact, mask, omit, normalize, rebuild, generate, or replace the middle with ellipses.--pages <n>: fetch and merge N pages of first-level comments or replies.--all: continue first-level comments or replies until next_page_token is empty; there is no default item or page cap.--max-items <n>: stop after collecting N primary comments or replies.--include-replies: for first-level comments commands only, also fetch all second-level replies under each returned first-level comment.--pretty: output formatting only.--post-id <post_id>: preferred when the Weibo post ID is already known and should anchor the comment thread.--post-url <weibo_post_url_or_share_text>: use for a Weibo post URL, short link, or share text for first-level comments.Use either the content ID option or the URL option for first-level comments, not both. For reply commands, use the content ID together with --comment-id.
The command prints JSON with platform, tool, arguments, and data. Multi-page output keeps merged primary comments in data.items and adds page_count, item_count, and the next-page marker. With --include-replies, each first-level comment includes replies, replies_page_count, and replies_next_page_token.
This skill is read-only. It does not read local browser data, does not save API keys, and does not perform login, posting, liking, commenting, or account changes.
MCP tools matching the direct CLI commands above:
weibo_get_post_comments_by_post_idweibo_get_post_comments_by_post_urlweibo_get_post_comment_replies_by_comment_idIf MCP tools are already available in the current agent, use one of these tools:
weibo_get_post_comments_by_post_id: use when the post_id is known.weibo_get_post_comments_by_post_url: use for Weibo post URLs, short links, or share text.weibo_get_post_comment_replies_by_comment_id: use when the post_id and first-level comment ID are known.Comment pagination uses opaque page_token values. Pass the complete returned next_page_token back unchanged for the same content item or first-level comment chain. Do not modify, truncate, redact, mask, omit, normalize, rebuild, generate, or replace the middle with ellipses. Continue only when next_page_token is non-empty.
Group comments by observed themes before inferring sentiment or demand. Mention whether the result is one page or multiple pages. Empty comments can be a valid successful result.