Menu
Post tweets, like, reply, retweet, and quote on X (Twitter) using browser automation. Use when the user asks you to interact with X/Twitter.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when managing the pynchy service on the server — deploying changes, observing logs, checking service status, restarting the service, setting up GitHub auth, rebuilding the agent container, or running commands on the live Pynchy host. Also use when interacting with the LiteLLM proxy — investigating failed requests, model routing errors, spend tracking, health checks, API gateway diagnostics, or modifying the LiteLLM configuration. Also use when the user mentions the LiteLLM UI, dashboard, proxy errors, or model availability.
Use when creating, scaffolding, or updating a pynchy plugin, including channels, MCP servers, skills, agent cores, workspace specs, and container runtime plugins. Also use when users ask how to register plugins via config.toml, add entry points, or validate plugin hook wiring.
Drive a host desktop through Pynchy's policy-mediated provider plugins when browser automation is inappropriate.
How to use browser tools for web navigation and interaction
Refresh expired Slack browser tokens (xoxc/xoxd) using persistent browser sessions. Use when Slack MCP tools fail with authentication errors.
When running multi-line Python code or code with quotes, apostrophes, or f-strings via Bash, always use heredoc syntax instead of python -c to avoid shell quoting issues.
| name | x-integration |
| description | Post tweets, like, reply, retweet, and quote on X (Twitter) using browser automation. Use when the user asks you to interact with X/Twitter. |
| tier | social |
Automate X/Twitter actions via Playwright browser automation, persistent Chromium profile.
Need system Chrome/Chromium binary — CHROME_PATH must be set in .env (e.g. CHROME_PATH=/usr/bin/google-chrome-stable). Playwright bundled Chromium not used — X fingerprint as bot.
All X tools run headed mode (not headless) — X detect + block headless browsers. Headless servers need Xvfb (apt install xvfb).
Interactive login via setup_x_session also need VNC (apt install x11vnc novnc).
Playwright drive system Chrome binary (via CHROME_PATH) with persistent browser contexts. After one manual login (human do CAPTCHA / 2FA), next actions run auto from saved session. All tools use headed mode + anti-detection flags to dodge X bot fingerprinting.
Human must log in once before any X action:
setup_x_session()
Opens visible Chromium window at X login page. Human do login flow. Session saved for future auto use.
On headless server (no X display), tool auto-starts Xvfb + noVNC on port 6080. Before call setup_x_session, tell human open http://<server>:6080/vnc.html?autoconnect=true in browser.
Hardware security keys (YubiKey, FIDO2): noVNC cannot forward WebAuthn challenges — key must physically connect to machine running browser. If X login need hardware key, run setup_x_session on local machine with key attached, then rsync profile to server:
rsync -az data/playwright-profiles/x/ server:path/to/pynchy/data/playwright-profiles/x/
setup_x_session(timeout_seconds=120)Launch headed browser for manual X login. Saves session to persistent profile for future use.
timeout_seconds — wait time for login completion (default: 120s)x_post(content)Post tweet. Content 1–280 chars.
x_like(tweet_url)Like tweet. Accepts full URL (https://x.com/user/status/123) or bare tweet ID.
x_reply(tweet_url, content)Reply to tweet. Content 1–280 chars.
x_retweet(tweet_url)Retweet, no comment.
x_quote(tweet_url, comment)Quote tweet with comment. Comment 1–280 chars.
setup_x_session again.timeout_seconds.CHROME_PATH in .env to system Chrome/Chromium binary path.