/apply

name: apply
description: Assisted job-application filler. Given a job posting URL, open it in a browser via Playwright, extract the JD and company, score resume-to-JD fit, fill every form field from the user's profile and answer memory, flag anything uncertain, and STOP before Submit for human review. After the human submits, capture their edits back into answer memory. Use for /apply or whenever the user wants help applying to a specific job.

Apply (assisted, human owns Submit)

Fill one job application from a URL. **You never click Submit.** You fill, flag, and hand back a browser tab parked at the Submit button for the human to review, edit, and send.

Data lives in `~/.dear-hiring-manager/`: `profile.md`, `answers.md`, `applications.md`, `resume.*`.

Preconditions

• If `~/.dear-hiring-manager/profile.md` is missing, stop and tell the user to run

`/dear-hiring-manager:onboard` first.

Procedure

1. **Open the posting.** Use the Playwright MCP tools to navigate to the URL. Take a page snapshot (accessibility tree / DOM) — do not rely on vision unless the DOM is unusable. **If the URL redirects to the board root or an error page (e.g. `?error=true`, only a job list / "Back to jobs", no job title or application form), the posting is closed or expired — stop and tell the user; do not proceed.**

2. **Extract JD + company.** Pull role title, company, location, and the job description. Detect the ATS from the URL/DOM (greenhouse, lever, ashby, workday, other). Append a row to `applications.md` (create from `${CLAUDE_PLUGIN_ROOT}/templates/applications.template.md` if missing) with `status=in-progress` (fit is filled in the next step; status advances as the run proceeds): `date | company | role | url | ats | fit | status | flags`.

3. **Score fit — FIRST FILTER (hard gate, nothing filled before it passes).** Read `resume.*` and the JD, give a 0–100 fit score with a 2–3 line rationale (matched strengths, gaps), and record it in the tracker row. Read the user's **Minimum fit score to apply** from `profile.md` (default 50 if unset). **If the score is below that threshold — or there's a hard-eligibility blocker (the role's country needs work authorization the user lacks) — STOP here:** set the tracker row `status=skipped` (reason: low-fit or ineligible), report the score, the threshold, and why, and do not fill the form. The user can override by replying "apply anyway" or lowering their threshold.

3b. **Account / login wall (Workday, iCIMS, SuccessFactors — only after the fit-gate passes; never create an account for a role you won't apply to).** If applying requires sign-in / create-account before the form:

• **Already signed in** (persistent session) → continue.
• **Saved creds exist** → fetch this portal's password from the macOS Keychain

(`security find-generic-password -s dear-hiring-manager -a "<domain>|<email>" -w`) and log in with the profile email + that password.

• **New portal** → generate a strong **unique** password (never reuse across portals), fill

create-account with the profile email + that password, submit, then **save it to the Keychain** (`security add-generic-password -U -s dear-hiring-manager -a "<domain>|<email>" -w "<password>"`). Passwords live **only** in the Keychain — never in `profile.md` / `answers.md` / any file.

• **Email verification** required → set tracker `status=blocked`, pause and ask the human to click the

verify link in their inbox (or, if a job-inbox integration is configured, open + click it), then resume.

• **CAPTCHA / 2FA on signup** → do not solve; set `blocked`, hand to the human, resume after.

Then continue to the form.

4. **Map every field — fill or flag, never silently skip.** Every required field must end up either filled or explicitly flagged; a blank required field is acceptable only when it is flagged. **Paginated wizards (Workday-style: My Information → My Experience → Questions → Self-Identify → Review):** run this fill pass on **each page**, click **Next/Continue** to advance, re-snapshot after every page, and only stop at the FINAL Submit (step 7) — **never click an intermediate Submit**. If the portal offers **autofill-from-resume**, use it first, then complete/fix the parsed fields. For each field:

• **Profile-backed** (name, contact, salary): fill from `profile.md`.
• **Work authorization (per role country)**: answer for the ROLE's country — do not paste the

profile's raw yes/no. E.g. authorized in NL+EU but the role is in the US → "authorized: No", "sponsorship: Yes". Flag whenever the role country is outside the user's authorized regions.

• **Legal attestations** (non-compete, felony, illegal activity, accommodation, previously-employed,

age): fill **only** from a confirmed, non-blank `profile.md` value. If blank/unconfirmed, **flag and leave for the human** — never auto-attest a legal answer from a default.

• **Voluntary EEO** (gender, race/ethnicity, veteran, disability): use `profile.md` if set; if

blank, select "prefer not to answer" / "decline to self-identify". Never flag, never block on these.

• **Open-ended / unseen** (e.g. "Why this company?", custom screening): search `answers.md` for a

matching prior Q&A. Prefer the newest, most company/role-specific match.

• Match found → adapt and fill.
• No match → write a best-guess grounded in resume + profile, fill it, and **flag** it.

Run **every** open-ended answer you write or adapt through the **`humanize`** skill — sound like the candidate, no AI tells, no em/en-dashes, no parenthetical asides.

• **File uploads (resume/CV, cover letter)**: Playwright MCP sandboxes file reads to the workspace

root. Copy `~/.dear-hiring-manager/resume.*` into `.playwright-mcp/` (gitignored), upload from there, then delete the staged copy. Do NOT enable `--allow-unrestricted-file-access` —