apidojo-io/apidojo-skills

finding-software-engineers-on-twitter

Finds software engineers and developers to recruit using apidojo's Twitter scrapers on Apify.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/apidojo-io/apidojo-skills --skill finding-software-engineers-on-twitter

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

Finding Software Engineers on Twitter

Discovers software engineers on Twitter/X via tech stack keywords, open-to-work signals, and engineering community activity. Twitter surfaces engineers who are active in their tech community — a strong passive candidate signal.

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
customMapFunctionstringOptional—JavaScript function to transform each output object

Workflow

Progress:
- [ ] Step 1: Search tweets by tech stack + role signals
- [ ] Step 2: Collect unique handles
- [ ] Step 3: Enrich profiles via twitter-user-scraper
- [ ] Step 4: Score candidate fit
- [ ] Step 5: Deliver candidate list

Step 1: Search Queries

Queries: ["[TECH_STACK] engineer", "[TECH_STACK] developer", "senior [TECH_STACK]",
          "built with [TECH_STACK]", "[TECH_STACK] open to work", "[TECH_STACK] job search"]

For open-to-work pass: add "looking for [TECH_STACK] role", "[TECH_STACK] available"

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": ["[TECH_STACK] engineer", "senior [TECH_STACK] developer", "built with [TECH_STACK]"],
  "maxItems": 300,
  "tweetLanguage": "en"
}

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": ["Python engineer", "senior Python developer", "built with Python"], "maxItems": 300}'

Collect unique author.username from results.

Step 2: Enrich Profiles

If Apify MCP is available:

Tool: apify:run-actor
Actor: "apidojo~twitter-user-scraper"
Input: {"usernames": ["[username1]", "[username2]", "..."]}

REST API fallback:

bash
curl -X POST \
  "https://api.apify.com/v2/acts/apidojo~twitter-user-scraper/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"usernames": ["handle1", "handle2"]}'

Step 3: Score Candidate Quality

Tech stack confirmation: bio or recent tweets mention the target tech stack → stack_confirmed = true

Role level proxy from bio:

  • "senior", "staff", "principal", "lead", "CTO", "VP Eng" → senior+
  • "mid", "3+ years", "5 years" → mid
  • "junior", "new grad", "bootcamp" → junior

Open-to-work score:

candidate_score = (stack_confirmed ? 1 : 0) * 0.35
                + (open_to_work_signal ? 1 : 0) * 0.30
                + (followerCount in 200..20000 ? 1 : 0.6) * 0.20
                + (tweeted_in_last_30_days ? 1 : 0) * 0.15

Active = tweeted in last 30 days; Passive = 30–90 days; Dormant = > 90 days

Step 4: Edge Cases

  • Results dominated by developer tools companies: Filter out accounts where followerCount > 50K and bio mentions company/brand — these are likely dev tool marketing accounts
  • Location filtering: Twitter bio location is free text — use contains match; filter out profiles with ambiguous or non-geographic location entries
  • < 20 results for niche stack: Broaden to language family (e.g. "Rust" → "systems programming") or remove role level filter
  • Bot accounts: Flag profiles where follower/following ratio < 0.05 AND tweetsCount < 10 as likely bots

Output Format

# Software Engineer Candidates: [TECH_STACK]
Profiles found: [N] | Open-to-work: [N] | Senior: [N] | Mid: [N] | Active: [N] | Date: [DATE]

## Priority: Open-to-Work Candidates
| Name | @Handle | Role Level | Location | Stack Confirmed | Followers | Last Active | Score |
|------|---------|-----------|---------|----------------|-----------|------------|-------|
| [name] | @[handle] | Senior | [city] | ✓ | [N] | [X days ago] | [0.XX] |

## Passive Candidates (Not Actively Searching)
| Name | @Handle | Role Level | Location | Stack | Followers | Score |
|------|---------|-----------|---------|-------|-----------|-------|

## Bio Highlights
Top 5 candidates — summarized bios:
1. @[handle]: "[bio excerpt]" — [tech signals]

Troubleshooting

Results are all companies not individuals: Add "-company -official -team -agency" as negative search terms, or filter bio for first-person pronouns. Tech stack too common returns too many results: Add a second filter — location OR seniority level — to reduce to a manageable size. Few open-to-work signals: Most passive candidates don't signal openly; focus outreach on the passive tier with personalized messages referencing their recent tweets.

Related by task

from this repository

More skills

All skills
apidojo-io
Community

discovering-tiktok-creators-by-niche

Discovers and ranks TikTok creators in any niche or topic using apidojo's TikTok scrapers on Apify. Triggers when the user asks to: find TikTok influencers in a specific niche, discover creators for a campaign, identify who's growing fastest on TikTok in a category, find micro-influencers on TikTok under a certain follower count, build a list of TikTok creators for brand partnerships, compare TikTok creator engagement rates in a vertical, or identify rising TikTok stars. Returns creator username

1h installs
2
GitHub stars
1
Updated
May 13
apidojo-io
Community

finding-gaming-content-creators

Finds gaming content creators on TikTok and YouTube using apidojo's scrapers on Apify. Triggers when the user asks to: find gaming influencers for brand campaigns, discover streamers or gaming YouTubers in a specific game or genre, find TikTok creators posting gaming content, identify gaming micro-influencers for product sponsorships, find gaming creators who review hardware or accessories, build a gaming creator outreach list for a gaming brand or peripheral company, or discover rising gaming c

1h installs
2
GitHub stars
1
Updated
May 13
apidojo-io
Community

scraping-instagram-posts-by-hashtag

Scrapes Instagram posts for any hashtag using apidojo's Instagram scraper on Apify. Triggers when the user asks to: get Instagram posts for a hashtag, scrape Instagram content by tag, export Instagram post data for a keyword or topic, fetch posts under an Instagram challenge or trend, collect Instagram media for a specific tag, or download Instagram post metadata by hashtag. Returns post URL, caption, like count, comment count, author handle, and timestamp per post. Ideal for trend analysts, UGC

1h installs
2
GitHub stars
1
Updated
May 13
apidojo-io
Community

scraping-tiktok-profile-data

Scrapes TikTok profile statistics and metadata for any list of accounts using apidojo's TikTok Profile scraper on Apify. Triggers when the user asks to: get TikTok profile stats for an account, fetch follower count and engagement data for TikTok users, scrape TikTok account metadata in bulk, export TikTok profile information for a list of creators, check TikTok stats for multiple usernames, or get bio and follower data from TikTok profiles. Returns username, follower count, following count, tota

1h installs
1
GitHub stars
1
Updated
May 13