04-theirstack-jobs
SolidPulls open job postings from the TheirStack API and turns them into structured hiring signals - open roles per domain, titles, seniority, posting dates, hiring team, plus free firmographics (headcount, funding stage, industry). Step 04 (signals) of the API-first GTM chain, and the discovery entry for hiring-defined ICPs. Use when the user wants hiring signals, open reqs, job postings, "who is hiring", "which of these companies are hiring X", "find companies hiring Y right now", open-role checks on a domain list or records.jsonl, or anything TheirStack. Sizing counts bound every pull before spend - free without company filters, ~1 credit against a domain list - then 1 credit per job returned. For people who already joined - recent hires, headcount growth, funding rounds - use 04-crustdata-signals; for scoring and campaign angles, hand the records to 05-signal-builder.
Install
Quality Score: 81/100
Skill Content
Details
- Author
- Zevenue
- Repository
- Zevenue/headless-gtm
- Created
- 3 months ago
- Last Updated
- today
- Language
- Python
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
04-crustdata-signals
Enriches company domains with structured signals from CrustData - funding rounds, headcount growth, department growth, and recent hires. Use when the user wants to pull company signals, enrich domains with funding/growth/hiring data, check who recently joined a company, find new hires at a domain, get headcount trends, or anything involving CrustData enrichment. Also triggers on: "run crustdata signals", "enrich these domains", "pull funding data", "who joined recently", "headcount growth for these companies", "department growth", "recent hires at", "crustdata enrich".
job-scout
Discover and score open roles against the user's rubric. Sweeps ATS APIs, drops out-of-band roles before scoring, sorts survivors into apply-first / worth-a-look / skipped. Runs scheduled (daily digest) or on demand.
05-signal-builder
Rank a prospect's outbound signals and pick the campaign approach (PQS / PVP / Pain-led) - the judgment layer (step 05) of the API-first GTM chain. Takes scraped website markdown (03-firecrawl-research), structured vendor signals like funding / headcount / recent hires (04-crustdata-signals), or just a URL or pasted content, and emits ranked provenance-backed signals: the exact quotable sentence, source URL, 1-10 score, and recommended approach. Use whenever the user wants to score, rank, or prioritize prospects or accounts, decide outreach angles, or asks "which of these companies should we email first", "what's the angle for this account", "rank these signals", "score these prospects", "turn this scrape into campaign angles", or "run signal-builder" - and whenever a records.jsonl or enrichment output is ready for judgment before writing copy. Scoring and interpretation live here; scraping belongs to firecrawl-research, vendor signal pulls to crustdata-signals, email finding to resolution.