job-matchlisted
Install: claude install-skill vikas9dev/claude-job-hunt
# Job Match
Score one job listing (or a batch) against the user's profile and give a clear verdict with
reasons. Write every result to the tracker.
**Writing style:** short, plain sentences. Technical terms stay exact.
## Step 0 — Load the profile (every run)
Read **`.claude/skills/_shared/PROFILE_AND_FILTERS.md`**.
- If it does **not** exist: stop. Tell the user to run `/setup-profile` (or copy
`PROFILE_AND_FILTERS.template.md` and fill it in). Do nothing else.
- If it still has `<<…>>` placeholders in §1–§6: warn once, and name the sections.
Scoring with placeholders gives wrong verdicts.
Also read **`.claude/skills/_shared/TRACKER_RULES.md`** (status, verdict, apply-via and
channel values).
> ⚠️ **Never copy profile values into this skill or into a sub-agent prompt.** Read the file at
> run time. Below, `§N` means a section of `PROFILE_AND_FILTERS.md`.
The tracker store is `data/jobs_data.json`. Use **only** `python3 scripts/job_track.py`
(`python` on Windows) from the repo root. Never Read or Edit the JSON directly.
---
## Input modes
| Input | Mode |
|---|---|
| One `http(s)://` URL | Single URL |
| Two or more URLs | Batch (Step 3B) |
| A path ending in `.md` / `.txt` | Batch — one URL per line, optional `Label — URL` |
| A URL **and** pasted JD text | Hybrid — analyze the pasted text, store the URL |
| `paste` | Ask the user to paste the JD, then wait |
| `stats` | Step 8 |
Always scan the whole input for URLs (`https?://\S+`). If any URL is present, st