h1b-sponsor

1# H-1B sponsor check skill
2 
3Use this plugin during `oferta` evaluations of US roles to attach a factual sponsorship signal to Block G.
4 
5## When to run this check
6 
7Run it when any one of these is true:
8 
9- `config/profile.yml` has `location.country == "US"`.
10- The JD lists a US work location, remote-US, or a US-based employing entity.
11- The user asks explicitly about sponsorship for this role.
12 
13If none of those apply, skip the check silently. Do not run it on non-US roles just because the parent company is US-headquartered.
14 
15## If there is no index installed
16 
17The check reads a local copy of the DOL data, so the question never leaves the user's machine. When that index is missing and no `H1B_API_BASE` is configured, the CLI exits non-zero and its `error` field names `install-h1b-index.mjs`. No lookup happened and nothing was sent anywhere.
18 
19Installing downloads about 8 MiB from GitHub. That is an outward action in the same sense minting a key is, so ask first and run it only after the user agrees in the conversation:
20 
21```bash
22node plugins/h1b-sponsor/install-h1b-index.mjs
23```
24 
25Do not install on your own initiative to make a failing check succeed, and do not install inside an unattended scan or a batch run. Without the user's agreement the sponsorship check is simply inconclusive for that evaluation: skip the Block G bullet and carry on. The same applies to `--force`, which replaces an installed index with a newer release.
26 
27## How to call it
28 
29From the agent shell:
30 
31```bash
32…