git:20260820.52018fd to git:20260901.a860d43

---

name: "media-user-info"

description: "Retrieve social media creator profile information from platform-supported user IDs, usernames, channel URLs, profile URLs, short links, or share text. Supported input forms vary by platform. This version is backed by hosted platform MCP services and supports Xiaohongshu / XHS / RedNote, Douyin, Kuaishou, Bilibili, Zhihu, Instagram, X / Twitter, YouTube, TikTok, Weibo, and WeChat Channels creators."

source_client: "socialdatax-skills"

source_platform: "github"

source_skill: "media-user-info"

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=github"

---

<!-- AUTO-GENERATED from socialdatax-skill-source. Do not edit directly; run `node scripts/generate_socialdatax_skills.mjs`. -->

# Media User Info

Use this skill when the user wants creator profile data, account basics, creator positioning, audience scale, or profile lookup for supported social media platforms.

Current platform support:

- Xiaohongshu / XHS / RedNote creators through the `xhs_get_user_info_by_*` tools.

- Douyin / 抖音 creators through the `douyin_get_user_info_by_*` tools.

- Kuaishou / 快手 creators through the `kuaishou_get_user_info_by_*` tools.

- Kuaishou / 快手 creator discovery through `kuaishou_search_users` before profile lookup when only an account keyword or niche is known.

- Bilibili / 哔哩哔哩 / B站 creators through the `bilibili_get_user_info_by_*` tools.

- Zhihu / 知乎 creators through `zhihu_get_user_info_by_profile_url`.

- Instagram creators through the `instagram_get_user_info_by_*` tools.

- X / Twitter creators through the `x_get_user_info_by_*` tools.

- YouTube channels through `youtube_get_channel_info_by_url`.

- TikTok creators through the `tiktok_get_user_info_by_*` tools.

- Weibo / 微博 creators through the `weibo_get_user_info_by_*` tools.

- WeChat Channels / 视频号 creators through `wechat_get_user_info_by_url` for video or image-post links or share text, or `wechat_get_user_info_by_user_id` when a `v2_...@finder` user_id is already known.

## API Key

Use `SOCIALDATAX_API_KEY` for SocialDataX requests. The only official website for requesting or managing API access is <https://socialdatax.com/ai?from=github>. 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=github>，按官网的 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:

```bash

npx -y socialdatax-skills@latest xhs user-info \

--user-id "<user_id>" --pretty --source-client socialdatax-skills \

--source-platform github --source-skill media-user-info

npx -y socialdatax-skills@latest xhs user-info \

--profile-url "<profile_url_or_share_text>" --pretty \

--source-client socialdatax-skills --source-platform github \

--source-skill media-user-info

npx -y socialdatax-skills@latest douyin user-info \

--sec-user-id "<sec_user_id>" --pretty --source-client socialdatax-skills \

--source-platform github --source-skill media-user-info

npx -y socialdatax-skills@latest douyin user-info \

--profile-url "<profile_url_or_share_text>" --pretty \

--source-client socialdatax-skills --source-platform github \

--source-skill media-user-info

npx -y socialdatax-skills@latest kuaishou user-search \

--keyword "<creator_keyword>" --pretty --source-client socialdatax-skills \

--source-platform github --source-skill media-user-info

npx -y socialdatax-skills@latest kuaishou user-info \

--user-id "<user_id>" --pretty --source-client socialdatax-skills \

--source-platform github --source-skill media-user-info

npx -y socialdatax-skills@latest kuaishou user-info \

--profile-url "<profile_url_or_share_text>" --pretty \

--source-client socialdatax-skills --source-platform github \

--source-skill media-user-info

npx -y socialdatax-skills@latest bilibili user-info \

--user-id "<user_id>" --pretty --source-client socialdatax-skills \

--source-platform github --source-skill media-user-info

npx -y socialdatax-skills@latest bilibili user-info \

--profile-url "<profile_url_or_share_text>" --pretty \

--source-client socialdatax-skills --source-platform github \

--source-skill media-user-info

npx -y socialdatax-skills@latest zhihu user-info \

--profile-url "<profile_url_or_share_text>" --pretty \

--source-client socialdatax-skills --source-platform github \

--source-skill media-user-info

npx -y socialdatax-skills@latest instagram user-info \

--username "<username>" --pretty --source-client socialdatax-skills \

--source-platform github --source-skill media-user-info

npx -y socialdatax-skills@latest instagram user-info \

--profile-url "<profile_url_or_share_text>" --pretty \

--source-client socialdatax-skills --source-platform github \

--source-skill media-user-info

npx -y socialdatax-skills@latest x user-info \

--user-id "<user_id>" --pretty --source-client socialdatax-skills \

--source-platform github --source-skill media-user-info

npx -y socialdatax-skills@latest x user-info \

--username "<username>" --pretty --source-client socialdatax-skills \

--source-platform github --source-skill media-user-info

npx -y socialdatax-skills@latest x user-info \

--profile-url "<profile_url_or_share_text>" --pretty \

--source-client socialdatax-skills --source-platform github \

--source-skill media-user-info

npx -y socialdatax-skills@latest youtube channel-info \

--channel-url "<youtube_channel_url>" --pretty --source-client socialdatax-skills \

--source-platform github --source-skill media-user-info

npx -y socialdatax-skills@latest tiktok user-info \

--tiktok-id "<tiktok_id>" --pretty --source-client socialdatax-skills \

--source-platform github --source-skill media-user-info

npx -y socialdatax-skills@latest tiktok user-info \

--profile-url "<profile_url_or_share_text>" --pretty \

--source-client socialdatax-skills --source-platform github \

--source-skill media-user-info

npx -y socialdatax-skills@latest weibo user-info \

--user-id "<user_id>" --pretty --source-client socialdatax-skills \

--source-platform github --source-skill media-user-info

npx -y socialdatax-skills@latest weibo user-info \

--profile-url "<profile_url>" --pretty --source-client socialdatax-skills \

--source-platform github --source-skill media-user-info

npx -y socialdatax-skills@latest wechat user-info \

--user-id "<v2_finder_user_id>" --pretty --source-client socialdatax-skills \

--source-platform github --source-skill media-user-info

```

Optional arguments:

- XHS `--user-id <user_id>`: preferred when the creator ID is already known from another result.

- XHS `--profile-url <profile_url_or_share_text>`: use for a profile URL, short link, or profile share text.

- Douyin `--sec-user-id <sec_user_id>`: preferred when the creator sec_user_id is already known.

- Douyin `--profile-url <profile_url_or_share_text>`: use for a profile URL, short link, or profile share text.

- `--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 returned `next_page_token` from 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-days` because 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.

- Bilibili `--user-id <user_id>`: preferred when the creator user_id is already known.

- Bilibili `--profile-url <profile_url_or_share_text>`: use for a profile URL, short link, or profile share text.

- Zhihu `--profile-url <profile_url_or_share_text>`: use for a Zhihu profile URL.

- Instagram `--username <username>` or `--profile-url <profile_url_or_share_text>`: use exactly one creator profile entrypoint.

- X / Twitter `--user-id <user_id>`, `--username <username>`, or `--profile-url <profile_url_or_share_text>`: use exactly one creator profile entrypoint.

- YouTube `--channel-url <youtube_channel_url>`: use for a YouTube channel profile URL.

- TikTok `--tiktok-id <tiktok_id>` or `--profile-url <profile_url_or_share_text>`: use exactly one creator profile entrypoint.

- Weibo `--user-id <user_id>`: preferred when the creator user_id is already known.

- Weibo `--profile-url <profile_url>`: use for a Weibo user profile URL.

- WeChat Channels / 视频号 `--user-id <v2_finder_user_id>`: use when the creator `v2_...@finder` user_id is already known.

- `--source-client socialdatax-skills --source-platform github --source-skill media-user-info`: usage attribution for this Agent Skill; keep these values unchanged when running examples from this Skill.

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

## 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: `xhs_get_user_info_by_user_id`, `xhs_get_user_info_by_profile_url`

- DOUYIN: `douyin_get_user_info_by_sec_user_id`, `douyin_get_user_info_by_profile_url`

- KUAISHOU: `kuaishou_search_users`, `kuaishou_get_user_info_by_user_id`, `kuaishou_get_user_info_by_profile_url`

- BILIBILI: `bilibili_get_user_info_by_user_id`, `bilibili_get_user_info_by_profile_url`

- ZHIHU: `zhihu_get_user_info_by_profile_url`

- INSTAGRAM: `instagram_get_user_info_by_username`, `instagram_get_user_info_by_profile_url`

- X: `x_get_user_info_by_user_id`, `x_get_user_info_by_username`, `x_get_user_info_by_profile_url`

- YOUTUBE: `youtube_get_channel_info_by_url`

- TIKTOK: `tiktok_get_user_info_by_tiktok_id`, `tiktok_get_user_info_by_profile_url`

- WEIBO: `weibo_get_user_info_by_user_id`, `weibo_get_user_info_by_profile_url`

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

- `xhs_get_user_info_by_user_id`: preferred when `user_id` is already known from search, detail, comments, or creator note lists.

- `xhs_get_user_info_by_profile_url`: use for profile URLs, short links, or profile share text.

- `douyin_get_user_info_by_douyin_id`: use when the user provides the public Douyin account ID / 抖音号, not a nickname, search keyword, sec_user_id, or profile URL.

- `douyin_get_user_info_by_sec_user_id`: preferred when `sec_user_id` is already known from search, detail, comments, or creator work lists.

- `douyin_get_user_info_by_profile_url`: use for profile URLs, short links, or profile share text.

- `kuaishou_search_users`: use when the user only has a creator keyword and needs possible Kuaishou user_id candidates. Pass `keyword`; pass `page_token` only for continuation. Do not pass `page`.

- `kuaishou_get_user_info_by_user_id`: preferred when a non-empty `user_id` is already known from search, detail, comments, or creator work lists.

- `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-empty `user_id`.

- `bilibili_get_user_info_by_user_id`: preferred when a Bilibili user_id is already known.

- `bilibili_get_user_info_by_profile_url`: use for Bilibili profile URLs, short links, or profile share text.

- `zhihu_get_user_info_by_profile_url`: use for Zhihu profile URLs.

- `instagram_get_user_info_by_username`: use when the Instagram username is known.

- `instagram_get_user_info_by_profile_url`: use for Instagram profile URLs.

- `x_get_user_info_by_user_id`: use when the X user_id is known.

- `x_get_user_info_by_username`: use when the X username is known.

- `x_get_user_info_by_profile_url`: use for X profile URLs.

- `youtube_get_channel_info_by_url`: use for YouTube channel URLs.

- `tiktok_get_user_info_by_tiktok_id`: use when the TikTok tiktok_id is known.

- `tiktok_get_user_info_by_profile_url`: use for TikTok profile URLs.

- `weibo_get_user_info_by_user_id`: preferred when `user_id` is already known.

- `weibo_get_user_info_by_profile_url`: use for Weibo user profile URLs.

- `wechat_get_user_info_by_user_id`: use when the WeChat Channels / 视频号 creator `v2_...@finder` user_id is already known.

- `wechat_get_user_info_by_url`: use for a WeChat Channels / 视频号 video or image-post link or share text to resolve the creator profile.

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

For YouTube, report channel profile facts separately from video-list evidence.

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