profile

name	profile
description	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>".

jobfinder: profile

Turn the user's career documents into the grounding profile that every other jobfinder skill loads into context. $ARGUMENTS holds the file path(s).

Steps

1. Extract text. Run (pass every file the user gave):

   uv run "${CLAUDE_PLUGIN_ROOT}/scripts/ingest.py" $ARGUMENTS
   

   The script prints each document's text under an === filename === header and saves a copy to ~/.jobfinder/profile/raw/. If a file errors (scanned/image PDF, .doc, password-protected), relay the script's guidance and continue with the files that worked.

   If the user gave no files, list what's already in ~/.jobfinder/profile/raw/ and ask which document to add, or offer to let them describe their background in chat instead.

2. Merge, don't clobber. If ~/.jobfinder/profile/profile.json already exists, Read it first and merge the new documents into it (add new roles, skills, updated preferences) rather than replacing it.

3. Write profile.json to ~/.jobfinder/profile/profile.json — structured facts you'll reuse:

   • target_roles, seniority
   • skills (each with brief evidence from the documents)
   • experience (roles, employers, dates, key achievements — quantified where the source quantifies them)
   • locations (preferred Australian locations; note remote/hybrid appetite)
   • salary_expectation_aud (min, ideal)
   • work_rights (e.g. citizen / PR / visa — only what the documents state)
   • constraints and red_lines (things to avoid)

4. Write profile.md to ~/.jobfinder/profile/profile.md — a concise (~1500 token) context card that other skills load. It is the grounding, so keep it dense and factual: target roles, top skills with one-line evidence, seniority, Australian location preferences, salary expectation (AUD), work rights, and hard constraints.

5. Confirm. Show the user the profile.md card and ask them to correct anything wrong or missing. Only record facts supported by the documents or the user — never invent experience, credentials, or work rights.

6. Next step. Point them to /jobfinder:search <what you're looking for>.