Twitter Operations

Automate and manage Twitter/X accounts by posting, scheduling, replying, analyzing, tracking trends, managing followers, and handling media and analytics.

This skill's manifest looks functionally plausible for Twitter/X automation, but there are important gaps and mismatches you should resolve before installing: 1) Ask the author to provide a clear description and to update registry metadata to declare the required credentials (OAuth keys/tokens) and config paths explicitly. 2) Verify where credentials are stored and whether they are encrypted; prefer environment variables or a secure secrets store over plaintext files in your home directory. 3) Confirm how webhooks are used and whether any monitored content could be forwarded externally; never supply a webhook you do not control. 4) Request an install spec or vetted package instructions for the listed Python dependencies so you can review and control what is installed. 5) Be cautious with features that scrape data or perform bulk follow/unfollow/block operations — they can violate platform policies and enable abusive behavior. If you cannot verify the author or get these clarifications, test the skill in an isolated account and environment or do not install.

Type: OpenClaw Skill Name: twitter-operations Version: 1.0.0 The skill is classified as suspicious due to several high-risk capabilities, even though no explicit malicious intent is demonstrated in the provided files. Key indicators include the ability to 'scrape tweets and user profiles' and 'archive tweets and user data' (implying extensive data collection), the `python-dotenv` dependency (allowing access to environment variables), and the use of 'alert-webhook' in examples (demonstrating outbound network connections to arbitrary URLs, a potential exfiltration vector). Additionally, 'bulk operations' and local file writing for analytics (`~/twitter_stats.csv`) present further risks if misused.