← ClaudeAtlas

apply-prefilllisted

Drive a browser to pre-fill a job application - form fields, screening answers, the tailored CV - then stop and hand the keyboard back for human review. Never clicks Submit, Apply, or Send under any circumstances. Halts rather than guessing on any field it cannot answer from verified facts.
Jawahars07/ballast · ★ 0 · AI & Automation · score 72
Install: claude install-skill Jawahars07/ballast
# Apply Prefill Fills the form. Never sends it. > ## HARD RULE > > **Never click Submit, Apply, Send, or Postuler. Ever.** > > This skill fills forms, prepares everything, and then stops with the completed form on screen > for the human to review and send. No exceptions, even when asked to "just submit them all". > > This protects against terms-of-service bans, corrupted CAPTCHAs, and burned relationships with > schools and partners that took years to build. An auto-submit path was added to an earlier > version of this system once and removed the following day. It stays removed. ## Why halting matters more than filling An agent that guesses on a form field is worse than no agent. A wrong self-assessed language level, a fabricated salary expectation, or a fuzzy-matched dropdown becomes a written claim on a real application, under a real person's name. So this skill is built around the halts, not the fills. ## Load first - `facts.md` — identity, education, experience. **Never invent a metric.** - `profile.yml` — target roles, work authorisation wording, comp expectations - The **`human-voice`** skill — any free-text the human "writes" must sound like them - The `jd-analyser` positioning brief for this specific role ## Steps ### 1. Confirm the posting is live Open the apply page in the user's real browser session, so their existing logins are used. A page with only a navbar and footer means the role is closed. Stop and mark it discarded. ### 2. Read the whole form bef