apply

Solid

Apply to the queued jobs. Use when the user says /apply, "start applying", "run the applier", or asks to submit applications from the queue. Fills each form in the runner's own Chrome window with JEV, page by page, hands what is left to Claude, verifies, and submits only forms that are ready.

AI & Automation 374 stars 68 forks Updated 5 days ago MIT

Install

View on GitHub

Quality Score: 92/100

Stars 20%
86
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# /apply: the application loop The CLI does the whole loop. JEV maps every field, the runner fills the form in its own Chrome window, a headless Claude Code call (Sonnet 5.5, high effort) answers what JEV left open, a form with several pages is walked with its own Next button, and every value is read back from the page before anything is sent. Your job is to run it, read what it reports, and tell the user what was left for them. Run every command from the repo root with `npx jev <command>`. ## One posting the user found themselves `apply <link> --submit` takes a Greenhouse, Lever or Ashby posting link in place of an id: the posting is read from the board, rated, queued at the top and filled like any other. For a link on another board, tell the user the tool reads those three directly and that `discover` picks up the rest. ## Before the loop 1. `doctor`. If it names something missing, fix that first. A missing profile means `/setup`. 2. `status`. If the queue is empty or older than today, run `/discover` first. 3. Ask the user how many to send and whether to submit, unless they already said. Submitting is never the default. ## Rehearse first on a new machine or after a code change `apply --dry --count 5` fills and resolves five forms, records nothing, sends nothing and closes the tabs. Read the output. Every line is one field: its label and the value the page shows. If a value is wrong, fix the profile (`data/profile.json`, including `answers`) or the code before going...

Details

Author
qbeka
Repository
qbeka/jev-job-search
Created
1 months ago
Last Updated
5 days ago
Language
TypeScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Listed

auto-job-apply

Apply to jobs in the user's own Chrome through Claude in Chrome - open each application link, check the job against the user's fit rules, run Simplify's Autofill if installed, fill every remaining field from profile.md, attach the resume, submit only when the user's request for this run says to submit, and log the result to applications.csv. Use when the user gives one or more job or application URLs and asks to apply, autofill, fill out, or submit an application, or asks to set up their job-apply profile.

0 Updated today
antece1
Data & Documents Listed

apply-to-job

Run the entire application pipeline for a specific job from one command — extract the JD, assess fit, tailor the LaTeX resume, render the PDF, draft any free-text answers the form asks for, and prepare the submission for your confirmation. Use whenever the user gives a job URL or JD and wants the end-to-end result rather than a single step. If the user only wants to analyze a JD, check fit, or tailor without rendering, prefer the narrower skills (extract-jd / resume-fit-report / tailor-resume) instead. Orchestrates those skills in order, pauses for review before rendering, and never submits without an explicit yes.

1 Updated 2 months ago
DhruvPrajapati4
Data & Documents Listed

apply

Apply to planned jobs in the person's Chrome: fills each form from their records with the right CV and a fresh letter, submits by APPLY_MODE and records it. Use for 'apply to these jobs', 'send the applications', 'candidati per me', 'başvuru yap'. Stops at codes, CAPTCHAs, passwords, essays.

0 Updated today
cenksimsek1988