Skip to main content
Category: GTM Intelligence · Version: 0.0.1 · Author: opendirectory · Compatibility: All targets (claude, codex, opencode, gemini, anti-gravity, openclaw, hermes)
Generated_chart__twitter-gtm-find-cover-bw png Find developer-first GTM, DevRel, and Growth hiring signals from X/Twitter, then verify funding and product fit. This pipeline uses Apify as the default discovery path. OpenClaw users can also use TweetClaw for tweet search, reply search, user lookup, follower export, monitors, and webhooks before the same ICP validation step.

​
Install

​
The Skill Directory

All executable code and documentation are packaged cleanly inside the twitter-GTM-find/ folder. This is designed to be directly imported and read by AI agents (like OpenClaw or Claude) so they understand how to use the tool.

​
Usage

To run the pipeline manually or via an agent:
  1. Create a .env file at the root of the repository:
  2. Run the shell script:

​
Optional Native X/Twitter Plugin Paths

The existing Apify pipeline remains the default end-to-end workflow. For OpenClaw users who already run TweetClaw, the skill can also use TweetClaw as a native OpenClaw plugin for the first discovery pass:
After setting XQUIK_API_KEY, use explore to find the relevant tweet search, reply search, user lookup, follower export, monitor, and webhook endpoints. Use tweetclaw to scrape tweets, search tweets and replies, look up founders or company accounts, export followers, and monitor promising leads during this workflow. For Hermes users who already run Hermes Tweet, the skill can also use Hermes Tweet as a native Hermes Agent X/Twitter plugin for the first discovery pass:
After setting XQUIK_API_KEY, use tweet_explore to scrape/search tweets or search Twitter/X for GTM, DevRel, growth, and startup hiring signals. Use tweet_read to read tweet replies, look up users, and monitor tweets from promising founders or company accounts. Use tweet_action only for read-side exports such as export followers during this workflow. Keep the pipeline’s validation step intact: export the Hermes Tweet findings or TweetClaw findings into the same candidate review shape, then run the ICP checks before any outreach. Post tweets, post replies, send DMs, and other automated X actions should stay confirmation-gated and outside unattended discovery runs.

​
Output

The pipeline generates two temporary files at the root of the repository (which are .gitignored to prevent leaking data):
  • radar-jobs.json: The initial raw batch of scraped tech jobs.
  • openclaw-icp-jobs.json: The final, strict ICP-validated list of highly funded, developer-first startups hiring right now.