メニュー
Use Xquik for authorized X/Twitter data workflows, including tweet search, profile reads, follower exports, media lookup, monitoring, webhooks, REST API calls, SDK usage, and MCP setup.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/seaworld008/Commonly-used-high-value-skills --skill x-twitter-scraperコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SOC 職業分類に基づく
SKILL.md を表示中
| name | x-twitter-scraper |
| description | Use Xquik for authorized X/Twitter data workflows, including tweet search, profile reads, follower exports, media lookup, monitoring, webhooks, REST API calls, SDK usage, and MCP setup. |
| zh_description | 用于抓取和分析 X/Twitter 公开内容、线程和增长信号。 |
| version | 1.0.0 |
| author | Xquik-dev |
| source | github:Xquik-dev/x-twitter-scraper |
| source_url | https://github.com/Xquik-dev/x-twitter-scraper |
| license | MIT |
| tags | ["growth", "social-media", "twitter", "x", "api", "mcp"] |
| created_at | 2026-06-22 |
| updated_at | 2026-06-22 |
| quality | 4 |
| complexity | intermediate |
Use this skill when a user needs structured, authorized X/Twitter data through Xquik.
Use Xquik search when the user needs structured post results for a topic, account, URL, keyword, or monitoring seed. Ask for the query, time window, result limit, and output format before making calls.
Return a concise table or JSON summary with:
Use profile and network endpoints when the user asks for account-level context. Keep the output task-focused. For example, summarize profile tweets for campaign research, export followers for an authorized audit, or collect replies for support triage.
Do not infer identity, intent, or private attributes from public profile data. Report only what the returned fields support.
Use media and export workflows when the user asks for durable artifacts. Confirm whether the output should be CSV, JSON, Markdown, or a downstream dataset. Preserve original URLs and IDs so later steps can verify provenance.
Use monitoring only when the user asks for repeat checks or downstream automation. Define:
Keep webhook payload handling idempotent. Log source IDs, not secrets.
Only prepare publishing actions when the user explicitly requests them and the target account is authorized. Keep the agent confirmation step separate from draft generation. Never silently publish, like, repost, reply, follow, or unfollow.
Use the public API reference for the exact route, method, and fields. Keep examples generic and avoid hard-coding secrets.
curl "https://xquik.com/api/v1/account" \
-H "x-api-key: ${XQUIK_API_KEY}"
For any multi-step X/Twitter workflow, produce this plan before running calls:
Before treating a workflow as working, verify at least one documented public Xquik route or MCP setup step from the docs. For repository changes, check links to the docs and source repository, then scan the diff for secrets or unsupported claims.