building-twitter-industry-watchlist

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…

API Dojo

@apidojo-io

Install

$ openclaw skills install @apidojo-io/building-twitter-industry-watchlist

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

ParameterTypeRequiredDefaultNotes
startUrlsarrayOptional[]Twitter profile or tweet URLs
twitterHandlesarrayOptional[]Twitter usernames (without @)
twitterUserIdsarrayOptional[]Twitter user IDs
getFollowersbooleanOptionalfalseExtract follower lists
getFollowingbooleanOptionalfalseExtract following lists
getRetweetersbooleanOptionalfalseExtract retweeters of a tweet URL
includeUnavailableUsersbooleanOptionalfalseInclude unavailable/suspended users
maxItemsnumberOptionalUnlimitedMaximum users to return
customMapFunctionstringOptionalJavaScript 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):

# 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:

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.

Top skills in this category

description: 将用户讲稿一键生成乔布斯风极简科技感竖屏HTML演示稿。当用户需要生成PPT、演示文稿、Slides、幻灯片,或要求科技风/极简风/乔布斯风格的演示时触发此技能。输出为单个可直接运行的HTML文件。

@wwlyzzyorg

将讲稿一键生成乔布斯风极简科技感竖屏HTML演示稿

8534k

Feishu Evolver Wrapper

@autogame-17

(Depreciated: This skill is no longer maintained; its related functions have been absorbed by the Evolver main body.) Feishu-integrated wrapper for the capability-evolver. Manages the evolution loop lifecycle (start/stop/ensure), sends rich Feishu card reports, and provides...

1076k

Resume Assistant

@wscats

Assist job seekers by polishing, customizing, scoring, and exporting resumes with detailed checklist reviews and multi-format support.

1721k

Smart Model Switching

@millibus

Auto-route tasks to the cheapest Claude model that works correctly. Three-tier progression: Haiku → Sonnet → Opus. Classify before responding. HAIKU (default): factual Q&A, greetings, reminders, status checks, lookups, simple file ops, heartbeats, casual chat, 1-2 sentence tasks. ESCALATE TO SONNET: code >10 lines, analysis, comparisons, planning, reports, multi-step reasoning, tables, long writing >3 paragraphs, summarization, research synthesis, most user conversations. ESCALATE TO OPUS: architecture decisions, complex debugging, multi-file refactoring, strategic planning, nuanced judgment, deep research, critical production decisions. Rule: If a human needs >30 seconds of focused thinking, escalate. If Sonnet struggles with complexity, go to Opus. Save 50-90% on API costs by starting cheap and escalating only when needed.

216.8k

Writing Plans

@zlc000190

Use when you have a spec or requirements for a multi-step task, before touching code

813k