agentsclimarketplace
Sign in

Workday agent

Skill jjoseph1ne/workday-agent

Auto-fill Workday-style job applications using the user's profile and answer bank. Triggers on any mention of "fill workday", "apply to this job", or any Workday URL (`*.myworkdayjobs.com`). Uses Claude in Chrome to read the page, map fields to profile data, generate tailored short answers, and stop at Review for the user to submit.From its SKILL.md

Install
npx -y skills add jjoseph1ne/workday-agent

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.5 KB, 564 tokens by cl100k_base, as published. Nobody here has run it

Workday Auto-Fill Skill

This skill turns a Workday application URL into a half-filled, reviewed-ready application, without auto-submitting.

When to invoke

  • User pastes any URL that matches *.myworkdayjobs.com or similar Workday-hosted ATS
  • User says "fill this Workday for me", "apply for me", or "use my profile to apply to X"
  • User uploads a new job description and says "tailor my application to this"

Required files (in the same folder)

FilePurpose
profile.jsonStructured profile: identity, address, work auth, education, experience, skills, logistics
answer_bank.mdReusable answers for common Workday questions, with variants
workday_playbook.mdStep-by-step Chrome agent runbook (Phases 0-7)

How to run (for the agent reading this)

  1. Read all three files first. Do not start the browser agent before you've loaded them.
  2. Run Phase 0 pre-flight from workday_playbook.md: ask the user for role, full-time vs intern, referral, and "why us" hook.
  3. Follow Phases 1 through 7 in workday_playbook.md.
  4. Stop at Review. Never click Submit.
  5. Log the run to logs/YYYY-MM-DD__company__role.md in the same folder.

What to surface to the user mid-run

  • Any [CONFIRM] field the profile didn't resolve
  • Any new question not in the answer bank
  • Every drafted essay, shown in full, before it goes into the form
  • Final review table: field -> value, essays in full, anything skipped

Hard safety rules

  1. Never click Submit.
  2. Never invent answers.
  3. Never fill work-authorization or EEOC fields without explicit confirmation.
  4. Never enter SSN, bank info, or payment info.
  5. Stop on captcha or 2FA and ask for help.
  6. Throttle typing; one tab at a time.

Updating the skill

  • New Q/A pairs discovered mid-application go into answer_bank.md under "New questions captured" and should be reviewed with the user at the end of the session.
  • profile.json should be updated whenever the user takes a new role, graduates, changes address, etc.

Not in scope

  • Workday pre-hire assessments
  • Video interviews (HireVue etc.)
  • Background check or I-9 e-verify forms
  • Anything that requires SSN or banking details

What ships with it: 6 files

24.9 KB alongside SKILL.md

Keep looking

Skills are one crate of 326,506. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.