discover-companieslisted

Use when growing one ATS provider's curated roster with net-new companies — "find more <provider> companies", "add <industry/region/theme> companies to <provider>", or a roster is thin for a segment. Input is one existing roster-based provider. Not for pruning or promoting entries already on file (verify-companies) or adding a new ATS platform (integrate-new-provider).
amikai/openings-mcp · ★ 92 · AI & Automation · score 80

Install: claude install-skill amikai/openings-mcp

# Discover Companies ## Overview Given one roster-based provider, source companies hosted on that ATS that no roster has yet, confirm each against the live adapter path, and land them in `internal/provider/<provider>/companies.yaml`. This skill covers the sourcing; verification and promotion mechanics are the verify-companies skill, and the roster commit convention is in CLAUDE.md. Scope a session to one provider — rosters land one per PR. The providers in scope are the `--provider` values of `cmd/verify-companies` (`providerOrder`). SmartRecruiters keeps a roster too but has no adapter yet; spot-check its candidates with `go run ./cmd/smartrecruiters --company <id> search` instead. ## Sourcing channels Work from the provider's public board-host shape — the entry for the provider in `careersHostPatternsByAdapter` (`internal/ats/registry.go`). Mix channels; each one alone dries up: - **Site dorks** — WebSearch `site:<board host> <theme keywords>` (e.g. `site:jobs.lever.co fintech`, `site:job-boards.greenhouse.io robotics` — for greenhouse the legacy `boards.greenhouse.io` host is indexed too and redirects). Dork the public board host, never the API host — search engines index board pages, not API responses. Vary keywords by industry, region, and role; page past the first results. - **Theme-first probing** — start from a company list (industry roundups, accelerator batches, "companies using <ATS>" articles), websearch `<company> careers`, and keep the ones