TweetClaw OpenClaw X Automation Skill

Safety notes

TweetClaw can perform public X account actions after OpenClaw tool opt-in and approval; review exact posts, replies, DMs, follows, media, monitors, webhooks, and draws before allowing a call.
Keep `tweetclaw` as an optional OpenClaw tool and start with read-only `explore` until the user confirms the workflow.
Do not use TweetClaw for spam, deceptive engagement, harassment, credential collection, impersonation, or bulk unsolicited outreach.

Privacy notes

Xquik API keys and MPP signing keys must stay in OpenClaw plugin config or environment variables, never in prompts, shared logs, PRs, or committed files.
Tweet searches, timelines, DMs, bookmarks, follower exports, media metadata, monitors, webhook details, and account usage can expose private or account-scoped data.
Use the Xquik dashboard and public docs for current billing, account, and data-handling details.

Prerequisites

OpenClaw 2026.6.1 or newer for the current plugin metadata
Xquik account and API key before using account-backed reads, writes, monitors, webhooks, media, or extraction workflows
Agent client with Agent Skills support for `npx skills add`
Explicit user approval before any visible, private, paid, recurring, or account-changing action

Schema details

Install type: package
Reading time: 5 min
Difficulty score: 68
Troubleshooting: Yes
Breaking changes: No

Source repository stats

Scope: Source repo

Package metadata

Download URL: https://github.com/Xquik-dev/tweetclaw/archive/refs/heads/master.zip

Skill and platform metadata

Skill type: general
Skill level: advanced
Verification: validated
Verified at: 2026-06-09

Retrieval sources

https://github.com/Xquik-dev/tweetclawhttps://raw.githubusercontent.com/Xquik-dev/tweetclaw/master/skills/tweetclaw/SKILL.mdhttps://registry.npmjs.org/%40xquik%2Ftweetclaw/latest

Tested platforms

OpenClawClaudeCodexCursor

Platform	Support	Install path
claude-code	Native	.claude/skills/<skill-name>/SKILL.md
codex	Native	.agents/skills/<skill-name>/SKILL.md
windsurf	Native	.windsurf/skills/<skill-name>/SKILL.md
gemini	Native	.gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md
cursor	Adapter	.cursor/rules/<skill-name>.mdc
cli	Manual	AGENTS.md or tool-specific context file

Full copyable content

# Trigger
"Use the TweetClaw skill to set up a safe X/Twitter automation workflow."

# Skill install
npx skills add xquik-dev/tweetclaw

# OpenClaw plugin install
openclaw plugins install npm:@xquik/tweetclaw

About this resource

Overview

TweetClaw is the Agent Skill bundled with the @xquik/tweetclaw OpenClaw plugin. It gives agents a safety-first operating guide for X/Twitter workflows through Xquik: tweet search, reply search, user lookup, follower export, media upload and download, direct messages, monitors, webhooks, giveaway draws, and approval-gated posting.

Use the skill when an agent needs to install TweetClaw, decide which credential mode to use, verify OpenClaw runtime registration, or prepare a workflow that may touch public accounts, private account data, recurring monitors, or paid API calls.

Install

Install the reusable Agent Skill:

npx skills add xquik-dev/tweetclaw

Install the OpenClaw plugin runtime from npm:

openclaw plugins install npm:@xquik/tweetclaw

Verify the runtime before live work:

openclaw plugins inspect tweetclaw --runtime --json
openclaw skills info tweetclaw

The runtime should show the read-only explore catalog tool, optional tweetclaw API tool, approval hook, and bundled status/trends command.

Workflow Scope

Use explore first to inspect available Xquik endpoints without credentials.
Configure an Xquik API key for account-backed reads, writes, media, monitors, webhooks, and extraction workflows.
Configure MPP signing only for read-only pay-per-use workflows.
Add explore and tweetclaw to OpenClaw tool allow settings only when the user wants agent-driven X/Twitter workflows.
Review exact payloads before posts, replies, DMs, follows, profile changes, media uploads, webhooks, monitors, draws, or extraction jobs.

Safety Checklist

Confirm the user owns or is authorized to access the X account.
Keep API keys and signing keys out of chat, logs, screenshots, issues, and commits.
Start with read-only lookup before allowing writes or recurring workflows.
Show final text and media before publishing.
Re-confirm when scope, target account, limits, or recurring behavior changes.