tikhub-onboarding
Skill7 starsChanged 5 months agoMITView on GitHub
Entry point for using TikHub social-media data in Claude. Use when the user first mentions TikHub, asks to download/fetch TikTok/Douyin/Instagram/YouTube/Twitter/Xiaohongshu data, or hasn't set up access yet. Walks through getting an API key, setting TIKHUB_API_KEY, choosing a path (hosted MCP / REST / Python SDK), and routes to the right skill.
- Reads credentials
In this repository18 other files it gives its agents.
- bulk-data-exportSkill
- comments-analysisSkill
- competitor-analysisSkill
- creator-analyticsSkill
- douyinSkill
- hashtag-researchSkill
- instagramSkill
- social-listeningSkill
- social-media-downloaderSkill
- tikhub-endpoint-discoverySkill
- tikhub-mcpSkill
- tikhub-python-sdkSkill
- tikhub-rest-apiSkill
- tiktokSkill
- trend-researchSkill
- twitter-threadsSkill
- xiaohongshuSkill
- youtubeSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Read this once, get the user set up, then hand off to the skill that owns the task.
- Very specific: line 21
Every path reads TIKHUB_API_KEY from the environment:
- Distinctive: line 47
If unset, halt and walk the user through Steps 1–2 before proceeding.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
TikHub — Onboarding & Routing
TikHub is a unified API for social-media data across 16+ platforms (TikTok, Douyin, Instagram, YouTube, Twitter/X, Threads, Xiaohongshu, Weibo, Bilibili, Reddit, LinkedIn, and more): download media, fetch posts/profiles/comments, search, trends, and analytics.
Read this once, get the user set up, then hand off to the skill that owns the task.
Step 1 — Get an API key (one time)
Send the user to https://user.tikhub.io: register (email verification), open the API Keys page, and create a key. Pricing is per-endpoint, credit-based.
Step 2 — Set the key in the environment
Every path reads TIKHUB_API_KEY from the environment:
export TIKHUB_API_KEY="your_api_key_here"
# persist it: add the line to ~/.zshrc or ~/.bashrcStep 3 — Pick a path and hand off
| If the user wants… | Path | Hand off to |
| Claude to call TikHub directly as tools (default) | Hosted MCP | tikhub-mcp |
| To script/curl it, CI, or no Python/Node | REST API | tikhub-rest-api |
| To build an app or pipeline in Python | Python SDK | tikhub-python-sdk |
| To find which endpoint does X (1,100+ exist) | Discovery | tikhub-endpoint-discovery |
| A finished outcome (download, analyze a creator, trends, listening…) | Task skill | social-media-downloader, creator-analytics, trend-research, social-listening, competitor-analysis, hashtag-research, comments-analysis, bulk-data-export |
| Deep work on one platform | Platform skill | tiktok, douyin, instagram, youtube, twitter-threads, xiaohongshu |
Setup gate (run before any TikHub call)
if [ -z "${TIKHUB_API_KEY:-}" ]; then
echo "TIKHUB_API_KEY is not set — get a key at https://user.tikhub.io then: export TIKHUB_API_KEY=..."
fiIf unset, halt and walk the user through Steps 1–2 before proceeding.
Red flags
- Calling endpoints before
TIKHUB_API_KEYis set (every call 401s). - Forgetting that calls cost credits — warn before large/bulk pulls.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

