X CDP Automation

Automate X (Twitter) via Chromium CDP: post tweets, reply, quote-retweet, publish articles. Uses real browser sessions with existing login, no API keys neede...

What to consider before installing/using this skill: - Review the scripts locally before running. The tool will operate the browser using your profile, so it can act with whatever X session (cookies/tokens) is present. - Prefer creating and using an isolated Chromium profile (not your main profile) via the --profile and --port flags to avoid exposing other sessions or data. - Run with --dry-run first to verify behavior; dry-run saves a screenshot under /tmp so you can confirm the composed content won't be posted. - The setup auto-installs puppeteer-core into /tmp via npm. Consider installing puppeteer-core yourself (verify version) and setting NODE_PATH instead of letting the script auto-install. - Because the script spawns Chromium with a user-data-dir, any attacker or misused script could post as you — only run this on machines you control and avoid using your primary account if you want extra safety. - If you want stronger isolation, run this inside a disposable VM or container and/or inspect /tmp/node_modules after installation to ensure no unexpected packages were installed. - Limit agent autonomy: require explicit user confirmation before posting (the SKILL.md describes an approval step — keep that in place). Do not grant blanket autonomous invocation to the agent without oversight. - If unsure, test on a secondary or throwaway X account first.

Type: OpenClaw Skill Name: x-cdp Version: 1.0.0 The skill is classified as suspicious due to a critical vulnerability in `scripts/post-article.js`. The `--body-file` argument allows reading arbitrary local files using `fs.readFileSync`. While intended for article content, this could be exploited via prompt injection against the agent to read sensitive files (e.g., `/etc/passwd`, `~/.ssh/id_rsa`) and potentially publish their content to X, leading to unauthorized data disclosure. Other scripts use `execSync` and `spawn` (e.g., `scripts/setup.js` for `npm install puppeteer-core` and launching Chromium), which are powerful but appear to be used for legitimate setup purposes, not for malicious execution or exfiltration.