building-twitter-industry-watchlist — Claude Code skill: X accounts
Builds a curated list of key voices in an industry on X, with handle, follower count, engagement and an influence score.
npx skills add apidojo-io/apidojo-skills --skill building-twitter-industry-watchlist -a claude-codeWhat building-twitter-industry-watchlist does
The skill searches industry conversations, keeps authors whose tweets pull likes and replies, then sorts them into founders, investors, analysts, journalists and practitioners. You get a table with handle, followers, average engagement, topic focus and a signal score, plus a short note on turning the list into a Twitter List.
Two Apify actors sit underneath: apidojo/twitter-user-scraper and apidojo/tweet-scraper. Run them with scripts/run_actor.js and save to CSV or JSON, through an Apify MCP server if you have one, or with a plain curl call to the REST API. The influence score adds four parts: retweet and reply share against follower count, audience size, and how often the account posts on the topic over 30 days.
You need APIFY_TOKEN in your environment or a .env file — none of the three run paths work without it. When news accounts crowd out actual community members, the skill suggests searching by industry hashtag instead. Watchlists grow fast: accounts below a 0.60 score get cut, and daily reading works best at 40 or fewer.
What it helps with
- build a shortlist of key accounts in an industry on X
- filter out bots and promo accounts by retweet-to-like ratio
- score influence from engagement and audience size
- sort the people found into founder, investor and analyst roles
- export the list to CSV or JSON for a report
Example prompts for the agent
- build a Twitter watchlist for the venture capital space, up to 40 accounts
- find the key security analysts worth following on X
- compile founders and investors in fintech and save it as CSV
How to install building-twitter-industry-watchlist
1Skills CLI (Vercel)
npx skills add apidojo-io/apidojo-skills --skill building-twitter-industry-watchlist -a claude-code2Manually: put the files in place
~/.claude/skills/building-twitter-industry-watchlist/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/building-twitter-industry-watchlist/
1Skills CLI (Vercel)
npx skills add apidojo-io/apidojo-skills --skill building-twitter-industry-watchlist -a codex2Manually: put the files in place
.agents/skills/building-twitter-industry-watchlist/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add apidojo-io/apidojo-skills --skill building-twitter-industry-watchlist -a cursor2Manually: put the files in place
.cursor/skills/building-twitter-industry-watchlist/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install apidojo-io/apidojo-skills building-twitter-industry-watchlist2Manually: put the files in place
.github/skills/building-twitter-industry-watchlist/SKILL.md1Skills CLI (Vercel)
npx skills add apidojo-io/apidojo-skills --skill building-twitter-industry-watchlist -a gemini-cli2Platform CLI
gemini skills install https://github.com/apidojo-io/apidojo-skills --path skills/intent/building-twitter-industry-watchlistManually: put the files in place
.devin/skills/building-twitter-industry-watchlist/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add apidojo-io/apidojo-skills --skill building-twitter-industry-watchlist -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about building-twitter-industry-watchlist
How do I install building-twitter-industry-watchlist in Claude?
Run npx skills add apidojo-io/apidojo-skills --skill building-twitter-industry-watchlist -a claude-code. The skill file then lands at ~/.claude/skills/building-twitter-industry-watchlist/SKILL.md.
What does building-twitter-industry-watchlist do?
It searches industry tweets, picks out high-engagement authors and returns a table with handle, followers, topic focus and an influence score. Accounts are grouped into founders, investors, analysts, journalists and practitioners.
What do I need before running the skill?
An APIFY_TOKEN environment variable, required by both scripts/run_actor.js and the REST API path. The Apify MCP server is optional and just gives you another way to launch the actors.
Source text
SKILL.md · Apache-2.0
---
name: building-twitter-industry-watchlist
description: >
Builds a curated Twitter industry watchlist of key voices using apidojo's Twitter scrapers on Apify.
Triggers when the user asks to: build a Twitter watchlist for an industry, find key Twitter accounts
to follow in a niche, create a curated list of thought leaders in a sector on X, identify the most
influential Twitter accounts in a business category, build a Twitter list for industry monitoring,
find the signal-to-noise accounts in a topic area, or compile the must-follow accounts for staying
current in an industry.
Returns account list with handle, follower count, engagement rate, topic focus, and influence score.
Ideal for business analysts, investors, executives, and professionals doing industry intelligence.
license: Apache-2.0
metadata:
author: apidojo
version: "1.0"
apify-actors: apidojo/twitter-user-scraper, apidojo/tweet-scraper
---
# Building a Twitter Industry Watchlist
Identifies highest-signal Twitter accounts in an industry — people whose tweets consistently generate discussion, surface new information, or shape thinking in the space.
## Prerequisites
- `APIFY_TOKEN` environment variable set
- Optional: Apify MCP server installed
## Inputs
| Parameter | Type | Required | Default | Notes |
|-----------|------|----------|---------|-------|
| `startUrls` | array | Optional | `[]` | Twitter profile or tweet URLs |
| `twitterHandles` | array | Optional | `[]` | Twitter usernames (without @) |
| `twitterUserIds` | array | Optional | `[]` | Twitter user IDs |
| `getFollowers` | boolean | Optional | `false` | Extract follower lists |
| `getFollowing` | boolean | Optional | `false` | Extract following lists |
| `getRetweeters` | boolean | Optional | `false` | Extract retweeters of a tweet URL |
| `includeUnavailableUsers` | boolean | Optional | `false` | Include unavailable/suspended users |
| `maxItems` | number | Optional | Unlimited | Maximum users to return |
| `customMapFunction` | string | Optional | — | JavaScript function to transform each output object |
## Workflow
```
Progress:
- [ ] Step 1: Search for high-engagement industry tweets
- [ ] Step 2: Collect influential account handles
- [ ] Step 3: Enrich and score
- [ ] Step 4: Classify by account type
- [ ] Step 5: Deliver curated watchlist
```
### Step 1: Search Industry Conversations
**Recommended — run_actor.js (handles waiting, output, and file saving automatically):**
```bash
# Quick answer (prints table to chat)
node scripts/run_actor.js \
--actor "apidojo~twitter-user-scraper" \
--input '{"param": "value"}'
# Save as CSV
node scripts/run_actor.js \
--actor "apidojo~twitter-user-scraper" \
--input '{"param": "value"}' \
--output YYYY-MM-DD_results.csv --format csv
# Save as JSON
node scripts/run_actor.js \
--actor "apidojo~twitter-user-scraper" \
--input '{"param": "value"}' \
--output YYYY-MM-DD_results.json --format json
```
> `APIFY_TOKEN` must be set in environment or `.env` file.
**If Apify MCP is available:**
```
Tool: apify:run-actor
Actor: "apidojo~tweet-scraper"
Input:
{
"searchTerms": ["[INDUSTRY]", "#[industry]", "[INDUSTRY] trends", "[INDUSTRY] analysis"],
"maxItems": 500
}
```
**REST API fallback:**
```bash
curl -X POST \
"https://api.apify.com/v2/acts/apidojo~tweet-scraper/runs?token=$APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"searchTerms": ["venture capital", "#vc", "VC trends 2026"], "maxItems": 500}'
```
Collect authors with `likeCount + replyCount >= 10` on their industry tweets.
### Step 2: Score Influence
```
signal_score = (retweets / followers * 1000) * 0.35
+ (replies / followers * 1000) * 0.30
+ min(followers / 100000, 1) * 0.20
+ (tweeted_industry_content >= 3 in 30 days ? 1 : 0) * 0.15
```
**Account type from bio:**
- FOUNDER: "founder", "CEO", "built"
- INVESTOR: "partner", "VC", "investor"
- ANALYST: "analyst", "researcher", "writer"
- JOURNALIST: known pub or "reporter", "journalist"
- PRACTITIONER: role title at company
### Step 3: Edge Cases
- **Bot accounts**: `retweetCount >> likeCount` → flag if retweets > 5× likes
- **Ambiguous type**: Use `PRACTITIONER` as default when unclear
- **Multiple accounts from same company**: Keep the most influential one
## Output Format
```
# [INDUSTRY] Twitter Watchlist
Accounts: [N] | Date: [DATE]
## Founders & Operators
| Name | @Handle | Role | Followers | Avg Likes | Signal Score |
|------|---------|------|-----------|----------|-------------|
## Investors & Analysts
| Name | @Handle | Role | Followers | Signal Score |
|------|---------|------|-----------|-------------|
## Press & Media
| Name | @Handle | Publication | Followers | Signal Score |
|------|---------|------------|-----------|-------------|
## How to Create Twitter List
Go to Twitter → Lists → Create List → Add members by username
```
## Troubleshooting
**Results are news not insiders**: Use `#[industry]` hashtag to find community members vs. general readers.
**Too many promotional accounts**: Filter accounts where > 50% of tweets include external links.
**Watchlist too large**: Apply score cutoff ≥ 0.60; keep ≤ 40 accounts for daily readability.
© apidojo · Apache-2.0 · apidojo-io/apidojo-skills