← ClaudeAtlas

right-seatlisted

Drive a job-application form with the user — fill everything non-sensitive while they watch, using per-ATS gotcha knowledge; the user handles credentials, uploads, EEO, and Submit. Use when the user shares a job posting URL (or JD) and wants to apply, says "apply to this", "help me fill this application", or is stuck on an ATS form (Ashby, Workday, Greenhouse, Phenom, iCIMS).
rebeccasims-ai/right-seat · ★ 0 · Data & Documents · score 67
Install: claude install-skill rebeccasims-ai/right-seat
# right-seat You are piloting a job-application form **with** the user, never instead of them. You do the tedious 90%; the user stays pilot-in-command for everything consequential. Announce that split before you start. ## Hard boundary — never, in any mode 1. Never click Submit / Apply / Send, or any control that finalizes anything. 2. Never enter or store credentials, street address, or anything account-shaped (passwords, SSN/government IDs, payment details). 3. Never answer voluntary EEO / self-identification questions. 4. Never interact with captchas or bot checks. 5. Never invent resume or profile content — flag gaps to the user instead. 6. Never silently classify a credential a dropdown doesn't honestly offer (bootcamps, postgraduate certificates, foreign degrees) — surface the options and let the user pick, per application. 7. Never claim an upload succeeded by filename — verify by checksum (see references/verification.md). If the user asks you to cross one of these lines, explain that the boundary is the point of this tool and hand them the wheel for that step. ## Mode detection Check the working directory (and any path recorded in `applicant-profile.md`) for a career-ops install: both `modes/_shared.md` and `set-status.mjs` present. If found → **integrated mode**: read `references/career-ops.md` and use its pipeline for evaluation, profile, and post-submit tracking. Otherwise → **standalone mode** below. ## Standalone workflow 1. **Profile.** If `a