agentleFS
amikaiamikai/openings-mcp/.agents/skills/discover-companies/SKILL.md

discover-companies

Skill106 starsChanged 3 months agoMITView on GitHub

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).

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. CodesWhat/careerrat★ 4same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Commit per the roster: convention in CLAUDE.md: one batch, one commit, one PR.

    line 85

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 whose careers URL matches the provider's host shape. The slug comes from that URL, never from guessing the company name.
  • Migration finds — verify-companies audits surface companies that moved ATS; their new host names the provider and slug directly.

A careers URL matching a different supported provider's host shape is still a find — park it in unverified/<other>.yaml rather than mixing rosters in one session.

Candidate to entry

  1. Dedupe first: grep -ri "<name-or-slug>" internal/provider/*/companies.yaml unverified/*.yaml. ats.NewRegistry only requires unique display names and slugs within one adapter's own roster; a hit inside the target provider's file disqualifies or renames the candidate. A hit in a different provider's roster is fine — cross-adapter collisions are allowed and Registry.Resolve disambiguates them by careers URL at runtime, not a curation bug to dodge here. The one exception: when the target adapter cannot render a careers URL for the candidate, its display name is the only disambiguation key left, so that name must collide with no other entry's name or slug anywhere — NewRegistry fails otherwise.
  2. Copy the YAML key shape from the target companies.yaml — every provider names its identifier differently, and workday needs the tenant/instance/site triple from the careers URL, one row per tenant (the adapter dedupes by tenant and serves only the first).
  3. Display name comes from an authoritative source (the company's own site or the board's page title). A slug with an unconfirmed name goes to unverified/<provider>.yaml, not the curated roster.

Verify the batch

  1. Append the batch to companies.yaml, then go run ./cmd/verify-companies --provider <name> — rosters are go:embed'd, so go run picks the additions up. Keep the default timeout; big full-dump boards need it.
  2. Drop confirmed-stale ERRORs; retry transients first (the verify-companies skill's audit steps). zero-job entries are fine — board live, no current openings.
  3. go test ./... — registry tests catch collisions and shape mistakes. A red TestCompanyCollisionReport from a genuine new cross-adapter collision (not a curation mistake) is expected as rosters grow: regenerate cmd/openings-mcp/testdata/company_collisions.txt with go test ./cmd/openings-mcp -run TestCompanyCollisionReport -update and show its diff in the PR.
  4. Commit per the roster: convention in CLAUDE.md: one batch, one commit, one PR.

Common mistakes

  • Probing a guessed slug and accepting any 200 — a wrong slug can be a different company's live board. The board's company name must match the candidate.
  • Promoting a slug straight into companies.yaml with the slug as its display name — that's what unverified/ quarantines.
  • Dorking the API host (api.lever.co, api.ashbyhq.com) and finding nothing.
  • Adding several rows for one workday tenant; only the first is served.
  • Sourcing across providers in one session and batching multiple rosters into one PR.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.