Twitter intelligence skill
Search tweets, analyze trends, monitor users, and gather social intelligence from Twitter/X through SandBase.
by sandbaseai·Apache-2.0 license·★ 203 Stars on the repo·GitHub ↗
npx degit sandbaseai/sandbase-skills/research/twitter-intelligence#main ~/.claude/skills/twitter-intelligenceChecked ·commit main
Inside this skill
SKILL.md · the author's own words# Twitter Intelligence Full-spectrum Twitter/X research and social listening through SandBase. Search public tweets, discover trends, analyze user profiles, and m… ## Call SandBase capabilities Use the capability identifiers below as discovery hints, not MCP tool names. Find the matching endpoint with `sandbase_discover(q: "<provid… ## Operating principles - Use Twitter data as social signal evidence, not as representative public opinion. - Separate observations (tweet volume, engagement, accounts posting) from interpretation (sentiment, trend direction). - Preserve attribution: include tweet URLs, usernames, dates, and engagement metrics. - Never post, like, retweet, follow, or engage on behalf of the user. - Keep monitored accounts and strategy confidential unless sharing is requested.
Word-for-word excerpt, not a result. Read the full SKILL.md ↓
Files of Twitter intelligence
Show the full text74 lines
Twitter Intelligence
Full-spectrum Twitter/X research and social listening through SandBase. Search public tweets, discover trends, analyze user profiles, and monitor discussions — all read-only, never posts or engages. Read the API map before selecting a capability.
Call SandBase capabilities
Use the capability identifiers below as discovery hints, not MCP tool names. Find the matching endpoint with sandbase_discover(q: "<provider and capability>"); use its returned name in sandbase_inspect(name: "<returned name>"). Read inputSchema, pricing, and execute_as, then call sandbase_run using execute_as.arguments.name and schema-defined arguments. If a run_id is returned, poll sandbase_run_get(run_id: "<returned run_id>") within the task budget until completed or failed; report pending or failed runs without resubmitting them automatically.
Operating principles
- Use Twitter data as social signal evidence, not as representative public opinion.
- Separate observations (tweet volume, engagement, accounts posting) from interpretation (sentiment, trend direction).
- Preserve attribution: include tweet URLs, usernames, dates, and engagement metrics.
- Never post, like, retweet, follow, or engage on behalf of the user.
- Keep monitored accounts and strategy confidential unless sharing is requested.
Workflow
1. Frame the research
Classify the request:
- Trend discovery: what's trending, emerging topics
- Topic monitoring: track discussions around a keyword or brand
- User analysis: profile, content, followers, engagement patterns
- Sentiment tracking: how people feel about a topic or brand
- Competitor intelligence: what competitors post and how audiences respond
2. Search tweets
Use twitter_web_search_timeline for keyword-based tweet discovery:
- Search for brand names, product names, hashtags, or topic phrases
- Use negative keywords to filter noise
- Compare search results for competitors side by side
Use twitter_bulk_tweet_search for higher-volume batch searches.
3. Discover trends
Use twitter_web_trending to find what's trending globally or by location.
4. Analyze users
Use twitter_web_user_profile for account details (bio, follower count, verified status).
Use twitter_web_user_media and tweet timeline tools for content analysis.
Use twitter_web_user_followers / twitter_web_user_followings for network analysis.
5. Deep-dive tweets
Use twitter_web_tweet_detail for specific tweet metrics and thread context.
Use twitter_web_latest_post_comments or twitter_web_post_comments for reply analysis.
Output
Return: search scope, tweet volume summary, key accounts involved, sentiment signals, trend indicators, engagement patterns, and evidence gaps.
Example tasks
- "What are people saying about [brand] on Twitter this week?"
- "Find trending topics in the AI/tech space right now."
- "Analyze @competitor's Twitter presence — posting frequency, engagement, top content."
- "Monitor mentions of [product launch] and summarize sentiment."
- "Who are the most influential voices discussing [topic] on Twitter?"
Failure handling
- If SandBase is unavailable, report the failure and do not substitute a direct API.
- If searches return few results, try broader terms or related hashtags.
- If a user account is private/suspended, note the gap and continue with available data.
| 1 | |
| 2 | name twitter-intelligence |
| 3 | description Search tweets, analyze trends, monitor users, and gather social intelligence from Twitter/X through SandBase. Use when asked for Twitter research, social listening, trend analysis, influencer monitoring, sentiment tracking, or competitor social intelligence. |
| 4 | |
| 5 | |
| 6 | # Twitter Intelligence |
| 7 | |
| 8 | Full-spectrum Twitter/X research and social listening through SandBase. Search public tweets, discover trends, analyze user profiles, and monitor discussions — all read-only, never posts or engages. Read [the API map] before selecting a capability. |
| 9 | |
| 10 | ## Call SandBase capabilities |
| 11 | |
| 12 | Use the capability identifiers below as discovery hints, not MCP tool names. Find the matching endpoint with `sandbase_discover(q: "<provider and capability>")`; use its returned `name` in `sandbase_inspect(name: "<returned name>")`. Read `inputSchema`, pricing, and `execute_as`, then call `sandbase_run` using `execute_as.arguments.name` and schema-defined `arguments`. If a `run_id` is returned, poll `sandbase_run_get(run_id: "<returned run_id>")` within the task budget until `completed` or `failed`; report pending or failed runs without resubmitting them automatically. |
| 13 | |
| 14 | ## Operating principles |
| 15 | |
| 16 | Use Twitter data as social signal evidence, not as representative public opinion. |
| 17 | Separate observations (tweet volume, engagement, accounts posting) from interpretation (sentiment, trend direction). |
| 18 | Preserve attribution: include tweet URLs, usernames, dates, and engagement metrics. |
| 19 | Never post, like, retweet, follow, or engage on behalf of the user. |
| 20 | Keep monitored accounts and strategy confidential unless sharing is requested. |
| 21 | |
| 22 | ## Workflow |
| 23 | |
| 24 | ### 1. Frame the research |
| 25 | |
| 26 | Classify the request: |
| 27 | **Trend discovery**: what's trending, emerging topics |
| 28 | **Topic monitoring**: track discussions around a keyword or brand |
| 29 | **User analysis**: profile, content, followers, engagement patterns |
| 30 | **Sentiment tracking**: how people feel about a topic or brand |
| 31 | **Competitor intelligence**: what competitors post and how audiences respond |
| 32 | |
| 33 | ### 2. Search tweets |
| 34 | |
| 35 | Use `twitter_web_search_timeline` for keyword-based tweet discovery: |
| 36 | Search for brand names, product names, hashtags, or topic phrases |
| 37 | Use negative keywords to filter noise |
| 38 | Compare search results for competitors side by side |
| 39 | |
| 40 | Use `twitter_bulk_tweet_search` for higher-volume batch searches. |
| 41 | |
| 42 | ### 3. Discover trends |
| 43 | |
| 44 | Use `twitter_web_trending` to find what's trending globally or by location. |
| 45 | |
| 46 | ### 4. Analyze users |
| 47 | |
| 48 | Use `twitter_web_user_profile` for account details (bio, follower count, verified status). |
| 49 | Use `twitter_web_user_media` and tweet timeline tools for content analysis. |
| 50 | Use `twitter_web_user_followers` / `twitter_web_user_followings` for network analysis. |
| 51 | |
| 52 | ### 5. Deep-dive tweets |
| 53 | |
| 54 | Use `twitter_web_tweet_detail` for specific tweet metrics and thread context. |
| 55 | Use `twitter_web_latest_post_comments` or `twitter_web_post_comments` for reply analysis. |
| 56 | |
| 57 | ## Output |
| 58 | |
| 59 | Return: search scope, tweet volume summary, key accounts involved, sentiment signals, trend indicators, engagement patterns, and evidence gaps. |
| 60 | |
| 61 | ## Example tasks |
| 62 | |
| 63 | "What are people saying about [brand] on Twitter this week?" |
| 64 | "Find trending topics in the AI/tech space right now." |
| 65 | "Analyze @competitor's Twitter presence — posting frequency, engagement, top content." |
| 66 | "Monitor mentions of [product launch] and summarize sentiment." |
| 67 | "Who are the most influential voices discussing [topic] on Twitter?" |
| 68 | |
| 69 | ## Failure handling |
| 70 | |
| 71 | If SandBase is unavailable, report the failure and do not substitute a direct API. |
| 72 | If searches return few results, try broader terms or related hashtags. |
| 73 | If a user account is private/suspended, note the gap and continue with available data. |
| 74 |
Discussion
Alternatives
Browse more free Claude skills or everything in Marketing.