Give your agent read-only Twitter/X data—search, threads, profiles, trends—via thirteen twitterapi.io tools.
Overview
twitter is an agent skill for the Build phase that registers 13 read-only Twitter/X data tools powered by twitterapi.io.
Install
npx skills add https://github.com/starchild-ai-agent/official-skills --skill twitterWhat is this skill?
- 13 read-only tools: search, tweets by ID, articles, threads, quotes, trends
- User graph helpers: info, tweets, followers, followings
- Engagement tools: replies, retweeters, user search
- Auto-loaded ExtensionLoader entry point with register(api)
- Requires TWITTER_API_KEY for twitterapi.io
- 13 registered Twitter/X read tools
- TWITTER_API_KEY required environment variable
Adoption & trust: 6.6k installs on skills.sh; 13 GitHub stars; 1/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your agent needs X search, threads, and profile data but you do not want to maintain custom API clients and parsers.
Who is it for?
Solo builders shipping agent extensions that research trends, monitor accounts, or enrich launch intel from X.
Skip if: Teams that need tweet posting, DMs, or write access—this extension is read-only via twitterapi.io.
When should I use this skill?
Extension auto-loaded by ExtensionLoader when the Twitter package is present and TWITTER_API_KEY is set.
What do I get? / Deliverables
Your extension host loads named Twitter tools so agents can query public X data read-only with a single API key.
- Registered tool names from register(api)
- Agent-callable read endpoints for X data
Recommended Skills
Journey fit
Extension wiring belongs in Build when you connect external APIs to your agent runtime. Integrations is the canonical shelf because the skill registers third-party Twitter tools behind TWITTER_API_KEY.
How it compares
An agent integration package, not an MCP server or official X enterprise contract—data via twitterapi.io abstraction.
Common Questions / FAQ
Who is twitter for?
Developers wiring Starchild-compatible agents who need structured, read-only Twitter/X fetches inside tool-calling loops.
When should I use twitter?
During Build integrations when prototyping social research agents, and later in Grow or Launch when those agents power distribution or lifecycle monitoring—always as a read-only data layer.
Is twitter safe to install?
Check Prism’s Security Audits panel; you must supply TWITTER_API_KEY and treat third-party API traffic, rate limits, and data handling per twitterapi.io terms.
SKILL.md
READMESKILL.md - Twitter
""" Twitter/X Extension — Read-only data via twitterapi.io Provides 13 tools for Twitter/X data: - twitter_search_tweets: Advanced tweet search - twitter_get_tweets: Get tweets by ID - twitter_get_article: Get long-form article by tweet ID - twitter_tweet_thread_context: Get complete thread context - twitter_tweet_quote: Get quote tweets for a tweet - twitter_get_trends: Get trends - twitter_user_info: User profile lookup - twitter_user_tweets: User's recent tweets - twitter_user_followers: User's followers - twitter_user_followings: User's followings - twitter_tweet_replies: Replies to a tweet - twitter_tweet_retweeters: Users who retweeted - twitter_search_users: Search for users Environment Variables: - TWITTER_API_KEY: API key for twitterapi.io (required) Usage: This extension is auto-loaded by the ExtensionLoader. """ import logging from typing import List logger = logging.getLogger(__name__) def register(api) -> List[str]: """ Extension entry point — register all Twitter tools. Args: api: ExtensionApi instance with registry and config Returns: List of registered tool names """ registered = [] try: from .tools import ( TwitterSearchTweetsTool, TwitterGetTweetsTool, TwitterGetArticleTool, TwitterTweetThreadContextTool, TwitterTweetQuoteTool, TwitterGetTrendsTool, TwitterUserInfoTool, TwitterUserTweetsTool, TwitterUserFollowersTool, TwitterUserFollowingsTool, TwitterTweetRepliesTool, TwitterTweetRetweetersTool, TwitterSearchUsersTool, ) api.register_tool(TwitterSearchTweetsTool()) api.register_tool(TwitterGetTweetsTool()) api.register_tool(TwitterGetArticleTool()) api.register_tool(TwitterTweetThreadContextTool()) api.register_tool(TwitterTweetQuoteTool()) api.register_tool(TwitterGetTrendsTool()) api.register_tool(TwitterUserInfoTool()) api.register_tool(TwitterUserTweetsTool()) api.register_tool(TwitterUserFollowersTool()) api.register_tool(TwitterUserFollowingsTool()) api.register_tool(TwitterTweetRepliesTool()) api.register_tool(TwitterTweetRetweetersTool()) api.register_tool(TwitterSearchUsersTool()) registered = [ "twitter_search_tweets", "twitter_get_tweets", "twitter_get_article", "twitter_tweet_thread_context", "twitter_tweet_quote", "twitter_get_trends", "twitter_user_info", "twitter_user_tweets", "twitter_user_followers", "twitter_user_followings", "twitter_tweet_replies", "twitter_tweet_retweeters", "twitter_search_users", ] logger.info(f"Registered Twitter tools ({len(registered)} tools)") except Exception as e: logger.warning(f"Failed to load Twitter tools: {e}") return registered # Extension metadata EXTENSION_INFO = { "name": "twitter", "version": "1.1.0", "description": "Twitter/X data — search tweets, article, thread context, quote tweets, trends, users", "tools": [ "twitter_search_tweets", "twitter_get_tweets", "twitter_get_article", "twitter_tweet_thread_context", "twitter_tweet_quote", "twitter_get_trends", "twitter_user_info", "twitter_user_tweets", "twitter_user_followers", "twitter_user_followings", "twitter_tweet_replies", "twitter_tweet_retweeters", "twitter_search_users", ], "env_vars": [ "TWITTER_API_KEY", ], } """ Twitter API client — wraps twitterapi.io endpoints. Read-only: search tweets, user profiles, followers, replies, thread context, quote tweets, article, and trends. Auth: X-API-Key header from TWITTER_API_KEY env var. ""