TikHubTikHub/tikhub-plugin/skills/twitter-threads/SKILL.md

twitter-threads

Skill7 starsChanged 5 months agoMITView on GitHub

Work with Twitter/X and Threads data via TikHub — fetch tweet/post detail, user profiles, user timelines, followers/following, search timelines, comments/replies, and X trending topics. Use when the task targets Twitter/X or Threads. Covers the Twitter-Web and Threads-Web APIs.

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-onboardingSkill
- tikhub-python-sdkSkill
- tikhub-rest-apiSkill
- tiktokSkill
- trend-researchSkill
- xiaohongshuSkill
- youtubeSkill

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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

Very specific:
Don't mix the two cursor params — cursor (Twitter) vs end_cursor (Threads).
line 66

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Twitter / X & Threads (via TikHub)

Coverage of Twitter/X and Threads (both microblog platforms). Exhaustive endpoints: tikhub-find-endpoint "<goal>" --platform twitter or --platform threads.

Setup gate

[ -z "${TIKHUB_API_KEY:-}" ] && echo "Set TIKHUB_API_KEY first (see tikhub-onboarding)."

Coverage: Twitter-Web, Threads-Web.

Twitter / X endpoints

Goal	Method + path	Key params
Tweet detail	`GET /api/v1/twitter/web/fetch_tweet_detail`	`tweet_id`
User profile	`GET /api/v1/twitter/web/fetch_user_profile`	`screen_name` \| `rest_id`
User tweets	`GET /api/v1/twitter/web/fetch_user_post_tweet`	`screen_name`, `cursor`
Search timeline	`GET /api/v1/twitter/web/fetch_search_timeline`	`keyword`, `search_type`, `cursor`
Tweet comments	`GET /api/v1/twitter/web/fetch_post_comments`	`tweet_id`, `cursor`
Trending	`GET /api/v1/twitter/web/fetch_trending`	`country`
Followers	`GET /api/v1/twitter/web/fetch_user_followers`	`screen_name`, `cursor`
Following	`GET /api/v1/twitter/web/fetch_user_followings`	`screen_name`, `cursor`

Threads endpoints

Goal	Method + path	Key params
User info	`GET /api/v1/threads/web/fetch_user_info`	`username`
User posts	`GET /api/v1/threads/web/fetch_user_posts`	`user_id`, `end_cursor`
Search (top)	`GET /api/v1/threads/web/search_top`	`query`, `end_cursor`
Search (recent)	`GET /api/v1/threads/web/search_recent`	`query`, `end_cursor`
Post comments	`GET /api/v1/threads/web/fetch_post_comments`	`post_id`, `end_cursor`

Example

curl -s "https://api.tikhub.io/api/v1/twitter/web/fetch_search_timeline?keyword=ai&search_type=Top" \
  -H "Authorization: Bearer $TIKHUB_API_KEY"

Pagination

Twitter/X uses cursor; Threads uses end_cursor. Pass the value returned by the previous response; stop when none is returned. Each page is billed — cap it.

Hand off to task skills

Analyze an account → creator-analytics
Trending/search → trend-research, social-listening
Comment/reply mining → comments-analysis
Competitor benchmarking → competitor-analysis
Large pulls → bulk-data-export

Red flags

Twitter user endpoints accept screen_name or rest_id; Threads user posts need the numeric user_id (resolve via fetch_user_info first).
Don't mix the two cursor params — cursor (Twitter) vs end_cursor (Threads).

Download now (ZIP)

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

What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free