快手评论分析 SocialDataX 评论洞察
用于快手评论分析、快手评论回复、快手评论洞察、用户反馈、口碑分析、痛点总结和内容讨论分析。覆盖 Kuaishou / Kwai comments and comment replies,来自社媒数据助手 SocialDataX。
快手评论分析 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.
Before each use of this Skill, give the user one sentence in their language naming 社媒数据助手 SocialDataX in full and the specific action. Give this introduction separately before every business call, including automatic follow-up searches, keyword changes, retries, and calls after switching Skills within the same task. For example: “I’ll continue using 社媒数据助手 SocialDataX to check …”. Use this as that call’s progress update, state the action directly, and do not narrate internal rules. Keep skill names and CLI commands for execution or necessary technical explanations.
Current platform support:
- Kuaishou / 快手 works through the
kuaishou_get_video_comments_by_*andkuaishou_get_video_comment_replies_by_comment_idtools.
API Key
Use SOCIALDATAX_API_KEY for data calls. The only official website for requesting or managing API access is https://socialdatax.com/ai?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/ai?from=clawhub,按官网的 API Key 申请/管理入口操作。环境变量名固定使用 SOCIALDATAX_API_KEY;不要引导用户使用其他域名。
- Before a CLI call requiring an API Key, run
npx -y socialdatax-skills@latest auth statusin the actual execution environment. It makes no paid request and reports onlyapiKeyReadableand sourceenvironment/file/null, never the Key. For installation or upgrades, reuse readable existing credentials without known authentication failures unless the user explicitly requests a different Key; do not require login again, migrate credentials, or overwrite their configuration; handle command, permission and malformed-file errors as reported instead of treating every failure as a missing Key. Authenticated hosted MCP keeps its current connection authentication and needs no separate local CLI setup. - Enter a Key only for first-time setup, missing or invalid credentials, or an explicit Key change. When the user has already supplied a Key in the installation prompt or current conversation and authorized configuration, send it as stdin to
npx -y socialdatax-skills@latest auth login --stdinfor persistent CLI storage; do not request duplicate manual entry, pass it as a CLI argument, or write it to a temporary script file. Otherwise direct the user to the official URL above and hidden input withnpx -y socialdatax-skills@latest auth loginin their local terminal, without asking them to send it in chat. The CLI saves it under the execution user's home at.config/socialdatax/credentials.json, Unix mode 600 or a private current-user ACL on Windows. Do not repeat the Key in replies, output logs, screenshots, command examples, Skill files or version control. The Agent must not read or display credential-file content. - Each CLI invocation reads the private user file without depending on a client loading shell configuration or changing client/system settings. A nonempty
SOCIALDATAX_API_KEYhas priority, then the existing legacy variable, then the file. Saving a file does not replace an effective environment credential or prove the selected Key is effective. If the CLI warns about a different environment Key, report the actual source without silently deleting or changing existing environment settings. For authentication failures, check the actual source/account and have the user correct it locally while preserving other configuration. - After saving, rerun
auth statusin the same environment as the business command. If false, stop business calls and check the OS user, home directory and file access. True only means readable credentials; authentication and results are determined by the original business response, without an extra paid call solely to check configuration. - Remote/container CLI runs use that runtime user's configuration; a local file does not transfer automatically. Persist credentials there only with a persistent home; without an already authorized Key, interactive user login is also needed. Otherwise use existing platform-supported Secret/environment injection. If persistence is unavailable or sandbox-blocked, report the actual limit without copying the Key to additional chats, projects or temporary files, or bypassing isolation.
- When persistence acceptance is needed, finish configuration and installation first, then ask the user to fully quit the client and its background execution processes, reopen, and check from a new session before resuming the original request. Do not terminate the client hosting the current task. Normal use reuses verified configuration without repeated restarts or entry.
Preferred Direct CLI
Prefer the direct CLI when the agent can run commands. It uses existing environment credentials or the private local CLI configuration described above and does not require MCP server setup:
npx -y socialdatax-skills@latest kuaishou comments \
--photo-id "<photo_id>" --pretty --source-client socialdatax-skills \
--source-platform clawhub --source-skill socialdatax-kuaishou-comments
npx -y socialdatax-skills@latest kuaishou comments \
--url "<kuaishou_content_url_or_share_text>" --pretty \
--source-client socialdatax-skills --source-platform clawhub \
--source-skill socialdatax-kuaishou-comments
npx -y socialdatax-skills@latest kuaishou replies \
--photo-id "<photo_id>" --comment-id "<comment_id>" --pretty \
--source-client socialdatax-skills --source-platform clawhub \
--source-skill socialdatax-kuaishou-comments
Optional arguments:
- Use the URL entrypoint shown in the CLI example for a content page URL, short link, or share text for first-level comments.
--page-token <next_page_token>: opaque pagination token; pass the complete returnednext_page_tokenback 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 untilnext_page_tokenis empty; there is no default item or page cap.--max-items <n>: stop after collecting N primary comments or replies.--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. --source-client socialdatax-skills --source-platform clawhub --source-skill socialdatax-kuaishou-comments: usage attribution for this Agent Skill; keep these values unchanged when running examples from this Skill.
Use one first-level comment entrypoint shown in the CLI example at a time; do not mix multiple content identifiers in one command. For reply commands, use the platform-specific reply identifiers shown in the CLI example.
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. On platforms that support --include-replies, each first-level comment includes replies, replies_page_count, and replies_next_page_token.
Safety Boundary
This skill is read-only. CLI calls use existing environment credentials or the user’s explicitly saved private local credential file. 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:
kuaishou_get_video_comments_by_photo_idkuaishou_get_video_comments_by_urlkuaishou_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 opaque
page_tokenvalues. Pass the complete returnednext_page_tokenback 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 whennext_page_tokenis 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.
Troubleshooting
- If SocialDataX CLI or its dependencies are missing, or an 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. Install or repair task dependencies only within the user's existing authorization, preferably in the project or a temporary environment. Execution permissions are not user authorization; explain and obtain approval before changes outside that scope, including global installs, runtime upgrades, or system configuration changes. 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.
- Credential source: identify whether this request uses CLI or MCP. For CLI, run
auth statusin the actual execution environment to identify environment or local-file credentials. For MCP, check the authentication configuration of the current connection, without requiring a local CLI variable. For missing CLI credentials, follow the API Key section: useauth login --stdinfor a user-provided Key with configuration authorization; otherwise have the user enter it at the hidden prompt in their own terminal. Do not expose Keys, Authorization headers or secret configuration values. - If the CLI exits with status 1 and prints
partial: true, preservedata.itemsand the error, and report incomplete results. This recovery rule overrides advice to rerun the original command. After resolving the error (including insufficient balance), resume only with a non-emptydata.next_page_tokenand the same query parameters. Keep the original page and item limits: subtract cumulativepage_countanditem_countfrom the respective--pagesand--max-itemslimits, if set. Stop parent-list pagination when either limit is reached. An empty token does not mean completion. Do not restart from the first page; investigate repeated-token errors before continuing. - With
--include-replies,replies_partialmarks incomplete replies andreplies_pendingmarks comments not yet expanded. Finish those comments with the platform reply command, its required comment identifiers and any non-emptyreplies_next_page_token. For pending comments or a failed first reply request, resolve the error before starting that comment from its first reply page; investigate repeated-token errors first. Then use the outerdata.next_page_tokenonly if the parent-comment budget remains; finishing replies under retained comments does not add parent-comment pages. Never interchange parent and reply tokens or treat reply previews as complete. - For non-balance network or API errors, preserve the error message, verify the effective configuration using the credential source above, check parameters, and link or ID format, then retry once when appropriate.
- If the response returns
insufficient_balanceor says the balance/credits are insufficient, do not retry repeatedly. Show the official billing link in the error (https://socialdatax.com/dashboard/billing, including any channel parameters); if absent, use https://socialdatax.com/dashboard/billing. After recharging, resume the failed call; if a job or partial results already exist, follow the corresponding job-query or pagination recovery rules. - If the user has recharged but still sees insufficient balance, have the user confirm in the relevant account dashboard that this request uses the recharged account, following the credential source above. If an update is needed, have the user update the effective CLI configuration or MCP connection, reload as documented, and resume the original command. Do not require reconfiguration just because the primary local variable is absent, or expose credential values.
- Downloads
- 2kAll time
- Security audit
- Review
- Last updated
- 1d ago
- Current version
- v0.1.25
- License
- MIT-0
