← ClaudeAtlas

apply-draftlisted

Start (but never submit) job applications for roles the user has selected and tailored a CV for — fills the base application form on LinkedIn Easy Apply or the company's ATS, uploads the tailored CV, and stops at the final review step for the user to submit themselves. Use when the user runs /apply-draft or asks to start applications for selected jobs.
robbiehaynes/job-search · ★ 0 · AI & Automation · score 62
Install: claude install-skill robbiehaynes/job-search
# apply-draft Drafts applications for roles that are `selected: true` **and** already have a tailored CV (`cvPath` set by `/tailor-cv`) in the **Role Pipeline** artifact's `jobs` database. This is Phase 3, the last and highest-stakes phase: it enters the user's real data into real employer/ATS forms. **It must never click the final Submit/Apply button under any circumstances — the user submits every application themselves.** ## Hard rules (never violate these) 1. **Never click Submit / Submit application / Apply now / any final, irreversible action control.** Stop one step before it, every time, no matter how many steps preceded it or how confident the fill looks. 2. **Never create an account, never enter a password, never fill a "create password" field.** If a site requires signing up or logging in to apply, stop that job immediately, record it as needing an account, and move on — per the user's standing instruction, they create their own accounts. 3. **Never attempt to solve or bypass a CAPTCHA or bot-check.** Stop that job, record it, move on. 4. **Only use `answer-sheet.json` (this directory) for personal-data fields.** Never invent an employer, job title, visa category, or number not present in it. If a field doesn't clearly map to something in the answer sheet, leave it blank/skip and note it for the user rather than guessing. 5. **Get explicit go-ahead from the user before touching any live site**, every run (see Step 1) — this is standing per-run consent, not a one