Two capabilities: ① Search TikTok users by keyword (you can first locate the target account's userId); ② Query a user's following list by userId / secUserId; the two can be chained together to complete "search and locate → query following list" in a single conversation.
Usage Guide
① Keyword user search (searchUser)
- What it can do: Search TikTok accounts by nickname / handle, returning userId, follower count, following count, likes received, and work count
- What you need to provide: Nickname or handle keyword; optional filters: follower count range, verified accounts only
- Trigger examples: "Search for the user called Nanxun on TikTok" "Help me find the account solid.guts"
- Output content: User list table (No., nickname, Handle, userId, followers, following, likes received, works) + pagination/chained query guidance
② Following list query (userFollowing)
- What it can do: Query which accounts a TikTok account follows, and output profiles of the followed accounts
- What you need to provide: The account's purely numeric userId or a secUserId starting with
MS4wLjABsecUserId starting with - Trigger examples: "Query the following list of userId 6748953635118187521"
- Output content: Followed accounts table (No., nickname, Handle, followers, works, likes received, region, verification) + pagination prompt
Chained query (new users are recommended to start here)
When you only have a nickname or handle and no userId, follow this process to close the loop in a single conversation:
- Directly say "Query solid.guts's following list" → the skill first searches and locates the account, and lists candidates (including userId and follower count)
- You confirm the target (if there is a unique exact match, you can confirm directly) → the skill queries its following list and outputs it
Prerequisites
You need to configure the environment variable REDFOX_API_KEY(go to Honghu hub to register and obtain it, format ak_xxxxxxxx). Each successful query may consume credits; by default only one page is queried; to paginate, you need to explicitly instruct "next page"; when a query returns no results, do not switch to querying other targets.
Trigger scenarios
Use this Skill when the user raises the following needs:
Following list query (userFollowing)
- "Check who this TikTok user follows"
- "TikTok following list"
- "Query an account's following list"
- "Analyze the following targets of a TikTok account"
Keyword user search (searchUser)
- "Search for the user called xxx on TikTok"
- "Help me find the ID of the account solid.guts"
- "What accounts on TikTok do xxx"
Chained query: When the user only provides a nickname/handle and wants to check the following list, first search and locate the target (to obtain the userId), then after confirmation query its following list.
Note: The following list API only accepts userId(pure digits) or secUserId(starting with MS4wLjAB), and does not accept @handle nicknames; when the user only provides a handle, first use keyword search to locate it, and if the search results have no match, do not switch to other keywords.
Data Description
Output Content
Following list (userFollowing)
- Following list: Output as a Markdown table, including No., nickname, Handle, followers, works, likes, region, verification
- Private marker：
isSecret=1For followed accounts with this, append "(Private)" after the nickname - Fixed reminder: Include an API Key acquisition reminder in the output
User search (searchUser)
- User list: Output as a Markdown table, including No., nickname, Handle, userId, followers, following, likes, works
- The userId column is always output: for direct use in chained queries of the following list
- Filtering: Supports follower count ranges (01K / 1K10K / 10K~100K / above 100K) and verified accounts only
Sorting and Criteria
- By default, the following list is output in the API's original order (i.e., follow time from most recent to earliest); when the user specifies, it can be sorted locally in descending order by follower count, work count, or likes
- User search is output in descending order by follower count by default;
--sort noneretain the API's original relevance order - Only display fields returned by the API; do not construct output for fields not returned by the API (such as homepage URL), and do not fabricate detail information such as avatars or videos
One-click Installation
Prerequisites
- Python 3.8+ (uses only the standard library, no additional dependencies required)
- Red Fox Data API Key (go to Red Fox hub to register and obtain)
Installation Steps
- Place the skill folder into your Skills directory
- Configure the environment variable
REDFOX_API_KEY(for configuration details, seereferences/core_workflow.md） - No additional dependencies need to be installed; use it directly
Workflow
The core execution flow (intent recognition, script invocation, pagination rules, table rendering, empty results and error handling, etc.) is detailed in
references/core_workflow.md. The Agent must follow all rules in that file during execution. For complete field descriptions, seereferences/api-spec.md。
Usage Guide
Describe query requirements directly in natural language; no need to memorize commands.
| Intent | Example phrasing | Effect |
|---|---|---|
| Check following list | "Check the following list of userId 6748953635118187521" | Output the list of followed accounts (in reverse follow-time order) |
| Search users | "Search for users on TikTok named Nanxun" | Output the user list (default sorted by follower count descending, including userId) |
| Filtered search | "Search xxx, only show accounts with over 100K followers" | Filter users by follower range |
| Specify sorting | "Sort by follower count to see which big accounts he follows" | Change to output sorted by follower count descending |
| Specify count | "Only show the first 10 followed accounts" | Only show the first 10 entries |
| Chained query | "Query solid.guts' following list" | First search to locate the userId, then query the following list after confirmation |
| Continue paging | "Next page" | For the following list, use the returned minTime / pageToken to continue the query; for user search, use the returned cursor to continue the query |
Notes
- Data authenticity: All values come from the data service's responses and are displayed truthfully; estimating or fabricating is strictly prohibited; fields not returned by the API (such as homepage URL) must not be constructed in the output
- No substitutions when queries return nothing: When any capability returns an empty list, output only "No data available" and possible reasons (such as following count being 0, incorrect ID, private account, or no matching keywords); do not proactively query other users or keywords
- Credit protection: Each successful query may consume credits; by default, query only one page and do not proactively paginate without the user's explicit request; chained queries (search → following list) involve two separate calls, and search results must first be confirmed with the user before querying the following list
- Authentication: First-time use requires configuring the environment variable
REDFOX_API_KEY; for API Key acquisition and configuration, seereferences/core_workflow.md