← ClaudeAtlas

competlab-hiring-signalslisted

Probes hiring + GTM-motion signals for each monitored competitor via public ATS APIs (Ashby, Greenhouse, Lever, Workable) + LinkedIn unauth fallback + Perplexity for exec transitions. Three-condition feasibility: (1) LinkedIn employer-brand presence, (2) ATS adoption (Ashby/Greenhouse/Lever), (3) vendor-name uniqueness. Use when the user asks "competitor hiring", "is X expanding sales motion", "competitor headcount trend", "GTM motion shift signals", "exec transitions". Most reliable for Series-B+ private + public vendors; less for bootstrapped operators without public ATS. Requires CompetLab MCP + Bash + Perplexity + URL verification.
competlab/competlab-ci-skills · ★ 0 · Data & Documents · score 76
Install: claude install-skill competlab/competlab-ci-skills
# Hiring & GTM Intelligence You probe hiring signals across public ATS APIs + LinkedIn unauth + Perplexity to infer GTM-motion shifts, headcount velocity, executive transitions. ## Pre-scan vendor-profile filter (Step -1, banked from a real-world validation run) **Before running ATS probes, check if the vendor is even an ATS candidate.** If the vendor profile shows ANY of these → skip ATS probes entirely (saves 30-60s per vendor): - **Employee count < 10** (per any prior knowledge or LinkedIn unauth quick-check) — indie operator, no public ATS likely - **Bootstrapped category with categorical no-ATS pattern** detected from sibling skills: - Hospitality / vacation rental tools - Indie hosting tools - Solo-founder AI tools - **Vendor profile indicates founding within last 12 months** — too young for ATS adoption For skipped vendors, output: "ATS probe skipped — vendor profile (indie/small/young) indicates ATS-data unlikely; founder-channel monitoring required if signal needed." Saves time + token budget on guaranteed-null probes. Surfaced from a real-world validation run: 9 of 9 hospitality vendors had no ATS, but the orchestrator burned ~30-90s × 9 vendors × 4 ATS platforms anyway. ## Three-condition feasibility probe (Step 0) For each vendor NOT pre-filtered out at Step -1, check which of these apply: 1. **LinkedIn employer-brand presence** — Series-B+ private + public almost always have it; bootstrapped operators often don't 2. **ATS adoption** — Ashby (api.ash