x-integration

Automate X posting and engagement via Playwright browser automation.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/theowenyoung/nanoclaw --skill x-integration-theowenyoung
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: x-integration
Source: https://github.com/theowenyoung/nanoclaw/tree/main/.claude/skills/x-integration
Command: npx skills add https://github.com/theowenyoung/nanoclaw --skill x-integration-theowenyoung

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, and includes scripts (resource) components.

What problem does it solve?

Enables NanoClaw agents to interact with X (Twitter) without using the paid API by automating a real browser session on the host; this solves the need to programmatically post, like, reply, retweet, and quote while preserving OS-level isolation between agents and the host.

Core Features & Use Cases

  • Post Tweets: Publish text tweets from container agents via host browser automation with a persistent Chrome profile.
  • Engage: Like, reply, retweet, and quote tweets using Playwright-driven interactions.
  • Operational Flow: Container-side MCP tools write IPC task files, the host runs Playwright scripts using the user's Chrome profile, and results are written back via IPC.
  • Use Case: Use during setup, testing, or troubleshooting social posting workflows where API access is restricted or costly.

Quick Start

Ask the assistant to post a tweet by saying: @Assistant post a tweet: Hello world!

Frequently Asked Questions about x-integration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate posting tweets without using the paid X API?

Automate posting tweets without the paid X API by using Playwright browser automation with a persistent host Chrome profile. This approach drives a real browser session to publish text, preserving OS-level isolation between container agents and the host system.

Can I use Playwright to like, reply, and retweet on X?

Yes, you can use Playwright to like, reply, retweet, and quote tweets on X. The automation interacts directly with the web interface using your existing Chrome profile to execute these engagement actions programmatically.

How does file-based IPC work for browser automation tasks?

File-based IPC works by having container-side MCP tools write task files to a shared location, which the host Playwright scripts read and execute. Results are then written back via IPC files, ensuring secure task exchange and OS-level isolation between agents.

Do I need a persistent Chrome profile to automate Twitter interactions?

Yes, a persistent Chrome profile is required to maintain authentication state for Twitter automation. The Playwright scripts run on the host using this profile, avoiding repeated logins and preserving persistent auth files for continuous session management.

What are the limitations of using browser automation for X interactions?

Limitations of browser automation for X include dependency on host Chrome profile availability and potential interface changes breaking selectors. It enforces configurable timeouts and main-group permissions, making it best suited for setup, testing, or troubleshooting rather than high-volume production.

What's the best way to test social posting workflows when API access is restricted?

The best way to test social posting workflows with restricted API access is using Playwright-driven browser automation. It bypasses API costs by automating a real browser session on the host, enabling tweet publishing and engagement for testing or troubleshooting.