job-triagelisted

# Job Triage Raw postings in, a short-list of two or three worth real effort out — plus an auditable record of what got screened out and why. This skill does not scrape. Bring it postings from wherever you get them: an export, a board, a pasted list, an ATS API. It does the judging. ## Load first - `profile.yml` — target archetypes, exclusions, location rule, granted exceptions - `applications.tsv` — so nothing already tracked resurfaces - A dedup history file, if you keep one ## Steps ### 1. Coarse filter Drop, before reading anything closely: - Seniority mismatches. A search for apprentice roles should never surface "Senior Staff X" - Excluded functions from `profile.yml` - Locations outside the commutable zone, unless `profile.yml` grants that role an exception - Anything already in `applications.tsv` at any status If results look suspiciously global, your location filter has broken. Check it before blaming the source. ### 2. The requirements-block screen For each survivor, fetch the posting and read the **requirements block only**: "Requirements", "Your profile", "Qualifications", "Profil recherché", "Type d'études", "À propos de toi". Apply `jd-analyser`'s hard gates: | Gate | Kill signal in the requirements block | |---|---| | Degree field | Names a field the candidate does not hold | | Specialised school | Names a school type they are not in, as an exclusive | | Stated language | "fluent French", "proficiency in X", "bilingual" above their level | | Hard t