portal-filler
Skill0 starsChanged 5 months agoUnlicenseView on GitHub
Autofill external ATS application forms (Greenhouse, Lever, Ashby, and a generic fallback) from an identified opportunity and its tailored artifacts, using Chrome MCP. Fills fields, dropdowns, file uploads, and screener questions, then STOPS for human review — it never clicks the final Submit. Use when the user wants to apply to a scouted job's external portal. Part of the Mercury job search toolkit.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- experience-bankSkill
- job-scoutSkill
- outreach-trackerSkill
- profile-optimizerSkill
- recruiter-outreachSkill
- resume-tailorSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 50
If a required key is missing, ask the user once and persist it so it's reusable next time:
- Very specific: line 101
Use the adapter's fields to fill the known core fields by selector (most reliable), then run the generic matcher (step 4) for everything …
- Distinctive: line 178
When something can't be filled programmatically, add it to the review summary as a "do this yourself" item rather than silently skipping it.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Portal Filler
Take an identified opportunity (a jobs row with an external link) plus its
tailored artifacts from resume-tailor, navigate the employer's ATS with
Chrome MCP, and fill the application form. Fill, then pause for human review —
never auto-submit. This mirrors the confirm_send human-in-the-loop pattern
used by recruiter-outreach.
[!IMPORTANT] This skill fills, it does not submit. Always end by handing the already-open browser back to the candidate to verify and click Submit themselves. Do not click the final Submit/Apply button.
Prerequisites
- Chrome MCP —
navigate_page,take_snapshot,fill,fill_form,click,upload_file,take_screenshot(andpipelineto batch them). - Mercury CLI —
mercury detect-portal,mercury answer,mercury match,mercury application,mercury export. - A reusable answer store populated via
mercury answer set(see below). - Tailored artifacts on disk: the
.typresume and the cover letter.
Workflow
1. Load inputs
- Resolve the opportunity: the
jobsrow (id, company, title,link). - Confirm tailored artifacts exist for it (resume
.typ, cover letter). Load the reusable answer store:
mercury answer listKeys are canonical field ids grouped by
category:contact(email, phone),eligibility(work_authorization, requires_sponsorship, salary_expectation),links(linkedin_url, github_url),eeo(eeo_gender, eeo_veteran, eeo_disability),custom.If a required key is missing, ask the user once and persist it so it's reusable next time:
mercury answer set --key phone --value "+1 555 ..." --category contact
2. Produce the upload PDF
Chrome MCP upload_file needs a real file; resume-tailor emits .typ. Compile
it with the shared helper:
mercury export --typ ".mercury/tailored/{company}-{jobId}.typ" \
--out ".mercury/tailored/{company}-{jobId}.pdf"The cover letter is uploaded as-is when the form has a file field, or pasted into a textarea when it has one.
3. Detect the ATS + load its adapter
mercury detect-portal --url "{link}"Returns the portal id plus its known stable field selectors, widget types, and quirk notes:
{
"portal": "greenhouse",
"fields": [
{ "key": "first_name", "selectors": ["#first_name"], "widget": "text" },
{ "key": "email", "selectors": ["#email"], "widget": "text" },
{ "key": "phone", "selectors": ["#phone"], "widget": "tel" },
{ "key": "resume", "selectors": ["#resume"], "widget": "file" }
],
"notes": ["...quirks: react-select dropdowns, async S3 upload, reCAPTCHA..."]
}Adapter coverage (selectors verified against live forms):
| Portal | Host | Stable fields keyed by | Resume | Dropdowns |
greenhouse | greenhouse.io | ids (#first_name, #email, …) | async S3 upload | react-select |
lever | lever.co | name attrs (name, email, org, urls[…]) | real file input | native <select> |
ashby | ashbyhq.com | #_systemfield_* ids | file input | button/listbox |
generic | anything else | — (no static fields) | — | — |
Use the adapter's fields to fill the known core fields by selector (most
reliable), then run the generic matcher (step 4) for everything else — the
per-posting custom questions the adapter deliberately doesn't map. For
generic, skip straight to step 4.
4. Fill (adapter selectors + generic match → fill → pause)
navigate_pageto thelink, thentake_snapshotto get the live form tree with element uids. Collect the visible field labels.- Fill the adapter's known
fieldsfirst, by selector, honoring eachwidget(see widget mechanics below). Map the remaining labels to answer keys with the deterministic matcher — don't eyeball it:
mercury match --labels '["Email *","Phone","Will you require sponsorship?", ...]'It joins the labels against your
applicant_answersand returns a plan:{ "matched": [{ "label": "Email *", "key": "email", "value": "me@example.com", "confidence": 1, "reason": "exact" }], "unfilled": [{ "label": "Phone", "skip": "no-stored-answer", "key": "phone" }, { "label": "Gender", "skip": "eeo-human-only", "key": "eeo_gender" }, { "label": "Favorite color", "skip": "no-match" }] }- Fill only the
matchedentries withfill/fill_form(batch viapipeline), keyed back to the snapshot uid for each label. Upload the resume PDF to the resume file field. - Leave every
unfilledfield empty and keep its list for the review summary. Theskipreason tells the user why:no-stored-answer— recognized, but you have no value stored (add one withmercury answer setif you want it auto-filled next time).eeo-human-only— EEO/demographic; never auto-filled, human enters it.no-match/ambiguous— couldn't confidently map it; human handles it.
take_snapshot+take_screenshotand present a "review these N fields before you submit" summary.
[!WARNING] Truthfulness guardrails carry over from
resume-tailor: never invent answers (work authorization, years of experience, EEO). The matcher already refuses to fill EEO fields and anything with no stored value — respect itsunfilledlist, don't fill those by hand from assumptions.
4a. Widget mechanics (per widget type; learned against live forms)
ATS forms are messier than a flat label list suggests. The adapter's widget
field tells you how to drive each control:
text/tel— plain inputs fill reliably. Set the value and dispatchinput+changeevents (React-controlled inputs ignore a bare value set).telis often anintl-tel-inputwidget that reformats the number (e.g.(+12) 34 5 6789-0000→+12 34 567890000); the reformatted value is correct — don't treat the difference as a failure.native-select(Lever dropdowns) — a real<select>: set value to the matching option and dispatchchange.react-select(Greenhouse) /listbox(Ashby) — not text inputs. Many questions that look free-text (country of residence, "require sponsorship?", yes/no screeners) are comboboxes. Click to open, then click the option — typing a raw value may not register. Confirm the selected text after.file— uploads can be unreliable. Greenhouse uses an async S3-backed widget behind an "Attach" button and swaps the underlying<input type=file>out after selection; Lever (#resume-upload-input) and Ashby (#_systemfield_resume) are plainer file inputs. Always click "Attach"/"Upload File", upload, then verify the chosen filename is shown before trusting it; if it didn't land, tell the user to attach the PDF manually. (PDF is produced bymercury export.)- reCAPTCHA / SSO may gate submission — out of scope; leave for the human.
Per-posting custom questions (Greenhouse #question_*, Lever
cards[uuid][fieldN], Ashby random-uuid ids) are not in the adapter — map
them via mercury match and drive them by their widget type above.
When something can't be filled programmatically, add it to the review summary as a "do this yourself" item rather than silently skipping it.
5. Persist + surface
Record what happened so the dashboard reflects it (table-scoped live refresh):
# first time for this opportunity
mercury application add --job-id {jobId} --portal {portal} \
--external-url "{link}" \
--resume-path ".mercury/tailored/{company}-{jobId}.pdf" --status draft
# after filling
mercury application update --id {appId} --status filled \
--portal {portal} --external-url "{link}" \
--fields '{json of what was entered}' \
--unfilled '["work_authorization","eeo_gender", ...]'
mercury activity log --skill portal-filler \
--summary "Filled {company} {title} ({portal}) — {N} fields, {M} left for review"Status lifecycle: draft → filled → submitted (use needs_input when blocked
on a missing answer). The candidate moves it to submitted after they click
Submit — or you set it on their confirmation; this skill never submits.
6. Hand off
Tell the user exactly which fields to verify and which were intentionally left blank (especially EEO), and that the browser is open and ready for them to review and submit.
Out of scope (v1)
- Workday, Taleo, iCIMS (multi-step, iframe-heavy, account-gated).
- Fully autonomous submit.
- CAPTCHA / SSO automation.
Summary table to print
| Field group | Filled | Left for review |
| Contact | email, phone | — |
| Eligibility | requires_sponsorship | work_authorization (verify) |
| Links | linkedin_url, github_url | — |
| EEO | — | gender, veteran, disability (human-only) |
| Resume | uploaded PDF | — |
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.

