$npx -y skills add Varnan-Tech/opendirectory --skill twitter-GTM-findEnd-to-end pipeline for scraping X/Twitter for GTM/DevRel tech startup jobs using Apify, or optionally TweetClaw for OpenClaw and Hermes Tweet for Hermes Agent, then validating them against an Ideal Customer Profile (ICP) using Gemini's native Google Search Grounding. Use this sk
| 1 | # Twitter GTM Find Skill |
| 2 | |
| 3 | This skill provides an automated pipeline to scrape Twitter for Developer-First startups hiring GTM/DevRel roles, followed by an automatic web-search verification step to validate them against our Ideal Customer Profile (ICP). |
| 4 | |
| 5 | ## Using the Pipeline |
| 6 | |
| 7 | You can run the full pipeline using the executable Node.js project bundled in `scripts/`. |
| 8 | |
| 9 | ```bash |
| 10 | cd scripts |
| 11 | npm install |
| 12 | npx ts-node src/index.ts |
| 13 | ``` |
| 14 | |
| 15 | **Requirements:** |
| 16 | A `.env` file must be present at the workspace root with: |
| 17 | - `APIFY_API_TOKEN` (Apify account access) |
| 18 | - `GEMINI_API_KEY` (Gemini 3 Flash Preview with Search Grounding) |
| 19 | - `MAX_POSTS=20` (Optional limit) |
| 20 | |
| 21 | ## Optional Native X/Twitter Plugin Inputs |
| 22 | |
| 23 | If the user is running OpenClaw with |
| 24 | [TweetClaw](https://github.com/Xquik-dev/tweetclaw), you may use it as a native |
| 25 | OpenClaw plugin for the discovery stage while keeping the ICP validation stage |
| 26 | unchanged. |
| 27 | |
| 28 | Install it when needed: |
| 29 | |
| 30 | ```bash |
| 31 | openclaw plugins install @xquik/tweetclaw |
| 32 | ``` |
| 33 | |
| 34 | With `XQUIK_API_KEY` configured, use: |
| 35 | |
| 36 | - `explore` to find tweet search, reply search, user lookup, follower export, |
| 37 | monitor, and webhook endpoints |
| 38 | - `tweetclaw` to scrape tweets, search tweets and replies, look up promising |
| 39 | founders or company accounts, export followers, and monitor leads during this |
| 40 | workflow |
| 41 | |
| 42 | If the user is running Hermes Agent with |
| 43 | [Hermes Tweet](https://github.com/Xquik-dev/hermes-tweet), you may use it as a |
| 44 | native X/Twitter plugin for the discovery stage while keeping the ICP validation |
| 45 | stage unchanged. |
| 46 | |
| 47 | Install it when needed: |
| 48 | |
| 49 | ```bash |
| 50 | hermes plugins install Xquik-dev/hermes-tweet --enable |
| 51 | ``` |
| 52 | |
| 53 | With `XQUIK_API_KEY` configured, use: |
| 54 | |
| 55 | - `tweet_explore` to scrape/search tweets and search Twitter/X for GTM, DevRel, |
| 56 | growth, and startup hiring signals |
| 57 | - `tweet_read` to read tweet replies, look up users, and monitor tweets from |
| 58 | promising companies or founders |
| 59 | - `tweet_action` only for read-side exports such as export followers in this |
| 60 | discovery workflow |
| 61 | |
| 62 | Convert the findings into the same candidate shape used by the pipeline, then |
| 63 | run the ICP checklist before ranking leads. Do not post tweets, post replies, |
| 64 | send DMs, or automate X actions without explicit human confirmation. |
| 65 | |
| 66 | ## Outputs |
| 67 | |
| 68 | The script handles two primary JSON files: |
| 69 | 1. `radar-jobs.json`: The initial raw batch of tech jobs identified by the scraper. |
| 70 | 2. `openclaw-icp-jobs.json`: The **final validated file** OpenClaw should ingest, containing only companies that passed the strict web-search evaluation. |
| 71 | |
| 72 | ## References |
| 73 | |
| 74 | For deeper context on how the evaluation works or modifying the pipeline, read these files as needed: |
| 75 | |
| 76 | - **ICP Checklist**: See [references/icp-checklist.md](references/icp-checklist.md) for the exact strict evaluation criteria (Developer-first + $100K minimum funding). |
| 77 | - **Gemini Search Grounding**: The pipeline (`scripts/src/icp-filter.ts`) natively uses Google Search Grounding via the `@google/generative-ai` SDK (`gemini-3-flash-preview` / `gemini-flash-latest`) to look up live funding and product data. |