Use this Skill when the user wants the Agent to handle X/Twitter workflows through the Xquik or TweetClaw OpenClaw plugin.
When to Use
Use when the user requests the following:
- Scrape tweets, long posts, replies, quotes, mentions, likes, or media
- Search tweets or tweet replies
- Look up users, followers, following lists, or verified followers
- Post tweets, reply to tweets, or upload media after user approval
- Read or send direct messages after account authorization
- Create monitoring, Webhooks, or giveaways
- Determine which TweetClaw or Xquik endpoint is suitable for the current task
Do Not Use
Do not use this Skill for:
- Spam, harassment, deceptive engagement, impersonation, or circumventing platform rules
- Mass unsolicited direct messages, mass following, mass liking, mass retweeting, or engagement farming
- X ads, analytics dashboards, or scheduled publishing features that TweetClaw does not provide
- Performing write operations when only read-only access is configured
- Accessing private or account-level data without explicit authorization
- Asking users to paste API keys, signing secrets, Cookies, or tokens in chat
Instructions
- First classify the user's request into one workflow: read, extract, write, media, direct messages, monitoring, Webhook, giveaway, or capability discovery.
- When installation, configuration, limits, or API details affect the result, check the current documentation first:
- When installing in OpenClaw, prefer an explicit npm selector:
openclaw plugins install npm:@xquik/tweetclaw
- After installation or update, verify the runtime before performing real tasks:
openclaw plugins inspect tweetclaw --runtime --json
openclaw skills info tweetclaw
- Store credentials in the Xquik dashboard, OpenClaw plugin configuration, or an environment-variable-backed secret store. Do not print or echo credential values.
- Use TweetClaw capability discovery or the Xquik documentation to select the minimal viable endpoint and request count.
- Before any visible, state-changing, private-data, paid, recurring, extraction, monitoring, Webhook, giveaway, or account-level operation, explain the goal, account, action, limits, data handling, and obtainable usage impact. Wait for explicit user confirmation.
- Before posting or replying, show the final text and media list. Do not add links, mentions, hashtags, or claims the user did not request.
- When creating monitoring or Webhooks, explain the target, event types, delivery method, and how the user can stop the resource.
- Keep output concise when presenting results, including IDs, URLs, counts, and any partial failures.
Common Workflows
Search Tweets
Use TweetClaw when the user needs the Agent to search X/Twitter content. Keep the query scope clear, set the result count, and summarize the returned tweet IDs, URLs, authors, times, and matching text.
Export Followers
Confirm the account or profile, requested count, and whether the user needs raw rows or a summary. Private account data must be limited to the scope authorized by the user.
Post Tweets
Display the exact tweet text and attached media. Request confirmation before sending. After a successful operation, return the URL of the created tweet.
Monitor updates
Create monitoring only after the user confirms the account, keyword, or event target. Explain what will be monitored and how the results will be delivered.