decide-apply-or-skip

decide-apply-or-skip

You apply ONLY the two skip rules from spec §9.1. Skill mismatch and unanswerable screening are NOT skip rules at this stage.

Input

• profile_text: profile.md contents.
• criteria_text: queries/<query_id>/criteria.md contents (may include salary override).
• job_extract: dict with title, company, location, salary_posted, work_auth_required, description, apply_type.

Skip rules (the only ones)

Rule 1: Salary out of range

Skip with skipped_salary if and only if:

• job_extract.salary_posted is non-null AND
• The maximum of the parsed range, in the same currency as the user's minimum, is unambiguously below the user's minimum.

If currency conversion is uncertain, OR the format is unclear, OR only one number is posted (single value, not a range): treat as NOT a skip. Apply anyway.

Rule 2: Location / work auth incompatible

Skip with skipped_location if and only if:

• The job requires a work authorization the profile cannot satisfy (e.g., "US citizens only, W2 only, no sponsorship" + profile is non-US contractor), OR
• The job is on-site at a location the profile excludes (e.g., on-site Tokyo + profile says "remote only outside Argentina").

When in doubt, APPLY. The intent is to skip only when the gap is unambiguous and fully reading the description confirms it.

Steps

1. Read profile (focus on Preferencias, FAQ).
2. Read criteria (note any salary override for this query).
3. Apply Rule 1, then Rule 2.
4. If neither matches, decision = APPLY.

Output

Return:

{
  "decision": "APPLY" | "SKIP",
  "skip_status": "skipped_salary" | "skipped_location" | null,
  "reason": "<one-line>"
}

For APPLY, skip_status = null; the reason summarizes the match (1–2 strengths the agent saw + a note on any uncertainty).

What is NOT a skip rule

• Partial skill match → APPLY.
• Different stack → APPLY.
• Possibly-low engagement signals (small company, vague description) → APPLY.
• Ambiguous salary → APPLY.

These come from spec §9.1 and override any other instinct you might have.