accounts
Skill368 starsChanged 5 days agoMITView on GitHub
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.
- Reads credentials
5 other projects use a version of this.
Adopted by
Most recently taken up by
- notque/vexjoy-agenttheir own version, first seen Nov 10, 2026
- grechj/Australian-Builders-Braintheir own version, first seen Oct 17, 2026
- harshsinghmp/muse-skillstheir own version, first seen Oct 15, 2026
- notque/claude-code-toolkittheir own version, first seen Oct 8, 2026
- MGrin/bb-plugin-accountstheir own version, first seen Sep 13, 2026
Used with
Projects with it also use content and research.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Rayan55050Skillcontent
Создание контента: посты, статьи, тексты
Also in 3 projects that use this
NVIDIASkillresearch
Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.
Also in 3 projects that use this
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- notque/claude-code-toolkit★ 450same name
- notque/vexjoy-agent★ 450same name
- MGrin/bb-plugin-accounts★ 4same name
- harshsinghmp/muse-skills★ 1same name
- grechj/Australian-Builders-Brain★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 1 is distinctive, and 7 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
Run npx jev accounts. If nothing is set up, this is the guided setup:
- Very specific: line 29
Run 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 …
- Very specific: line 32
Ask which one to start with, then do /accounts signin <employer>.
- Very specific: line 33
After it works, run npx jev discover and say how many jobs at that employer are now in the queue.
- Distinctive: line 36
If something is set up, say what, what waits for them, and the next step.
- Very specific: line 52
After any of these, run npx jev accounts and read the result back.
- Very specific: line 82
Never allow more than they said: No flag they did not agree to, and no edit to data/accounts.json by hand.
- Very specific: line 84
If the permission system declines a command, do not try another way.
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/accounts
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.
- They sign in once at an employer, themselves; the tool keeps the session.
- They store that employer's password; the tool signs in when the session ends.
- Experimental: the tool makes accounts where they have none.
/accounts with nothing after it
Run npx jev accounts. If nothing is set up, this is the guided setup:
- Say in two sentences what this is: Workday employers each want an account, and the simplest way is to sign in once yourself.
- Run
npx jev statusand name the two or three Workday employers with the best jobs they are missing (npx jev queuelists skipped jobs withworkdayas the reason; use the companies, not ids). - Ask which one to start with, then do
/accounts signin <employer>. - After it works, run
npx jev discoverand 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.
What the user can type
| They type | You do |
/accounts signin <employer> | Show npx jev accounts signin <employer> in a bash block. It opens the employer's page in the tool's Chrome window; they sign in there themselves. Tell them to click Run and then look at that window. |
/accounts password <employer> | Run npx jev accounts password <employer>. A window opens on their Mac; they type that employer's password there, twice. You never see it. With no employer it stores the one password they use on accounts they already had. |
/accounts browser <employer> | Only when they say they saved that employer's password in the tool's Chrome and want the tool to use it. Run npx jev accounts browser <employer>. The tool then presses Sign In once that browser has filled the page in; it types nothing and never reads the password. --off takes it back. |
/accounts add workday | The questions below. Run it with --preview first and read what it allows back to them. Save only after a yes, with exactly the flags they agreed to. |
/accounts setup <employer> | Show npx jev accounts setup <employer> in a bash block. It signs in, or makes the account. They click Run. |
/accounts clear | npx jev accounts clear, after they fixed what paused an account. |
/accounts off / /accounts on | npx jev accounts off / on. Say that everything set up is kept. |
/accounts forget <employer or all> | Run it without --yes first and read back what it removes. After a yes, run it with --yes. Say that the account at the employer still exists. |
/accounts gmail | Only if they want verification emails read for them. Say first that the default needs no setup: they click the link and type /resume. If they still want it, walk through "Verification emails" in docs/ACCOUNTS.md one step at a time. Do not promise how long it takes. Then /accounts gmail <file> runs npx jev gmail connect --client <file>. |
After any of these, run npx jev accounts and read the result back.
The questions for add workday
Say that this is experimental before asking. Each is a separate yes:
- May the tool make an account where an employer has none for you?
Each is a real account at that employer, in your name. (
--create) - May it tick the box that accepts each employer's candidate-account
terms for you, without your reading them one by one? A marketing box
is never ticked. (
--terms) - May it read the verification email an employer sends? That needs
Gmail connected. Without it you click each link. (
--verify-email)
They choose no password: each new account gets its own random one, kept in
their Keychain. --max-new 3 is the default.
What you never do
- Never ask for, read, type or repeat a password, a code or a token,
in chat, in a file or in a command. Never read the Keychain,
.envor the tool's Chrome profile. - Never start anything that signs in or signs up at an employer. That
is
accounts signin,accounts setup,applyon a Workday job in a real run,dailyandresume --submitwhen Workday is set up. Show the command in abashblock; 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. - Never pass a human check: a CAPTCHA, a phone code, a passkey, or the code a board emails because it suspects a robot.
- Never allow more than they said. No flag they did not agree to, and
no edit to
data/accounts.jsonby hand. - If the permission system declines a command, do not try another way.
Show the command in a
bashblock for them to run with one click.
When a sign-in stops
The reason is on the job's row (/status). In their words:
- The employer refused the password. Either they sign in themselves in
the tool's Chrome window, or they type
/accounts password <employer>with the right one. Then/resume. - A robot check, a phone code, a passkey, single sign-on. They do it
in the tool's window. Then
/resume. - A verification email. They click its link in their own mail. Then
/resume. - No account there, in a rehearsal.
/accounts setup <employer>, or/accounts signin <employer>to make it themselves.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

