原始内容
name: "socialdatax-xhs" description: "用于小红书数据助手、小红书搜索热榜、小红书数据分析、小红书笔记搜索、笔记详情、评论分析、博主数据和博主笔记。覆盖 Xiaohongshu / XHS / RedNote,来自 SocialDataX 社媒数据助手。" source_client: "socialdatax-skills" source_platform: "clawhub" source_skill: "socialdatax-xhs" metadata: {"openclaw":{"requires":{"env":["SOCIALDATAX_API_KEY"],"bins":["node","npm"]},"primaryEnv":"SOCIALDATAX_API_KEY","install":[{"kind":"node","package":"socialdatax-skills","bins":[]}],"emoji":"📕","homepage":"https://socialdatax.com/ai?from=clawhub"}}
小红书数据助手 SocialDataX
Use this skill when the user needs a Xiaohongshu / 小红书 / XHS / RedNote data assistant for search hot list, content research, note search, note details, comment analysis, creator profile lookup, or creator note lists.
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;不要引导用户使用其他域名;do not infer alternate domains。
Preferred Direct CLI
Choose the matching SocialDataX command:
npx -y socialdatax-skills@latest xhs hot-search \
--pretty --source-client socialdatax-skills --source-platform clawhub \
--source-skill socialdatax-xhs
npx -y socialdatax-skills@latest xhs search \
--keyword "<keyword>" --pretty --source-client socialdatax-skills \
--source-platform clawhub --source-skill socialdatax-xhs
npx -y socialdatax-skills@latest xhs search \
--keyword "<keyword>" --pages 3 --pretty --source-client socialdatax-skills \
--source-platform clawhub --source-skill socialdatax-xhs
npx -y socialdatax-skills@latest xhs detail \
--note-id "<note_id>" --pretty --source-client socialdatax-skills \
--source-platform clawhub --source-skill socialdatax-xhs
npx -y socialdatax-skills@latest xhs detail \
--url "<note_url_or_share_text>" --pretty --source-client socialdatax-skills \
--source-platform clawhub --source-skill socialdatax-xhs
npx -y socialdatax-skills@latest xhs comments \
--note-id "<note_id>" --pretty --source-client socialdatax-skills \
--source-platform clawhub --source-skill socialdatax-xhs
npx -y socialdatax-skills@latest xhs comments \
--note-id "<note_id>" --all --include-replies --pretty \
--source-client socialdatax-skills --source-platform clawhub \
--source-skill socialdatax-xhs
npx -y socialdatax-skills@latest xhs comments \
--url "<note_url_or_share_text>" --pretty --source-client socialdatax-skills \
--source-platform clawhub --source-skill socialdatax-xhs
npx -y socialdatax-skills@latest xhs sub-comments \
--note-id "<note_id>" --comment-id "<comment_id>" --pretty \
--source-client socialdatax-skills --source-platform clawhub \
--source-skill socialdatax-xhs
npx -y socialdatax-skills@latest xhs user-info \
--user-id "<user_id>" --pretty --source-client socialdatax-skills \
--source-platform clawhub --source-skill socialdatax-xhs
npx -y socialdatax-skills@latest xhs user-info \
--profile-url "<profile_url_or_share_text>" --pretty \
--source-client socialdatax-skills --source-platform clawhub \
--source-skill socialdatax-xhs
npx -y socialdatax-skills@latest xhs user-posts \
--user-id "<user_id>" --pretty --source-client socialdatax-skills \
--source-platform clawhub --source-skill socialdatax-xhs
npx -y socialdatax-skills@latest xhs user-posts \
--user-id "<user_id>" --all --pretty --source-client socialdatax-skills \
--source-platform clawhub --source-skill socialdatax-xhs
npx -y socialdatax-skills@latest xhs user-posts \
--profile-url "<profile_url_or_share_text>" --pretty \
--source-client socialdatax-skills --source-platform clawhub \
--source-skill socialdatax-xhs
Required arguments:
- XHS
hot-search: no required arguments.
Optional arguments:
- XHS comments
--sort-type <default|time_descending|like_count_descending>: optional first-level comment sort order; omit it for the platform default order. --source-client socialdatax-skills --source-platform clawhub --source-skill socialdatax-xhs: usage attribution for this Agent Skill; keep these values unchanged when running examples from this Skill.
Use hot-search for 小红书搜索热榜, search for 小红书数据分析 and note discovery, detail for one note, comments for comment analysis and replies, user-info for 博主信息, and user-posts for 博主笔记.
Safety Boundary
This skill is read-only. 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.
MCP Tools
MCP tools matching the direct CLI commands above:
xhs_get_search_hot_listxhs_search_notesxhs_get_note_detail_by_note_idxhs_get_note_detail_by_note_urlxhs_get_note_comments_by_note_idxhs_get_note_comments_by_note_urlxhs_get_note_sub_comments_by_comment_idxhs_get_user_info_by_user_idxhs_get_user_info_by_profile_urlxhs_get_user_posted_notes_by_user_idxhs_get_user_posted_notes_by_profile_url
XHS search parameter naming reminder: direct CLI uses --sort-type, --publish-time-range, and --note-type; the xhs_search_notes MCP tool uses sort_type, publish_time_range, and note_type. Do not pass sortType, publishTimeRange, or noteType.
Output Guidance
For XHS search or detail results, in every use of a returned note_url, such as final answers, display, references, storage, output, or forwarding, preserve it exactly as the full URL, including xsec_token query parameters. Do not modify, truncate, redact, mask, normalize, rebuild, or synthesize the URL from note_id; if detail note_url is null, show the note_id or say that no directly openable full link is available.
For XHS note_id, copy the complete 24-character lowercase hexadecimal ID exactly; do not pass or display only a prefix.
Troubleshooting
- 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_balanceor 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_KEYbelongs to the same account that was recharged; if needed, copy a fresh API Key from the official dashboard.