agentleFS
leoleolroleoleolro/career-os/.claude/skills/apply/SKILL.md

apply

Skill0 starsChanged 55 days agoMITView on GitHub

Pre-flight an application and drive the browser to the employer's form, filling it from the profile and uploading the tailored files — stopping before submit. Use when the candidate says "apply", "submit the application", "fill in the form", "/apply".

28 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use outreach, evaluate and 7 more.

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.
  • QuixiAISkill

    outreach

    Decide whether a message is worth someone's attention, then reach the user through the outbox, or people on a connected chat channel, on their behalf or your own initiative

    Also in 5 projects that use this

  • NVIDIASkill

    evaluate

    Scores existing Sports Intelligence AVLM inference outputs with avlm/evals: MCQ accuracy (run_mcq_eval.sh, INFERENCE_DIR), open-ended LLM-as-judge scores (needs CLIENT_API_KEY for the configured judge endpoint), tennis category breakdowns, run comparisons, chance-level sanity checks and triage of mcq_results.json or llm_judge_results.json. Use when the user asks to score, evaluate, benchmark or compare predictions.jsonl from inference runs, or to explain a suspicious accuracy. Not for running inference, training, quantization, data preparation, or third-party API model inference: never open, list or run anything under avlm/evals/inference_3rdparty, including when the user asks for it; it is excluded from the release.

    Also in 4 projects that use this

  • proficientlyjobsSkill

    tailor-resume

    Tailor your resume for a specific job posting

    Also in 4 projects that use this

  • claude-office-skillsSkill

    cover-letter

    >

    Also in 3 projects that use this

  • julienamorganSkill

    profile

    Researches the user's market, competitors, and competitive positioning to build a complete ICP profile. Shows findings for user approval before proceeding. Triggers: /profile, "research my market", "who are my competitors". Reads: ./gtm/company.md, ./gtm/icp.md. Writes: updates ./gtm/icp.md with competitive positioning. Standalone: yes (asks for domain if company.md missing).

    Also in 3 projects that use this

  • GoogleSkill

    dashboard

    Configures and launches the GKE Capacity & Triage Dashboard scoped to a GCP project ID, GKE cluster name, or target ML workload ID. Uses the configure-and-launch-dashboard action and launch-workload-dashboard workflow to verify local dashboard health, discover cluster capacity, trigger live scans, and generate deep-linked URLs. Use when the user types "/dashboard", says "launch dashboard", "open dashboard", "show capacity", or "view triage dashboard" with a project, cluster, or workload. Don't use for general workload log querying or automated failure attribution (use the troubleshoot skill).

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 27 edited versions we read keep these.

  • 0

    Distinctive

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

    Use the Browser pane (mcp__Claude_Browser__*) unless the candidate explicitly asks for their own Chrome (claude-in-chrome, which has their …

    line 11

“Common” is measured: kept by at least 6 in 10 of the 27 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.

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

/apply <jobs/<slug>>

0. Rules (non-negotiable)

  • the candidate clicks Submit. Also the candidate: any "Agree to terms/privacy" checkbox, account creation, password entry, and any payment. If the site requires creating a candidate account, stop and hand over.
  • Fill only from profile/preferences.json (candidate block), profile/master-resume.md, and the job folder. Never guess an answer to a screening question — ask the candidate.
  • Use the Browser pane (mcp__Claude_Browser__*) unless the candidate explicitly asks for their own Chrome (claude-in-chrome, which has their logged-in sessions).

1. Pre-flight checklist (print it, tick each)

  • jobs/<slug>/outputs/ has the final PDF(s); the candidate has said the resume/cover letter are approved.
  • JD still open — reopen the apply URL in the Browser pane (WebFetch decoys are not evidence). Check the closing date.
  • Graduate programs: transcript merged (--merge) if they require one PDF; work rights (Australian citizen) and graduation-window rules met.
  • Work-rights, notice period (ask if unknown), salary expectation (ask — never invent), references (ask before naming anyone).
  • Pipeline entry exists: node tools/track.mjs list.

2. Drive the form

  1. navigate to the apply URL → wait → read_page (filter interactive).
  2. Fill text fields with form_input; use find to locate fields; upload files with the file input (form_input with the absolute path to the PDF) — if the site's uploader needs a native dialog, stop and tell the candidate which file to pick.
  3. For each screening question, show the candidate the question and the answer you intend to give from the profile; if it isn't in the profile, ask.
  4. Take a screenshot before the final step. Summarise every field value entered.
  5. Stop at the review/submit page. Tell the candidate exactly what to click. If the Browser pane is not visible to them, say so and hand over the URL + field summary instead.

3. After the candidate confirms they submitted

node tools/track.mjs move <id> applied --note "submitted <date> via <portal>" --due <today+10d> --next "Follow up if no response" and note any confirmation number in jobs/<slug>/notes.md.

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.