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