快手数据分析 SocialDataX 作品详情

Use this skill when the user wants 快手作品详情, Kuaishou work details, interaction metrics, content research, or a structured view of one Kuaishou work.

Current platform support:

• Kuaishou / 快手 works through the kuaishou_get_video_detail_by_* tools.

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

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 detail \
  --photo-id "<photo_id>" --pretty --source-client socialdatax-skills \
  --source-platform clawhub --source-skill socialdatax-kuaishou-detail

npx -y socialdatax-skills@latest kuaishou detail \
  --url "<kuaishou_content_url_or_share_text>" --pretty \
  --source-client socialdatax-skills --source-platform clawhub \
  --source-skill socialdatax-kuaishou-detail

Optional arguments:

• --pretty: output formatting only.
• Kuaishou --photo-id <photo_id>: preferred when the Kuaishou work photo_id is already known.
• Kuaishou --url <kuaishou_content_url_or_share_text>: use for a Kuaishou work page URL, short link, or share text.
• --source-client socialdatax-skills --source-platform clawhub --source-skill socialdatax-kuaishou-detail: usage attribution for this Agent Skill; keep these values unchanged when running examples from this Skill.

Use either the ID option or the URL option for detail commands, not both.

The command prints JSON with platform, tool, arguments, and data.

Safety Boundary

This skill is read-only for SocialDataX detail requests. 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. The optional Kuaishou local save command writes only to the requested local --output path or --output-dir directory and does not require SOCIALDATAX_API_KEY.

MCP Tools

MCP tools matching the direct CLI commands above:

• kuaishou_get_video_detail_by_photo_id
• kuaishou_get_video_detail_by_url

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

• kuaishou_get_video_detail_by_photo_id: use when a photo_id is already known.
• kuaishou_get_video_detail_by_url: use for Kuaishou work page URLs, short links, or share text.

Output Guidance

Return factual fields such as title or description, content, author, publish time, interaction counts, images, and media summary when available. When the user wants to save Kuaishou media after detail, pass each returned images[].url, video.play_url, or cover_image_url to npx -y socialdatax-skills@latest kuaishou download-media --url "<media_url>" --output-dir <directory> --pretty; this local save command does not require SOCIALDATAX_API_KEY. Detail access is read-only and does not provide account actions.

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.