seekter-initlisted

# /seekter-init — build the candidate profile The goal is a complete `profile/profile.md` (from `templates/profile.md`) and `profile/search.json` (from `templates/search.example.json`). Every other Seekter skill reads only these files, so nothing may be guessed here: a value the user didn't give stays `ASK`. ## Rules for the interview - **One question per message.** Short, plain, in the user's language. Offer choices with the question tool when the answer is one of a few options; free text otherwise. - **Draft, then confirm.** If a CV or LinkedIn URL is available, read it first and turn questions into confirmations ("Your CV says 8 years in this field. Correct?"). Never write a value from the CV without the user confirming it. - **Skippable.** "Skip" or "later" writes `ASK` and moves on. Sensitive items (birth date, ethnicity, disability, gender, salary history) default to "prefer not to say" unless the user volunteers a value. - **Resumable.** After each answered section, save progress to `profile/.init-state.json` (`{"done": ["identity", ...], "answers": {...}}`) and write what's known into `profile/profile.md`. On restart, read the state file, say where you're resuming, and continue. - **Explain once why** at the start: "I'll ask about 40 short questions in 9 groups. Everything stays in `profile/`, which git ignores." - Don't ask what you can derive: timezone from city, ASCII fallback from name, E.164 phone from local number + country, LinkedIn geoId from country (table