- 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 accounts -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 accounts -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 accounts -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 accounts -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/accountsFrom the publisher
The user types a short command; you run the tool for them. They should
never have to type npx or edit a file. docs/ACCOUNTS.md is the
reference. Everything here is off until the user turns it on.
There are three ways to use it. Lead with the first. Offer the second when a session has ended, and the third only when they ask for less work per employer, and say that it is experimental.
/accounts with nothing after itRun npx jev accounts. If nothing is set up, this is the guided setup:
npx jev status and name the two or three Workday employers with
the best jobs they are missing (npx jev queue lists skipped jobs with
workday as the reason; use the companies, not ids)./accounts signin <employer>.npx jev discover and say how many jobs at that
employer are now in the queue. Offer /apply.If something is set up, say what, what waits for them, and the next step.
After any of these, run npx jev accounts and read the result back.
add workdaySay that this is experimental before asking. Each is a separate yes:
--create)--terms)--verify-email)They choose no password: each new account gets its own random one, kept in
their Keychain. --max-new 3 is the default.
.env or
the tool's Chrome profile.accounts signin, accounts setup, apply on a Workday job in a
real run, daily and resume --submit when Workday is set up. Show the
command in a bash block; the app puts a Run button on it. A rehearsal
(--dry) of a Workday job signs in to an account they have and makes
nothing; treat it the same way.data/accounts.json by hand.bash block for them to run with one click.The reason is on the job's row (/status). In their words:
/accounts password <employer>
with the right one. Then /resume./resume./resume./accounts setup <employer>, or
/accounts signin <employer> to make it themselves.Let the tool apply on job boards that want an account (Workday today). Use when the user says /accounts or /account, with or without a subcommand (signin, password, add, setup, clear, off, on, forget,
---name: accountsdescription: Let the tool apply on job boards that want an account (Workday today). Use when the user says /accounts or…---# .claude/skills/accounts/SKILL.mdOverview
Let the tool apply on job boards that want an account (Workday today). Use when the user says /accounts or /account, with or without a subcommand (signin, password, add, setup, clear, off, on, forget, gmail), "Workday", "sign in for me", "why are Workday jobs skipped", or asks about verification emails.
FAQ
Download .claude/skills/accounts/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.