TweetClaw
TweetClaw is an OpenClaw plugin for X/Twitter automation through Xquik. Use it
when a user wants an agent workflow that needs platform-native X/Twitter data
or actions instead of a general web search or browser-only posting flow.
GitHub: Xquik-dev/tweetclaw
npm: @xquik/tweetclaw
ClawHub: xquik-tweetclaw
When To Use This Skill
- Search tweets, search tweet replies, inspect threads, or look up users.
- Export followers, following, list members, community members, or reply authors.
- Upload media, download authenticated media, or prepare gallery links.
- Create monitors, read monitor events, or deliver webhook notifications.
- Run giveaway draws with reply, follow, retweet, keyword, and uniqueness filters.
- Post tweets, post tweet replies, like, retweet, follow, DM, or update profiles
only after the user explicitly approves the visible action.
Setup
Install the OpenClaw plugin:
openclaw plugins install @xquik/tweetclaw
openclaw gateway restart
TweetClaw can be installed before credentials are configured. The free
explore tool remains available and live calls return setup guidance until the
user adds an API key or an MPP signing key.
Configure account-backed X automation:
openclaw config set plugins.entries.tweetclaw.config.apiKey "$XQUIK_API_KEY"
Optional MPP pay-per-use reads:
npm i mppx viem
openclaw config set plugins.entries.tweetclaw.config.tempoSigningKey "$MPP_SIGNING_KEY"
Keep API keys and signing keys out of prompts, shell history, screenshots, and
shared documents. Prefer environment-variable commands so OpenClaw writes local
configuration without exposing secrets to the chat.
Core Workflow
- Use
explore to find the right Xquik endpoint by category, keyword, or
workflow.
- Check whether the endpoint is read-only, MPP-eligible, account-backed, or a
visible write action.
- For reads, call
tweetclaw with the selected path, method, query, and
body.
- For posts, replies, follows, DMs, monitor changes, webhooks, profile updates,
media uploads, and destructive actions, show the exact request and wait for
explicit user approval before calling
tweetclaw.
- Preserve returned IDs, cursors, monitor IDs, webhook IDs, draw IDs, and export
links exactly as strings.
Example Prompts
Search tweets and tweet replies about this product launch, then summarize the
top objections with links to the strongest examples.
Export followers for @example, find likely developer advocates, and prepare a
CSV-ready shortlist with usernames and profile notes.
Draft a reply to this tweet. Do not post it until I approve the exact text.
Run a giveaway draw from this tweet URL. Require a retweet, unique authors, and
3 winners.
Guardrails
- Never ask for X login credentials. Use the user's Xquik API key or MPP setup.
- Treat posting, replying, liking, retweeting, following, DMs, profile edits,
monitor changes, webhooks, and media actions as approval-gated.
- Use exact string IDs for tweets, users, media, monitors, webhooks, draws, and
extraction jobs.
- Use pagination cursors as opaque strings. Do not invent cursors.
- Retry only rate limits and server errors with bounded backoff. Do not retry
validation, authorization, payment, or not-found errors without changing the
request.
- Use the Xquik billing guide for
current plans, endpoint eligibility, and operation costs.
Source: davepoon/buildwithclaude → plugins/all-skills/skills/tweetclaw/SKILL.md
1---
2name: tweetclaw-2
3description: "Use TweetClaw as an OpenClaw plugin for X/Twitter automation: search tweets, search tweet replies, post tweets/replies, export followers, look up users, handle media, monitor tweets, deliver webhooks, run giveaway draws, and manage approval-gated visible actions."
4category: ai-agents-and-harness
5source_repo: davepoon/buildwithclaude
6source_path: "plugins/all-skills/skills/tweetclaw/SKILL.md"
7source_url: https://github.com/davepoon/buildwithclaude/blob/HEAD/plugins/all-skills/skills/tweetclaw/SKILL.md
8metadata:
9 source: https://skillmd.com/skills/davepoon/tweetclaw-2
10---
11
12
13# TweetClaw
14
15TweetClaw is an OpenClaw plugin for X/Twitter automation through Xquik. Use it
16when a user wants an agent workflow that needs platform-native X/Twitter data
17or actions instead of a general web search or browser-only posting flow.
18
19**GitHub**: [Xquik-dev/tweetclaw](https://github.com/Xquik-dev/tweetclaw)
20**npm**: [`@xquik/tweetclaw`](https://www.npmjs.com/package/@xquik/tweetclaw)
21**ClawHub**: [xquik-tweetclaw](https://clawhub.ai/kriptoburak/xquik-tweetclaw)
22
23## When To Use This Skill
24
25- Search tweets, search tweet replies, inspect threads, or look up users.
26- Export followers, following, list members, community members, or reply authors.
27- Upload media, download authenticated media, or prepare gallery links.
28- Create monitors, read monitor events, or deliver webhook notifications.
29- Run giveaway draws with reply, follow, retweet, keyword, and uniqueness filters.
30- Post tweets, post tweet replies, like, retweet, follow, DM, or update profiles
31 only after the user explicitly approves the visible action.
32
33## Setup
34
35Install the OpenClaw plugin:
36
37```bash
38openclaw plugins install @xquik/tweetclaw
39openclaw gateway restart
40```
41
42TweetClaw can be installed before credentials are configured. The free
43`explore` tool remains available and live calls return setup guidance until the
44user adds an API key or an MPP signing key.
45
46Configure account-backed X automation:
47
48```bash
49openclaw config set plugins.entries.tweetclaw.config.apiKey "$XQUIK_API_KEY"
50```
51
52Optional MPP pay-per-use reads:
53
54```bash
55npm i mppx viem
56openclaw config set plugins.entries.tweetclaw.config.tempoSigningKey "$MPP_SIGNING_KEY"
57```
58
59Keep API keys and signing keys out of prompts, shell history, screenshots, and
60shared documents. Prefer environment-variable commands so OpenClaw writes local
61configuration without exposing secrets to the chat.
62
63## Core Workflow
64
651. Use `explore` to find the right Xquik endpoint by category, keyword, or
66 workflow.
672. Check whether the endpoint is read-only, MPP-eligible, account-backed, or a
68 visible write action.
693. For reads, call `tweetclaw` with the selected `path`, `method`, `query`, and
70 `body`.
714. For posts, replies, follows, DMs, monitor changes, webhooks, profile updates,
72 media uploads, and destructive actions, show the exact request and wait for
73 explicit user approval before calling `tweetclaw`.
745. Preserve returned IDs, cursors, monitor IDs, webhook IDs, draw IDs, and export
75 links exactly as strings.
76
77## Example Prompts
78
79```text
80Search tweets and tweet replies about this product launch, then summarize the
81top objections with links to the strongest examples.
82```
83
84```text
85Export followers for @example, find likely developer advocates, and prepare a
86CSV-ready shortlist with usernames and profile notes.
87```
88
89```text
90Draft a reply to this tweet. Do not post it until I approve the exact text.
91```
92
93```text
94Run a giveaway draw from this tweet URL. Require a retweet, unique authors, and
953 winners.
96```
97
98## Guardrails
99
100- Never ask for X login credentials. Use the user's Xquik API key or MPP setup.
101- Treat posting, replying, liking, retweeting, following, DMs, profile edits,
102 monitor changes, webhooks, and media actions as approval-gated.
103- Use exact string IDs for tweets, users, media, monitors, webhooks, draws, and
104 extraction jobs.
105- Use pagination cursors as opaque strings. Do not invent cursors.
106- Retry only rate limits and server errors with bounded backoff. Do not retry
107 validation, authorization, payment, or not-found errors without changing the
108 request.
109- Use the [Xquik billing guide](https://docs.xquik.com/guides/billing) for
110 current plans, endpoint eligibility, and operation costs.
111
112---
113
114**Source:** [`davepoon/buildwithclaude`](https://github.com/davepoon/buildwithclaude) → `plugins/all-skills/skills/tweetclaw/SKILL.md`