From x-twitter-scraper
Drafts coherent multi-tweet threads for X (Twitter) from prompts, splitting into 280-char segments with narrative flow. Generates text for review before publishing via post-tweets.
npx claudepluginhub xquik-dev/x-twitter-scraper --plugin x-twitter-scraperThis skill uses the workspace's default tool permissions.
Draft multi-tweet threads on X. This skill produces the thread text; publishing is done through `post-tweets` chaining replies to the previous tweet ID.
Verifies tests pass on completed feature branch, presents options to merge locally, create GitHub PR, keep as-is or discard; executes choice and cleans up worktree.
Guides root cause investigation for bugs, test failures, unexpected behavior, performance issues, and build failures before proposing fixes.
Writes implementation plans from specs for multi-step tasks, mapping files and breaking into TDD bite-sized steps before coding.
Draft multi-tweet threads on X. This skill produces the thread text; publishing is done through post-tweets chaining replies to the previous tweet ID.
| Endpoint | Purpose | Cost |
|---|---|---|
| POST /compose with mode=thread | Draft a full thread | Compose tier |
| POST /drafts | Save a thread draft | Read tier |
Base URL: https://xquik.com/api/v1. Auth: x-api-key: xq_... header.
POST /compose
{
"mode": "thread",
"prompt": "explain why static sites beat SPAs for blogs",
"tone": "casual",
"target_tweet_count": 6
}
-> { thread: [{ text }], total_chars }
Each text is already within the 280-char limit. The response preserves a natural narrative flow (hook, arguments, conclusion).
POST /compose with mode: "thread".post-tweets skill.id.reply_to_tweet_id = previous id.Never publish a thread without user review of every tweet in order. Threads amplify mistakes - one typo becomes 10 tweets.
Single tweets: write-tweets. Publishing: post-tweets. Full API: x-twitter-scraper.