快手评论分析 SocialDataX 评论洞察

Data & APIs

用于快手评论分析、快手评论回复、快手评论洞察、用户反馈、口碑分析、痛点总结和内容讨论分析。覆盖 Kuaishou / Kwai comments and comment replies,来自 SocialDataX 社媒数据助手。

Install

openclaw skills install socialdatax-kuaishou-comments
<!-- AUTO-GENERATED from socialdatax-skill-source. Do not edit directly; run `node scripts/generate_socialdatax_skills.mjs`. -->

快手评论分析 SocialDataX 评论洞察

Use this skill when the user wants 快手评论分析, Kuaishou / 快手 first-level comments, comment replies, audience feedback, sentiment themes, objections, pain points, FAQ extraction, or discussion summaries.

Current platform support:

  • Kuaishou / 快手 works through the kuaishou_get_video_comments_by_* and kuaishou_get_video_comment_replies_by_comment_id tools.

API Key

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;不要引导用户使用其他域名。

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 kuaishou comments --photo-id "<photo_id>" --pretty
npx -y socialdatax-skills@latest kuaishou comments --url "<kuaishou_content_url_or_share_text>" --pretty
npx -y socialdatax-skills@latest kuaishou replies --photo-id "<photo_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 back exactly the token returned by the previous page and do not reuse it across content items or comments.
  • --pretty: output formatting only.
  • Kuaishou --photo-id <photo_id>: preferred when the Kuaishou work photo_id is already known and should anchor the comment thread.

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.

Safety Boundary

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

MCP tools matching the direct CLI commands above:

  • kuaishou_get_video_comments_by_photo_id
  • kuaishou_get_video_comments_by_url
  • kuaishou_get_video_comment_replies_by_comment_id

If MCP tools are already available in the current agent, use one of these tools:

  • kuaishou_get_video_comments_by_photo_id: use when the photo_id is known.
  • kuaishou_get_video_comments_by_url: use for Kuaishou work page URLs, short links, or share text.
  • kuaishou_get_video_comment_replies_by_comment_id: use when the photo_id and first-level comment ID are known.

Comment pagination uses page_token. Pass back exactly the returned next_page_token; tokens are bound to the current content item or first-level comment. Continue only when next_page_token is non-empty.

Output Guidance

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.