- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add qbeka/jev-job-search --skill setup -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add qbeka/jev-job-search --skill setup -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add qbeka/jev-job-search --skill setup -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add qbeka/jev-job-search --skill setup -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/qbeka/jev-job-search/tree/HEAD/.claude/skills/setupFrom the publisher
The user should need to do four things: give you their resume, answer your questions, paste one key into a file, and say "go". You do everything else.
Run every command from the repo root. After each step run
npx jev doctor --json. It lists what is in place and names the
next thing to do, so you never have to guess where you are. If the user
stops halfway and comes back, start from what doctor says.
node_modules is missing, run npm install.npx jev doctor. Fix what it names, in order:
ANTHROPIC_API_KEY to .env and the
commands use the API instead.)Look in documents/ first. Besides resume.pdf, a user may have put past
material there for you to read: old resumes, a LinkedIn profile export as
PDF, transcripts, past applications, a portfolio page saved as PDF. Read
every PDF and text file there (the Read tool opens PDFs). Each is a source
for the profile in step 3: a bullet, a date, a project, a skill that the
current resume leaves out. Nothing personal in documents/ is ever
committed; the folder is git-ignored apart from its README. Re-running
/setup after more files land there is safe: it adds, it does not
overwrite what the user confirmed.
documents/resume.pdf.Build data/profile.json in the shape of data/profile.example.json.
The schema is src/profile/schema.ts.
summary (three or four sentences: who they are, what they want,
where, when) and facts (one line per claim, every number exact, copied
from the resume or said by the user).answers, the standing answers, from part G of the questions.doctor again. A schema error names the field to fix.Rules for this step:
resume.path is the absolute path of documents/resume.pdf.data/voice.md to data/voice.local.md.data/bank.json in the shape of data/bank.example.json: one
starting draft per common question, from the user's own facts. Keep the
text in braces where an answer depends on the company.data/voice.local.md and the drafts until it does. One or two rounds is
enough.JEV is the only part of this tool the user is billed for. Tell them the numbers before they pay: about 6 cents each time the tool finds jobs, and about 1 cent for every 10 applications. Five dollars of credit lasts for months.
cp .env.example .env, then open -e .env so the file opens in a
text editor.TYPESAFE_API_KEY=, or an
OpenRouter key after OPENROUTER_API_KEY=, save, and tell you when it
is done.npx jev doctor --online. It makes one tiny JEV call and
one tiny Claude call to prove both work.Never ask the user to paste the key into the chat, and never print it. If they paste it into the chat anyway, tell them to delete that key where they made it (console.typesafe.ai/keys or openrouter.ai/keys) and create a new one, because a key in a chat is exposed.
Run npx jev discover. It takes about a minute. Show the top 15
as a short table: score, company, role, location, date posted. Say how many
jobs are queued and name the main reasons jobs were skipped
(npx jev status).
If the user wants other locations or kinds of roles than the ranking
prefers, the settings are in src/config.ts (LOCATION_MULTIPLIER,
FIT_WEIGHTS, DISCOVER).
npx jev apply --dry --count 3. A Chrome window opens,
three forms are filled, nothing is sent, and the tabs close.answers. Then rehearse again. Do not move on until
the user says the answers are right.Tell the user one thing before the first rehearsal: some job boards save a form as it is typed, so a rehearsal there leaves an unsent draft on that board. It is not an application and the employer is not told.
Setup ends with a real application filled and waiting, not with a list of
commands. Run npx jev apply --count 1 on the best job in the queue that
is on Greenhouse, Lever or Ashby. Without --submit the form is filled,
checked and left open in the tool's Chrome window.
Tell them to look at that window. Read the answers back to them, name
anything the tool held, and ask: "Send this one?" Only when they say yes,
run npx jev submit <id>. Then show the row in npx jev log.
That is the whole loop. Say so in one sentence, then stop asking questions.
Do not list commands. Say only:
/apply sends more: they say how many./report is the dashboard: what was sent, what needs them, and the
switch for a daily run./status says where things stand at any time.Mention these once, and only when they apply. Do not set any of them up during setup:
npx jev status
lists "workday" among the skip reasons), say that Workday employers each
want an account and /accounts handles that when they are ready./daily.Two things the tool will not do, so they are not surprised: it does not
pass a "prove you are human" check, and it does not sign in anywhere
unless they set that up. A form that needs them stays open in the tool's
window; /resume picks it up.
First-run setup, start to finish. Use when the user says /setup, "set this up", "get me started", "help me use this", hands you this repository for the first time, or when data/profile.json does not e
---name: setupdescription: First-run setup, start to finish. Use when the user says /setup, "set this up", "get me started", "help me use…---# .claude/skills/setup/SKILL.mdOverview
First-run setup, start to finish. Use when the user says /setup, "set this up", "get me started", "help me use this", hands you this repository for the first time, or when data/profile.json does not exist. Installs what is missing, builds the profile from the resume and a short interview, has the user add their own JEV key (TypeSafe or OpenRouter), finds jobs, rehearses, and stops for a "go" before anything is sent.
FAQ
Download .claude/skills/setup/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/qbeka/jev-job-search.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.