Skills / Apply online
Apply online
Get an online job application submitted properly. Parses the posting, tailors the materials honestly, and logs what was sent. Use when they say "help me apply for this job", "fill out this application", or have a posting link ready.
Use this skill. Nothing to install.
Don't have an agent? · Raw file: skills/apply-online.md
Watch the first two minutes
This is how a session goes, including the moment most people want to fudge. Click through it.
Scripted example of a real session.
Tempted to stretch the truth on the form?
The skill won't help with that, and it says so up front. No invented dates, no fake availability, no "yes" to experience questions that are really "no". What it will do is find the true version of your answer, which is usually better than you think: informal work counts, and a specific honest answer reads better than an inflated vague one. If a question exposes a gap that actually matters, the fix is to build the missing thing for real.
What you end up with
Applications actually sent, and a prep pack for each one so the form held no surprises. Here is the pack for one application, built before a single field was touched.
- Blockers get caught before you type. The hard requirements are checked against your reality first. If one genuinely rules you out, you skip this posting instead of spending an hour on a dead application.
- Three plain sentences you could say out loud. Drafted with you, edited until it sounds like you. Every claim in it is checkable: the weekly shopping, the two years of babysitting.
- The log is the receipt. Employer, date, resume version, any account the form made you create, and a follow-up date. Without it, applications rot.
Anatomy of a good short answer
Forms that ask "why do you want this job" get this shape, never boilerplate:
- A A true, specific connection to this place. If you can't name one, say what genuinely draws you.
- B What you actually want, plainly. Employers hiring entry level expect exactly this.
- C The practical facts they are scanning for: start date, hours.
- D One piece of evidence you are reliable. True and small beats grand and vague.
Questions people actually ask
Is this free?
The skill is free, no account, no catch. The agent you paste it into may or may not be: Gemini has the widest free tier, Copilot's free tier is enough to try it, ChatGPT and Claude free plans can also run it in a chat.
Will it fill in and submit the form for me?
No. It preps every answer so the form holds no surprises, and you type or paste and you click send. Anything submitted under your name should have passed through your hands.
What if I don't meet a requirement?
The posting gets read together first, and the hard requirements get checked against your reality before anything else. A genuine blocker means moving to the next opening instead of wasting the application. A soft gap gets the honest answer plus what you are doing about it.
The site made me create an account. Is that normal?
Common, unfortunately. Many employers use application systems that force an account. You create it with your own email and password, and the login goes in your log so the callback six weeks later isn't a mystery.
How many applications per sitting?
At least one fully submitted with the confirmation seen. Quality of the prep matters more than the count, and a logged, tailored application beats three rushed ones.
Where to go from here
Application sent? The waiting has skills too:
Need more to apply to? Fill the pipeline:
Curious? Read the full skill — the exact instructions your agent gets
--- name: apply-online category: get-hired description: Get an online job application submitted properly. Parses the posting, tailors the materials honestly, and logs what was sent. Use when they say "help me apply for this job", "fill out this application", or have a posting link ready. --- # apply-online Get real applications submitted with someone, probably their first. Online applications often remain in drafts; the bar here is applications actually sent this sitting, each one honest, tailored, and logged so they know what they are waiting on. ## Ground rules - Nothing invented. No fabricated jobs, dates, availability, eligibility, references, or certifications — on the resume, in form fields, or in screening questions. If a question exposes a real gap, answer it truthfully; if they ask you to fudge it, refuse and point at the honest fix (build the missing thing — sphinxstack has skills for that). - Their words. You draft, they edit until every sentence sounds like them; anything submitted under their name is theirs. Never answer "why do you want this job" with boilerplate they could not say out loud. - They drive the browser on anything that submits. You read the form with them and prep every answer; they click send. ## Parse the posting Read the full posting together. Pull out: the actual duties, the hard requirements (age, permit, schedule, certifications), the nice-to-haves, and the exact nouns the employer uses. Check the hard requirements against their reality first — if one genuinely blocks them, say so now and move to the next opening instead of wasting an application. ## Tailor the materials - Resume: start from their real one (build-resume if none exists). Reorder and reword so the most relevant true things come first, using the posting's own vocabulary where it is honest. Save as a new copy named for this employer. - Short answers and cover letter, only if the form asks: three or four plain sentences — why this place, what true thing they bring, when they can work. Workshop until they own every line. - Screening questions: rehearse the likely ones (availability, transport, why here) so the form holds no surprises. ## Submit and log Go through the form field by field. You supply the prepared answers; they type or paste, and they hit submit. Watch for the traps: resume uploads that mangle formatting (check the parsed preview), required fields hidden below the fold, accounts the ATS forces them to create — have them make those with their own email and password. After each submission, log it: employer, role, date, link, which resume version, any login created. Use job-application-tracker if they have it; a plain spreadsheet row otherwise. ## Done - At least one application fully submitted, confirmation seen - Every submitted word true and theirs - Each application logged with a follow-up date - Next: follow-up-after-applying in about a week, interview-prep the moment anyone replies