agentleFS
JiemsLBJJiemsLBJ/offer-harvester/.agents/skills/job-form-filler/SKILL.md

job-form-filler

Skill4 starsChanged 2 months agoMITView on GitHub

Safely fills job application forms with the AI Job Search Playwright pipeline. Use when a user asks to fill, autofill, inspect, or submit a job application form on a supported recruiting portal or an unfamiliar company careers site. Selects a verified dedicated adapter when available and otherwise uses the explicit generic fill-only fallback, learns missing form requirements, and stops for human review.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 5 are distinctive, and 7 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    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
  1. Very specific:

    Run from the repository's automation directory.

    line 8
  2. Very specific:

    Prefer the URL-recognized dedicated adapter.

    line 12
  3. Very specific:

    Use generic only when no dedicated adapter recognizes the URL and the user supplies the direct application-form URL.

    line 13
  4. Very specific:

    If the page has changed, use --probe, inspect the saved structure snapshot, then update the dedicated adapter.

    line 14
  5. Very specific:

    Only when the user explicitly asks to submit, rerun without --fill-only.

    line 24
  6. Distinctive:

    Use a separate persistent profile for sites that need independent login state or simultaneous review windows:

    line 40
  7. Very specific:

    If Chrome really crashes or a page closes, inspect apply_bot/state/browser_events.jsonl.

    line 46
  8. Distinctive:

    Never persist an ID-card number or copy it into logs, screenshots, the profile, or the dashboard.

    line 54
  9. Distinctive:

    Never bypass CAPTCHA, QR login, SMS verification, paywalls, or risk controls.

    line 55
  10. Distinctive:

    Never send BOSS messages, emails, or other external communications automatically.

    line 56
  11. Very specific:

    Never batch-submit. Dedicated submission always requires a fresh per-job y.

    line 57
  12. Distinctive:

    Stop on already-applied, closed, mismatched-company, or mismatched-title signals and ask the user.

    line 58

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Job Form Filler

Run from the repository's automation directory. Read automation/README.md and, when present, AUTOMATION_HANDOFF.md before modifying adapters or safety behavior.

Choose the mode

  1. Prefer the URL-recognized dedicated adapter. Current dedicated adapters are ByteDance, Shixiseng, Tencent, Wecruit/Hotjob, Nowcoder, BOSS, Xiaohongshu, Bilibili, and Zhaopin. The Hotjob adapter covers verified wecruit.hotjob.cn/.../pb/posDetail.html pages; do not assume older www.hotjob.cn/wt/... systems share its structure.
  2. Use generic only when no dedicated adapter recognizes the URL and the user supplies the direct application-form URL. Never use generic mode on a job list, job detail, login landing page, or unknown one-click-apply button.
  3. If the page has changed, use --probe, inspect the saved structure snapshot, then update the dedicated adapter. Do not guess selectors that could submit an application.

Dedicated adapter workflow

Fill, learn, and keep the browser open for review:

python -m apply_bot.apply_one "<job-url>" --fill-only --review --expect-company "<company>" --expect-title "<title>"

Only when the user explicitly asks to submit, rerun without --fill-only. The terminal must display the per-job confirmation summary, and only an entered y authorizes that single submission.

Generic fallback

Have the user log in and navigate to the actual form if necessary, then run:

python -m apply_bot.apply_one "<direct-form-url>" --portal generic --fill-only --review

Generic mode fills only empty, non-sensitive text/select fields that can be grounded in the structured profile. It does not click Apply, upload an ambiguous file input, or submit. It may upload the selected resume only through a visible control explicitly labelled resume/CV; QQ Docs' narrowly identified resume questionnaire is supported this way. The user reviews the visible page and handles unsupported widgets manually.

Preserve the review browser

--review starts system Chrome as an independent process with a loopback-only CDP port. When filling completes, is blocked, or raises an automation error, Playwright disconnects and the Chrome window stays open until the user closes it. Do not add a terminal input() hold or call browser.close() for this mode.

Use a separate persistent profile for sites that need independent login state or simultaneous review windows:

python -m apply_bot.apply_one "<job-url>" --fill-only --review --profile-dir "apply_bot/.chrome-profile-<site>"

If Chrome really crashes or a page closes, inspect apply_bot/state/browser_events.jsonl. Diagnostics may contain the portal, workflow stage, exception type, and URL without its query string or fragment; never add form values, cookies, tokens, or uploaded document contents.

Learn from every form

The pipeline snapshots field labels and static selector metadata without reading input values. It records covered, missing, unmapped, and manual-sensitive requirements in the local dashboard. Never invent an answer. Ask the user to resolve missing facts later in the dashboard; saved answers then become available to future forms.

Safety invariants

  • Never persist an ID-card number or copy it into logs, screenshots, the profile, or the dashboard.
  • Never bypass CAPTCHA, QR login, SMS verification, paywalls, or risk controls.
  • Never send BOSS messages, emails, or other external communications automatically.
  • Never batch-submit. Dedicated submission always requires a fresh per-job y; generic mode never submits.
  • Stop on already-applied, closed, mismatched-company, or mismatched-title signals and ask the user.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.