← Back to Skills Marketplace
Twitter Browser Automation
by
bulldozzer
· GitHub ↗
· v1.0.0
· MIT-0
106
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install twitter-browser-automation
Description
Interact with Twitter/X through Chrome browser via browser-relay MCP. Post tweets, search trends and hashtags, analyze engagement metrics, create threads, an...
Usage Guidance
This skill appears to do what it says (browser-driven Twitter automation) but it controls a logged-in Chrome session through an external MCP — a powerful capability. Before installing: 1) Verify and audit the browser-relay package (@anthropic-ai/browser-relay) you will run via npx (review the package source, maintainer, and network behavior). 2) Use a dedicated Chrome profile for automation (not your primary account) to limit exposure of cookies and other sessions. 3) Consider disabling autonomous invocation (set disable-model-invocation) if you don't want the agent to act without manual approval. 4) Confirm that the skill/platform enforces the claimed explicit-confirmation step before any publish action. 5) Manually inspect the SKILL.md/README for any lines that look like covert prompts or instructions that would cause the agent to ignore prior safeguards. If you need lower risk, prefer an API-key-based integration or a read-only analysis mode rather than live control of your logged-in browser.
Capability Analysis
Type: OpenClaw Skill
Name: twitter-browser-automation
Version: 1.0.0
The twitter-browser-automation skill provides a comprehensive and security-conscious framework for an AI agent to interact with Twitter/X via a browser-relay MCP. It includes robust defenses against prompt injection by explicitly instructing the agent to treat all platform data as untrusted, and it implements 'anti-ban' strategies (rate limiting, jitter, and session caps) to protect the user's account. The logic is entirely consistent with its stated purpose, lacks any indicators of data exfiltration or credential theft, and requires explicit user confirmation before performing impactful actions like posting.
Capability Assessment
Purpose & Capability
The name/description match the instructions: it automates Twitter/X via a browser-relay MCP (no API keys). Requiring a logged-in Chrome session and browser-relay is appropriate for this purpose. The README's guidance to run @anthropic-ai/browser-relay via npx is consistent with the stated architecture.
Instruction Scope
SKILL.md instructs the agent to navigate pages, click, type, and read content on x.com — which is expected. It explicitly says it will treat page content as untrusted and require confirmation before posting. Caution: a browser-relay agent controlling a logged-in Chrome profile can potentially access any data visible in that browser (other tabs, cookies, saved sessions). Confirm the skill enforces the stated explicit-confirmation behavior and that the agent will not be allowed to act on unrelated pages or credentials.
Install Mechanism
The skill is instruction-only (no install spec), which lowers risk. However README recommends configuring browser-relay via npx @anthropic-ai/browser-relay — this pulls code from npm at runtime. That is a reasonable distribution method but you should verify the package source and trustworthiness of the MCP implementation before running it.
Credentials
No environment variables, credentials, or config paths are requested by the skill itself — appropriate for a browser-driven integration that relies on the user's logged-in Chrome session rather than API keys.
Persistence & Privilege
always:false (good) and user-invocable:true. However, disable-model-invocation is false (default), so the agent may invoke this skill autonomously. Combined with the ability to control a logged-in Chrome session, that raises the blast radius: an autonomous agent could potentially read or act on the user's active browser session. The SKILL.md states it requires explicit confirmation before posting, but you should verify that the platform enforces that confirmation and consider disabling autonomous invocation if you want to avoid automated posts.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install twitter-browser-automation - After installation, invoke the skill by name or use
/twitter-browser-automation - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial browser-based Twitter/X automation skill release with human-like posting and engagement controls.
- Interacts with Twitter/X directly via Chrome browser (no API keys needed), using browser-relay MCP.
- Supports tweeting, creating threads, replying, searching hashtags/trends, and engagement checks with built-in anti-ban actions.
- Enforces strict guidelines for human-like tweet tone, character limits, hashtag usage, and newline handling.
- Prompts user at session start to select “X Free” or “X Premium” mode for accurate platform constraint handling.
- Prevents common errors such as improper newlines or AI-sounding phrasing; includes detailed rewrite guidance and context-based tone rules.
Metadata
Frequently Asked Questions
What is Twitter Browser Automation?
Interact with Twitter/X through Chrome browser via browser-relay MCP. Post tweets, search trends and hashtags, analyze engagement metrics, create threads, an... It is an AI Agent Skill for Claude Code / OpenClaw, with 106 downloads so far.
How do I install Twitter Browser Automation?
Run "/install twitter-browser-automation" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Twitter Browser Automation free?
Yes, Twitter Browser Automation is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Twitter Browser Automation support?
Twitter Browser Automation is cross-platform and runs anywhere OpenClaw / Claude Code is available (macos, linux).
Who created Twitter Browser Automation?
It is built and maintained by bulldozzer (@andreasozzo); the current version is v1.0.0.
More Skills