skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
apidojo-io/apidojo-skills636 installs

discovering-pre-launch-startups-on-twitter

Discovers pre-launch startups and products on Twitter using apidojo's Twitter Search scraper. Triggers when the user asks to: find pre-launch startups on Twitter, discover companies building in stealth mode on X, find products in beta or waitlist mode on Twitter, identify early-stage startups before they launch publicly, find founders building in public before launch, discover startup waitlists or beta invites on Twitter, or research what new companies are building in a space. Returns startup handle, product description, waitlist/launch signals, stage, and niche. Ideal for VCs scouting early deals, accelerator scouts, and competitive intelligence teams.

How do I install this agent skill?

npx skills add https://github.com/apidojo-io/apidojo-skills --skill discovering-pre-launch-startups-on-twitter
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    This skill provides a template and instructions for using a Twitter scraper via the Apify platform to identify early-stage startups. It is a standard tool implementation that requires external credentials and script execution for data processing.

  • Socketpass

    No alerts

  • Snykwarn

    Risk: MEDIUM · 1 issue

What does this agent skill do?

Discovering Pre Launch Startups On Twitter

Executes discovering pre launch startups on twitter using apidojo scrapers. Part of the apidojo intelligence skills library.

Prerequisites

  • APIFY_TOKEN environment variable set
  • Optional: Apify MCP server installed

Inputs

ParameterTypeRequiredDefaultNotes
searchTermsarray✅[]Twitter advanced search queries (e.g. ["#AI lang:en", "from:NASA"])
sortstringOptionalTopSort order: Latest, Top, or Latest+Top
tweetLanguagestringOptional—ISO 639-1 language code (e.g. en)
maxItemsnumberOptionalUnlimitedMaximum tweets to return
onlyVerifiedUsersbooleanOptionalfalseOnly tweets from verified users
onlyTwitterBluebooleanOptionalfalseOnly Twitter Blue subscribers
onlyImagebooleanOptionalfalseOnly tweets with images
onlyVideobooleanOptionalfalseOnly tweets with videos
onlyQuotebooleanOptionalfalseOnly quote tweets
authorstringOptional—Filter to a specific author handle
inReplyTostringOptional—Tweets replying to a specific handle
mentioningstringOptional—Tweets mentioning a specific handle
geotaggedNearstringOptional—Tweets near a location
withinRadiusstringOptional—Radius around geotaggedNear
geocodestringOptional—Lat/lng + radius string
placeObjectIdstringOptional—Tweets tagged with a place
minimumRetweetsnumberOptional—Minimum retweet count
minimumFavoritesnumberOptional—Minimum like count
minimumRepliesnumberOptional—Minimum reply count
startstringOptional—Tweets after this date (YYYY-MM-DD)
endstringOptional—Tweets before this date (YYYY-MM-DD)
includeSearchTermsbooleanOptionalfalseAdd the matched search term to each tweet
customMapFunctionstringOptional—JavaScript function to transform each output object

Workflow

Progress:
- [ ] Step 1: Define parameters
- [ ] Step 2: Run tweet-scraper
- [ ] Step 3: Filter and classify results
- [ ] Step 4: Score by quality and relevance
- [ ] Step 5: Deliver output

Step 2: Run the Actor

Recommended — run_actor.js (handles waiting, output, and file saving automatically):

# Quick answer (prints table to chat)
node scripts/run_actor.js \
  --actor "apidojo~tweet-scraper" \
  --input '{"param": "value"}'

# Save as CSV
node scripts/run_actor.js \
  --actor "apidojo~tweet-scraper" \
  --input '{"param": "value"}' \
  --output YYYY-MM-DD_results.csv --format csv

# Save as JSON
node scripts/run_actor.js \
  --actor "apidojo~tweet-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": ["launching soon [SECTOR]", "beta waitlist [SECTOR]", "building [SECTOR] product", "#buildinpublic [SECTOR]", "soft launch [SECTOR]"],
  "maxItems": 100
}

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": ["launching soon [SECTOR]", "beta waitlist [SECTOR]", "building [SECTOR] product", "#buildinpublic [SECTOR]", "soft launch [SECTOR]"], "maxItems": 100}'

Wait for SUCCEEDED. Fetch dataset:

curl "https://api.apify.com/v2/actor-runs/$RUN_ID/dataset/items?token=$APIFY_TOKEN"

Step 3: Classify Results

classification: WAITLIST (accepting signups) | BETA (active testing) | STEALTH (building but not sharing product) | SOFT_LAUNCH (live but not announced widely)

Step 4: Score Each Result

score = pre_launch_score = (waitlist_signal ? 1 : 0) * 0.40 + (build_in_public_signal ? 1 : 0) * 0.30 + (followerCount < 5000 ? 1 : 0.5) * 0.20 + (tweeted_in_last_14_days ? 1 : 0) * 0.10

Step 5: Edge Cases

  • Pre-launch startups may tweet inconsistently; check last 10 tweets for product updates rather than bio alone to confirm active development

Additional fallbacks:

  • < 20 results: Broaden search terms; remove secondary filters
  • No results: Verify the search terms are correct; try alternate phrasings
  • Data quality issues: Remove entries with missing key fields; note count in output

Output Format

# Discovering Pre Launch Startups On Twitter
Results: [N] | Date: [DATE]

| # | [Key Field] | [Metric 1] | [Metric 2] | [Classification] | [Score] |
|---|------------|-----------|-----------|-----------------|---------|
| 1 | [value] | [value] | [value] | [type] | [0.XX] |

## Summary
Top result: [description]
Key finding: [insight]

Troubleshooting

Too few results: Broaden the primary search term; remove restrictive filters. Low quality results: Apply minimum score threshold (≥ 0.50) to filter noise. Actor fails to run: Verify API key; check actor status at apify.com/apidojo.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/apidojo-io/apidojo-skills/discovering-pre-launch-startups-on-twitter">View discovering-pre-launch-startups-on-twitter on skillZs</a>