← ClaudeAtlas

jobmatchlisted

Daily job hunt. Search all platforms for US jobs, strictly evaluate the candidate's real abilities (a facts ledger) against each full JD ignoring seniority labels, and deliver EVERY genuinely applyable posting (no upper cap; 10 is a floor, not a target) with fact-grounded match evidence. Accepts a freshness window argument such as 24h, 7d, 30d, or all; defaults to the gap since the last run. Use when the user invokes /jobmatch, asks to find jobs to apply to today or this week, or asks whether a specific posting matches their abilities.
UrBaneee/job-match-skill · ★ 1 · AI & Automation · score 64
Install: claude install-skill UrBaneee/job-match-skill
# jobmatch: daily strict-match job hunt Find **every** US job posting the candidate can genuinely do, judged **only** on ability-vs-JD evidence. Titles and seniority words carry zero weight; unverifiable claims about abilities are forbidden. **No upper cap on results.** The candidate is job-hunting and wants a shot at every posting they qualify for. Present *all* jobs that clear the qualify bar (Tier S and Tier A alike). 10 is the minimum to aim for, never a ceiling. If 25 qualify, report 25. The only reasons a qualifying job is left out are the strict rubric (a required item missing, or a hard exclusion), never "we already have enough" or "this family is over-represented today." Strictness gates *quality*, not *quantity*. ## Time window (how far back to look) The window is an argument the user passes when invoking the skill, e.g. `/jobmatch 24h`. | Argument | Window | Use when | |---|---|---| | `24h` or `1d` | last 24 hours | running it daily; you only want what's brand new | | `3d` | last 3 days | checking every few days | | `7d` or `1w` | last 7 days | the common case, a weekly sweep | | `14d` / `30d` | 2 / 4 weeks | catching up after a break | | `90d` | 3 months | the widest useful net | | `all` | no window | exhaustive audit; ghost-job floor below still applies | **Default when no argument is given**: infer it from `seen.tsv`. Use the gap since the last recorded run, so a daily user gets 24h and someone returning after 8 days gets 8d. If `seen.tsv` is missing or em