x-integration

Automates posting, liking, replying, retweeting, and quoting on X via Playwright browser automation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, dotenv-cli, tsx, zod, @anthropic-ai/claude-agent-sdk, pino, and includes scripts (resource) components.

What problem does it solve?

It solves the problem of safely automating routine X (Twitter) actions without using blocked headless bot patterns or requiring a paid official posting API.

Core Features & Use Cases

  • Tweet posting: Publish new tweets from assistant-initiated requests.
  • Engagement actions: Like, reply, retweet, and quote tweets using real browser automation.
  • One-time manual authorization: Uses a persistent Chrome profile and stores an authenticated session so future actions can run hands-free.
  • Use Case: Have your NanoClaw assistant post a daily status update, then like and quote relevant tweets during testing or operational troubleshooting.

Quick Start

Run the interactive login setup by telling the assistant to start x-integration authentication so your session is saved, then rebuild and restart NanoClaw to enable the X tools.

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 official X API?

You can automate X engagement actions like liking, replying, retweeting, and quoting tweets through Playwright-based scripted UI interactions driven by assistant-triggered tasks and IPC coordination between container tools and host scripts.

What is the best way to avoid bot detection when automating X Twitter actions?

Avoid bot detection on X by automating actions through your real browser session using a persistent authenticated Chrome profile, which mimics genuine user behavior instead of relying on blocked headless bot patterns.

Do I need to authenticate manually every time I run browser automation for tweet posting?

Yes, tweet length validation is enforced. The automation validates tweet content against the 280-character limit before publishing new tweets from assistant-initiated requests.

How does IPC coordination work for automating X engagement actions?

IPC coordination enables task execution between container tools and host scripts, allowing your assistant to trigger X engagement actions through host-side subprocess execution with defined timeouts for reliable browser automation.