快手达人数据 SocialDataX 达人信息
用于快手达人数据、快手达人信息、账号资料、创作者画像、主页信息和粉丝规模查询。覆盖 Kuaishou / Kwai creator profiles,来自社媒数据助手 SocialDataX。
快手达人数据 SocialDataX 达人信息
Use this skill when the user wants 快手达人数据, creator profile lookup, account basics, creator positioning, audience scale, or Kuaishou profile information.
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 / 快手 creators through the
kuaishou_get_user_info_by_*tools. - Kuaishou / 快手 creator discovery through
kuaishou_search_usersbefore profile lookup when only an account keyword or niche is known.
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 user-search \
--keyword "<creator_keyword>" --pretty --source-client socialdatax-skills \
--source-platform clawhub --source-skill socialdatax-kuaishou-creator-profile
npx -y socialdatax-skills@latest kuaishou user-search \
--keyword "<creator_keyword>" --pages 3 --pretty --source-client socialdatax-skills \
--source-platform clawhub --source-skill socialdatax-kuaishou-creator-profile
npx -y socialdatax-skills@latest kuaishou user-info \
--user-id "<user_id>" --pretty --source-client socialdatax-skills \
--source-platform clawhub --source-skill socialdatax-kuaishou-creator-profile
npx -y socialdatax-skills@latest kuaishou user-info \
--profile-url "<profile_url_or_share_text>" --pretty \
--source-client socialdatax-skills --source-platform clawhub \
--source-skill socialdatax-kuaishou-creator-profile
Optional arguments:
--pretty: output formatting only.- Kuaishou
user-search --keyword <creator_keyword>: use when the user only has a creator name, account keyword, or niche and needs possible Kuaishou user_id candidates before profile lookup. - Kuaishou user-search
--page-token <next_page_token>: opaque pagination token; omit it on the first request and continue only with the complete returnednext_page_tokenfrom the same creator-search chain. - Kuaishou user-search
--pages <n>and--max-items <n>: fetch and merge bounded creator-search pages; user-search does not support--since-daysbecause creator search results are accounts, not published content items. - Kuaishou
--user-id <user_id>: use only when a non-empty creator user_id is already known. - Kuaishou
--profile-url <profile_url_or_share_text>: use for a profile URL, short link, or profile share text. Live/fw-user profile shares are supported; successful profile results return a reusable non-empty user_id. --source-client socialdatax-skills --source-platform clawhub --source-skill socialdatax-kuaishou-creator-profile: usage attribution for this Agent Skill; keep these values unchanged when running examples from this Skill.
Use exactly one supported identifier or URL entrypoint for a single command; do not combine them.
The command prints JSON with platform, tool, arguments, and data.
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_search_userskuaishou_get_user_info_by_user_idkuaishou_get_user_info_by_profile_url
If MCP tools are already available in the current agent, use one of these tools:
kuaishou_search_users: use when the user only has a creator keyword and needs possible Kuaishou user_id candidates. Passkeyword; passpage_tokenonly for continuation. Do not passpage.kuaishou_get_user_info_by_user_id: preferred when a non-emptyuser_idis already known.kuaishou_get_user_info_by_profile_url: use for profile URLs, short links, or profile share text, including live/fw-user profile shares; successful results return a reusable non-emptyuser_id.
Output Guidance
Report profile fields such as name, platform IDs, bio, verification, follower count, following count, received like count, IP location, and gender when available. Separate profile facts from strategic interpretation.
For Kuaishou creator search results, present account candidates separately from confirmed profile facts; use a returned user_id for profile lookup when the user chooses a candidate.
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. - 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
