coforce-apply: Skill for Claude Code

Apply — Chrome-backed job application

Input: a job posting / application URL (from args). Expect a non-trivial form: multi-step wizard, custom widgets, an ATS (Workday, Greenhouse, Lever, Ashby…), or login walls.

Setup (first run, answers persist in ~/.coforce/config.json)

Before the first application, ask ONCE and merge these keys into the flat ~/.coforce/config.json (setup owns the rest of that file — never overwrite it with just these):

{
  "email": "[email protected]",          // account email for ATS registrations
  "autoRegister": true,               // may I create ATS accounts for you?
  "mailboxAccess": "browser | paste", // how to fetch verification codes
  "resumePdf": "path/to/resume.pdf",
  "headlessApply": false              // explicit consent; setup manages this
}

Subsequent runs read this file and only ask about gaps.

This skill is the operator in the operator contract (docs/OPERATOR.md in the CoForce repo): inputs are job + profile + resume + intent, progress is reported as COFORCE_STATUS sentinels, and the iron laws (never cross the confirmation gate, never fabricate screening answers, instructions.md overrides everything) bind every run.

Preconditions

1. Read ~/.coforce/instructions.md — standing user instructions (never-apply companies, preferences). It overrides everything below; a never-apply company means stop and tell the user, not apply anyway.
2. Read ~/.coforce/profile.json. Missing → run the profile skill's init first; don't guess values.
3. Read ~/.coforce/config.json — canonical user intent plus runtime config (workAuthorization, needsSponsorship, work mode, locations, and the Setup answers above). Screening answers about visa/sponsorship come from here, never invented. Missing (and no legacy apply-config.json / preferences.json for the loader to fold in) → run Setup above. Batch any remaining per-job questions up front; don't drip.

Flow

1. Initialize Claude in Chrome from inside this skill (--chrome or /chrome) and open the URL in visible Chrome. Do not substitute the in-app Browser, Computer Use, or a second Playwright runtime for this workflow. If Chrome is unavailable, stop and report the setup/connection blocker.
2. Navigate to the actual application form (click "Apply" through interstitials). If the ATS demands an account (Workday, iCIMS, SuccessFactors…) and autoRegister is true, register one — see Account registration below.
3. Fill every field mappable from the profile: contact info, links, education, experience. Upload the resume PDF where a file input exists. Resume resolution: a campaign resume for this job wins; otherwise, if the user didn't hand over a specific PDF, run the tailor skill against this JD first and upload its ~/.coforce/out/resume-<company>-<role>.pdf. The static resumePdf in config.json is the last resort, not the default.
4. Free-text questions ("why us", cover letter): draft 2–4 sentences from the profile tailored to the posting — factual, no invented experience. Check ~/.coforce/research/<company>.json first (company-research cache; schema in the interview skill, 30-day TTL) for a verified company angle to ground the "why us" in; a cache hit is a lead, so re-check any specific claim against its recorded source URL before it lands in an answer. Show drafts to the user before submitting if they're required fields.
5. Stop before the final submit and show a summary of what was entered. Submit only after the user confirms. Submission is irreversible.
6. Report the outcome (confirmation page / email signal), record it in the local tracker (~/.coforce/applications.json, per the tracker skill — add or update the entry with the final status), then serve/refresh the board per the tracker skill and open it so the user sees the updated state without asking.