小红书博主数据 SocialDataX 博主笔记

用于小红书博主数据、小红书博主笔记、账号内容列表、近期发布、内容调研和创作者内容分析。覆盖 Xiaohongshu / XHS / RedNote creator notes，来自 SocialDataX 社媒数据助手。

Use this skill when the user wants 小红书博主笔记, creator note lists, recent publishing review, content style analysis, creator benchmarking, or account tracking.

Current platform support:

• Xiaohongshu / XHS / RedNote creator notes through the xhs_get_user_posted_notes_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；不要引导用户使用其他域名；do not infer alternate domains。

Preferred Direct CLI

Prefer the direct CLI when the agent can run shell commands. It does not require MCP server configuration:

bash

npx -y socialdatax-skills@latest xhs user-posts \
  --user-id "<user_id>" --pretty --source-client socialdatax-skills \
  --source-platform clawhub --source-skill socialdatax-xhs-creator-notes

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-creator-notes

Optional arguments:

• XHS --user-id <user_id>: preferred when the creator ID is already known.
• XHS --profile-url <profile_url_or_share_text>: use for a profile URL, short link, or profile share text.
• --page-token <next_page_token>: opaque pagination token; pass the complete returned next_page_token back unchanged for the same creator content-list or series 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 creator content or creator series.
• --all: continue until next_page_token is empty; there is no default item or page cap.
• --max-items <n>: stop after collecting N creator content or series items.
• --since-days <1-365>: keep only creator content whose public publish_time is within the last N days. When --pages is omitted, the CLI continues creator content lists until the publish-time boundary is reached.
• --pretty: output formatting only.
• --source-client socialdatax-skills --source-platform clawhub --source-skill socialdatax-xhs-creator-notes: usage attribution for this Agent Skill; keep these values unchanged when running examples from this Skill.

Use either the ID option or the profile URL option for a single command, not both.

The command prints JSON with platform, tool, arguments, and data. Multi-page output keeps merged creator content or series items in data.items and adds page_count, item_count, and next_page_token.

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_user_posted_notes_by_user_id
• xhs_get_user_posted_notes_by_profile_url

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

• xhs_get_user_posted_notes_by_user_id: preferred when user_id is already known.
• xhs_get_user_posted_notes_by_profile_url: use for profile URLs, short links, or profile share text.

Creator note-list pagination uses opaque page_token values. Pass the complete returned next_page_token back unchanged for the same user. Do not modify, truncate, redact, mask, omit, normalize, rebuild, generate, or replace the middle with ellipses.

Output Guidance

Summarize content-list evidence by title or description, summary, publish time, interaction counts, media links, and content type when present. For XHS creator note-list results, copy each returned note_id as the complete 24-character lowercase hexadecimal ID exactly; do not pass or display only a prefix. Use returned content IDs to chain into detail or comment analysis when needed.

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_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.