メニュー
Track and view the job-application pipeline (saved, applied, interviewing, offer). Use when the user wants to save a job, update its status, add a note, or see their pipeline, e.g. "/jobfinder:track applied adzuna:12345" or "/jobfinder:track list".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Apply to a job the hybrid way — auto-draft an EMAIL application (into the user's Gmail drafts, resume attached) when the ad accepts email, or hand back a ready-to-submit pack (direct link + cover letter on the clipboard + prepared screening answers) for form-only jobs. Use for "/jobfinder:apply adzuna:12345" or "apply to this job for me".
Save recurring job searches and surface only newly-posted matches on demand. Use when the user wants a saved search / job alert, e.g. "/jobfinder:alerts save devops devops engineer Brisbane" or "/jobfinder:alerts run".
Ingest the user's resume, CV, and other career documents to build a structured profile that grounds all job matching and application tailoring. Use when the user wants to upload or update their resume/CV, or run "/jobfinder:profile <files>".
Search Australian job listings (Adzuna + Workforce Australia) and rank them against the user's profile. Use when the user wants to find jobs, e.g. "/jobfinder:search devops engineer Brisbane" or "find me remote data roles".
One-time setup for the jobfinder plugin — configure Adzuna API credentials and verify each Australian job source is reachable. Run this first.
Draft a tailored cover letter and resume-tweak suggestions for a specific job listing, grounded in the user's profile. Use when the user wants to apply to or tailor an application for a saved job, e.g. "/jobfinder:tailor adzuna:12345".
| name | track |
| description | Track and view the job-application pipeline (saved, applied, interviewing, offer). Use when the user wants to save a job, update its status, add a note, or see their pipeline, e.g. "/jobfinder:track applied adzuna:12345" or "/jobfinder:track list". |
Manage the application pipeline. $ARGUMENTS is a free-text instruction —
map it to the right tracker.py subcommand.
Run uv run "${CLAUDE_PLUGIN_ROOT}/scripts/tracker.py" <subcommand>:
| User intent | Subcommand |
|---|---|
| save / bookmark a job | save <id> |
| mark applied | applied <id> |
| moving to interview | interviewing <id> |
| got an offer | offer <id> |
| rejected / passed | rejected <id> |
| hide it | archived <id> |
| add a note / reminder | note <id> <text...> |
| show one job + history | show <id> |
| see the pipeline | list (add --status <status> to filter) |
Valid statuses: seen, saved, applied, interviewing, offer,
rejected, archived.
For list, render the results grouped by stage in a sensible order
(saved → applied → interviewing → offer, with rejected/archived last). For each
job show title, company, AU location, AUD salary, id, and days since last
update.
Add gentle, useful nudges based on updated_at, e.g. "applied 14 days ago —
consider a follow-up" or "interview logged 3 days ago — send a thank-you note?".
Keep it brief; don't badger.
If a job id isn't found, the user probably needs to /jobfinder:search for it
first (searching stores listings automatically), or you can add it with
tracker.py add.
