ClawTrust
7.7
/ 10
1 evaluations
4.8k Downloads
Overview
Post content to X (Twitter) via the official X API using OAuth 1.0a, exposing a CLI (`x-post`) that publishes tweets and returns the tweet URL.
Key Advantages
1.Uses the official X API with OAuth 1.0a, avoiding fragile cookie-based scraping approaches and bot-detection issues that impact tools like bird CLI for posting.
2.Simple CLI interface (`x-post "Your tweet"`) with support for multi-line posts and clear success output (tweet URL).
3.Flexible credential configuration via environment variables or a local JSON secrets file, suitable for both local development and automated workflows.
4.Relies on the maintained `twitter-api-v2` library, reducing the likelihood of low-level protocol or signing errors.
5.Clear operational guidance, including X Developer Portal setup, rate/credit limits, and common error codes (401, 402) with remediation steps.
Use Cases
- Automated posting of announcements, release notes, or changelog updates to an organization’s X account from CI/CD pipelines.
- Broadcasting monitoring or incident notifications to an official X channel (e.g., outage updates, status summaries).
- Scheduled or rule-based social media posts driven by other OpenClaw skills or cron-like automation.
- Cross-posting summaries or highlights generated by LLM workflows to X as public updates.
- Operator-in-the-loop workflows where an LLM drafts tweet text and then calls this skill to publish after human approval.
Evaluation Scores
7.7
/ 10
Reliability
7.3
Functionality
8.8
Usability
7.5
Safety
6.8
Performance
8.0
Compatibility
8.2
Based on 1 evaluation · Latest: 3/19/2026
Download Trend
Loading...
Evaluation History (1)
7.7/103/19/2026▼
OS: linux-x64LLM: google/gemini-3.1-pro-preview
**Judgment:** Solid, focused skill for posting to X via the official API, technically appropriate for production-style posting but with external dependency and safety considerations.
**What it does well**
- Provides a clean, single-purpose CLI (`x-post`) for publishing tweets and returning the resulting URL.
- Uses OAuth 1.0a and the official X API via `twitter-api-v2`, which is more robust and compliant than cookie/session-based tools.
- Configuration options (env vars or `~/.clawdbot/secrets/x-api.json`) fit both local development and automated environments.
- Documentation clearly explains setup, limits (free vs. basic tier), and common error codes with practical fixes.
**Key risks & limitations**
- **External platform dependency:** Functionality and limits depend entirely on X’s Developer Portal tiers, credits, and any future API policy changes. 402 (credits depleted) and 401 (auth/permissions) are expected operational failure modes.
- **Credential management:** API keys and tokens are stored as env vars or in a plain-text JSON file; callers must ensure proper filesystem permissions, secret management, and rotation.
- **Powerful side effects:** Posts are public and irreversible in this flow; misuse (spam, posting from the wrong account, or policy-violating content) is possible if higher-level safeguards are not in place.
- **No built-in content or rate governance:** The skill itself does not enforce rate limiting, account safety checks, or content policies; those must be implemented by the orchestrating system or human operators.
**Recommended scenarios**
- Use when you **need reliable, API-based posting to X** from automations or LLM workflows, and you already manage X Developer credentials securely.
- Appropriate for **CI/CD release announcements, operational status updates, or curated social media posting** where an operator or upstream logic controls what is posted.
- Avoid or tightly permission this skill in contexts where **unreviewed model output could be posted automatically**, or where secret handling and X account risk are not well-managed.
Comments (0)
No comments yet. Be the first!