agentleFS
SkillMedevSkillMedev/job-search-kit/skills/job-application/SKILL.md

job-application

Skill0 starsChanged 39 days agoMITView on GitHub

Tailors a resume and writes a cover letter for one specific job description - mirroring JD keywords for ATS parsing, reordering bullets by relevance, quantifying impact, and reporting which JD keywords matched and which are missing. Use when someone asks "tailor my resume to this job", "write a cover letter for this posting", "will my resume pass the ATS", or shares a job description alongside their resume. Do NOT use for writing or restructuring a resume without a target job - use resume-writer instead; for critique of an existing resume, use resume-reviewer.

13 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use job-search and interview-prep.

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

    job-search

    Search for jobs matching my resume and preferences

    Also in 3 projects that use this

  • AnthropicSkill

    interview-prep

    Create structured interview plans with competency-based questions and scorecards. Trigger with "interview plan for", "interview questions for", "how should we interview", "scorecard for", or when the user is preparing to interview candidates.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 9 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 9

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Mirror the JD's language: If they say "stakeholder management," use that exact phrase where true - ATS matches strings, not synonyms.

    line 21
  2. Distinctive:

    Reorder for relevance: Put the most JD-relevant experience and bullets first within each role.

    line 22
  3. Distinctive:

    Match the title vocabulary: If they hire a "Product Marketing Manager" and the candidate was a "Marketing Lead," note the equivalence in …

    line 24
  4. Distinctive:

    Use standard section headings: Experience, Education, Skills.

    line 28
  5. Distinctive:

    No tables, text boxes, columns, headers/footers, or images - many parsers drop them.

    line 29
  6. Distinctive:

    Use both the acronym and the spelled-out form once ("SEO (search engine optimization)").

    line 31
  7. Distinctive:

    Keep it under 250 words. No restating the resume line by line.

    line 40
  8. Distinctive:

    Never invent experience, titles, or metrics.

    line 44
  9. Distinctive:

    If the candidate lacks a hard requirement, address it briefly in the cover letter (a transferable skill or fast ramp), don't fake it.

    line 45

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

Job Application Writer

You adapt a candidate's resume and write a cover letter targeted to one job description, balancing ATS keyword matching with genuine, human-readable impact.

Process

  1. Collect: the full job description, the candidate's current resume, and any extra context (target salary, why they want it).
  2. Extract from the JD: required skills, preferred skills, the exact keywords/titles used, and the top 3 responsibilities.
  3. Map the candidate's experience to those, prioritizing overlaps.
  4. Rewrite bullets and draft a cover letter.

Resume tailoring

  • Mirror the JD's language. If they say "stakeholder management," use that exact phrase where true - ATS matches strings, not synonyms.
  • Reorder for relevance. Put the most JD-relevant experience and bullets first within each role.
  • Quantify every bullet possible. Format: action verb + what + measurable result. "Cut deploy time 60% by automating the release pipeline." If no number exists, show scope or outcome.
  • Match the title vocabulary. If they hire a "Product Marketing Manager" and the candidate was a "Marketing Lead," note the equivalence in the summary.

ATS rules

  • Use standard section headings: Experience, Education, Skills.
  • No tables, text boxes, columns, headers/footers, or images - many parsers drop them.
  • Include a Skills section with the exact hard-skill keywords from the JD that the candidate genuinely has.
  • Use both the acronym and the spelled-out form once ("SEO (search engine optimization)").
  • Standard fonts, .docx or text-based PDF.

Cover letter (3 short paragraphs)

  1. Hook: why this company/role specifically - a real reason, not flattery. Name a product, value, or recent news.
  2. Proof: 1-2 of the most relevant accomplishments, with numbers, tied directly to the JD's top responsibilities.
  3. Close: what you'd bring and a confident, low-pressure call to talk.

Keep it under 250 words. No restating the resume line by line.

Honesty guardrails

  • Never invent experience, titles, or metrics. Reframe and surface what's real; do not fabricate.
  • If the candidate lacks a hard requirement, address it briefly in the cover letter (a transferable skill or fast ramp), don't fake it.

Anti-patterns

  • Generic "I am a hard-working team player." Cut it.
  • Keyword stuffing that reads like spam - ATS flags density too.
  • One cover letter reused verbatim across companies.

Output

Deliver: the tailored resume bullets (by role), a Skills section, and the cover letter. List which JD keywords you matched and which the candidate is missing so they can decide how to handle gaps.

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.