twitter

Retrieves content from Twitter/X through the twitterapi.io service, covering user profiles, tweets, replies, followers and following, communities, spaces, and trends. It is intended to trigger whenever a request mentions Twitter, X, or tweets, and it works through a collection of Python scripts run from the skill directory.

The scripts are grouped by endpoint type. User endpoints fetch profile and about information, batch user lookups, a user's tweets and mentions, followers and following including verified followers, relationship checks between two users, and user search. Tweet endpoints retrieve individual tweets, run tweet searches, and pull replies, quotes, retweeters, full threads, and articles. List endpoints return list followers and members; community endpoints cover community details, members, moderators, tweets, and community-scoped search; and additional endpoints retrieve a space or the current trends by WOEID.

Search is expressive, supporting query syntax such as filtering to a specific user's posts, since and until date ranges, excluding retweets, filtering for media, and requiring a minimum number of favorites, as well as choosing a result type like Latest. Most listing commands accept a limit argument to bound how many results are returned. Setup requires a twitterapi.io API key exported as an environment variable in the shell profile, after which a quick check can confirm access by pulling a known user's info. Under the hood the scripts call the twitterapi.io base URL with the key passed in an X-API-Key header. The documentation notes approximate pricing of about 0.15 to 0.18 US dollars per thousand requests, so usage carries a per-request cost that scales with how many endpoints are called and how large a limit each task uses.