agentleFS
tharun-kumar-korinepallitharun-kumar-korinepalli/job-application-claude-skills/skills/job-application-kit/SKILL.md

job-application-kit

Skill2 starsChanged 2 months agoMITView on GitHub

Build, tailor, review and package job applications: resumes, CVs, Lebensläufe, cover letters, Anschreiben, motivation letters, ATS keyword audits, job description fit checks, interview prep, follow-up emails and an application tracker. Use this skill whenever the user mentions a resume, CV, cover letter, job posting, job description, applying for a job, ATS, 'not getting interviews', 'help me get hired', LinkedIn-to-resume, or wants documents tailored to one role. Also use it for German-speaking markets (Germany, Austria, Switzerland): Bewerbung, Lebenslauf, Anschreiben, Motivationsschreiben, Arbeitszeugnis, Bewerbungsmappe. Use it even when the user only pastes a job ad and their background with no explicit request. Do not use for LinkedIn profile copy, portfolio websites or general document formatting unrelated to job hunting.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. JasmineNy/codex-skills-portfolio★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

The file

Show its rules and text

We split this skill into the rules it gives an agent

19 rules. About 0 are common, 16 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈16

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never invent anything. Every claim will be tested in an interview.

    line 14
  2. Very specific:

    Read SKILL.md fully. Then load only the references the task needs:

    line 18
  3. Distinctive:

    Before writing anything, establish these.

    line 37
  4. Very specific:

    If the person cannot give numbers, ask for estimates and label them [confirm].

    line 48
  5. Distinctive:

    Do this before touching the resume.

    line 52
  6. Distinctive:

    No summary for juniors. A three-line positioning statement for mid and senior people, and for career changers.

    line 81
  7. Distinctive:

    Every bullet: strong verb, what was done, in what context, with what result.

    line 83
  8. Distinctive:

    Use the posting's own terms where they are true.

    line 90
  9. Distinctive:

    Never add a tool, title, date, metric or degree the person does not have.

    line 91
  10. Distinctive:

    Read it aloud. Every sentence that would fit any other company gets cut.

    line 104
  11. Very specific:

    Run references/checklists.md before handing anything over.

    line 119
  12. Distinctive:

    Only when asked or clearly useful:

    line 124
  13. Distinctive:

    Follow-up and thank-you emails: same file

    line 126
  14. Distinctive:

    Do not invent employers, titles, dates, degrees, certifications, tools, metrics, publications, awards, citizenship, visa status, language …

    line 132
  15. Distinctive:

    Do not hide gaps with fake dates.

    line 133
  16. Distinctive:

    Do not stuff keywords, hide white text, or pad the skills list.

    line 134
  17. Distinctive:

    Do not recommend removing or changing information about protected characteristics to game a process.

    line 135
  18. Distinctive:

    Do not promise outcomes. A better application raises the odds.

    line 136
  19. Distinctive:

    Keep the person's voice. A polished letter that sounds like a chatbot is worse than a slightly plain one that sounds like them.

    line 137

≈ “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.

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

Job application kit

One skill for the whole application. It turns a job posting plus a person's real background into documents a recruiter reads in the first ten seconds and keeps reading.

The skill is built around three ideas that every serious source agrees on (Harvard Career Services, r/EngineeringResumes, The Tech Resume Inside Out, ex-FAANG recruiters, German HR practice):

  1. Humans reject resumes, not robots. The ATS is a database. A resume gets skipped because a tired recruiter could not see the fit in five seconds. Write for that recruiter.
  2. Tailored beats polished. A document that could be sent to fifty companies gets treated like it was.
  3. Never invent anything. Every claim will be tested in an interview. Truth is the whole strategy.

What to read, and when

Read SKILL.md fully. Then load only the references the task needs:

TaskRead
Any resume or CV workreferences/resume-format.md, references/writing-bullets.md
Tailoring to a posting, keyword audit, "why no replies"references/ats-and-tailoring.md
Cover letter, motivation letter, application emailreferences/cover-letter.md
Germany, Austria, Switzerland, any German-language applicationreferences/germany-dach.md
US, UK, Ireland, Australia, NZ, India, EU outside DACHreferences/regions.md
Academic, research, PhD, postdoc, professor trackreferences/academic-cv.md
Career change, gaps, visa, over/under qualified, layoffs, returning parentsreferences/special-cases.md
Any prose the user will send (letter, email, summary)references/human-voice.md
Interview prep, follow-ups, recruiter messages, negotiationreferences/interview-and-followup.md
Final check before deliveryreferences/checklists.md

Templates live in assets/. Scripts live in scripts/ and need only the Python standard library.

Step 0: Find out what you are working with

Before writing anything, establish these. Ask only for what is missing; do not run a questionnaire if the answers are already in the chat or in uploaded files.

  • Target: job title, company, and the full posting text (or URL). Without a posting, work generically and say so.
  • Market and language: which country, and does the posting want English or German (or both)?
  • What exists already: current resume, LinkedIn export, old cover letters, references, Zeugnisse.
  • Background: every role with dates, what the company does, what the person actually built or did, numbers where they exist.
  • Constraints: page limit, deadline, salary expectation or start date if the posting asks, visa or work permit status if it matters for the market.
  • Deliverable: chat text, Markdown, .docx, PDF, or a full application folder.

Ask about domain context for every role. "Built web apps" is nothing. "Built the credit-limit engine for a fintech lending app used by 40k SMEs" is a candidate. The single biggest upgrade to any resume is domain context, so dig for it: what industry, what data, who were the users, what changed because of the work.

If the person cannot give numbers, ask for estimates and label them [confirm]. If they still cannot, use scale words (thousands of users, daily releases, team of six).

Step 1: Decode the posting

Do this before touching the resume. Produce a short fit table in chat:

Requirement (from posting)      | Evidence (from candidate)          | Status
Python, production ML           | 3 yrs at X, shipped Y              | strong
Kubernetes                      | used Docker, no k8s                | adjacent
German C1                       | B1                                 | gap

Rules for the table:

  • Split must-have from nice-to-have. Postings put must-haves in the first block and in phrases like "required", "you have", "Sie bringen mit".
  • Note the exact vocabulary the posting uses. Mirror it where it is true.
  • Mark red flags plainly (unpaid trial work, ten roles in one, salary far below market). The user decides.
  • Give a rough fit: apply now, apply with a strong letter that addresses the gap, or skip. Below about 60 percent of must-haves the time is usually better spent elsewhere.

scripts/keyword_audit.py --resume r.md --job jd.md gives a deterministic keyword diff to start from. It is a helper, not a verdict.

Step 2: Write or rewrite the resume

Full detail in references/resume-format.md and references/writing-bullets.md. The rules that matter most:

Layout

  • Single column, no tables for layout, no text boxes, no icons, no photo (except DACH, see the Germany reference), nothing in headers or footers.
  • Calibri or Arial, 10.5 to 11 pt body, name 16 pt, margins about 2 cm. Black text, one accent colour at most.
  • Standard headings only: Experience, Education, Skills, Projects, Publications. Nothing creative.
  • Reverse chronological. Dates right-aligned, "Mar 2022 – Present", never "current".
  • Length: one page under about five years of experience, two pages otherwise. Never three, except academic CVs.

Content

  • No summary for juniors. A three-line positioning statement for mid and senior people, and for career changers.
  • Skills section near the top for technical roles, grouped by category, only things the person can talk about for ten minutes.
  • Every bullet: strong verb, what was done, in what context, with what result. "Cut checkout latency 38 percent by moving image processing to a background queue (Python, Redis)". Aim for measurable results in more than half the bullets.
  • 4 to 6 bullets for the current role, 2 to 3 for roles older than five years. Old or irrelevant jobs get one line.
  • Cut: objectives, "references on request", hobbies (unless they are relevant), Microsoft Office, high school once there is a degree, pronouns, "responsible for", "helped", adjectives about oneself.

Tailoring

  • Move the most relevant bullets to the top of each role.
  • Reorder skill categories so the posting's must-haves are first.
  • Use the posting's own terms where they are true. "CI/CD" if they say CI/CD.
  • Never add a tool, title, date, metric or degree the person does not have. If a keyword is missing and unsupported, it stays missing. Say so in the fit table.

Step 3: Write the cover letter

Full detail in references/cover-letter.md. Short version:

  • Under one page, 200 to 350 words, three or four paragraphs, same header font as the resume.
  • Address a named person if it can be found. Otherwise "Dear Hiring Team" (or "Sehr geehrte Damen und Herren" only as a last resort).
  • Paragraph 1: a specific hook tied to this company or this role. Never "I am writing to express my interest".
  • Paragraph 2: the two or three strongest proofs, with results, mapped to what the posting asks for. Not a rerun of the resume.
  • Paragraph 3: why this company. Something concrete: their product, a recent launch, a team, a paper, a problem they publicly have.
  • Paragraph 4: a plain close. Availability, start date and salary expectation if the posting asked. No begging, no "perfect candidate".
  • Address the obvious question head-on if there is one (gap, relocation, career switch, overqualified). One or two sentences, no apology.
  • Read it aloud. Every sentence that would fit any other company gets cut.

Then run the letter against references/human-voice.md. Recruiters in 2026 read hundreds of AI-written letters a week. The ones that get replies sound like a specific person.

Step 4: Region and language

Germany, Austria and Switzerland have their own conventions and they are where most foreign applicants get filtered out. Read references/germany-dach.md for anything DACH: tabular Lebenslauf, whether to include a photo, personal data lines, Zeugnisse, Bewerbungsmappe as one PDF, Anschreiben letter layout, Gehaltsvorstellung, Eintrittstermin, language levels, and how to present a foreign degree.

For everywhere else read references/regions.md.

Step 5: Build the file, check it, deliver it

  • Deliver text in chat first so the user can react. Only then build files.
  • For .docx use the docx skill if available. Build from a clean single-column structure. Convert to PDF and check the PDF with scripts/check_pdf.py: text must extract, page count must match, name and email must be present, no layout tables.
  • File name: Firstname_Lastname_Resume.pdf, Firstname_Lastname_Cover_Letter.pdf. German: Lebenslauf_Vorname_Nachname.pdf, Anschreiben_Vorname_Nachname.pdf, Bewerbung_Vorname_Nachname_Firma.pdf for a merged Mappe.
  • Run references/checklists.md before handing anything over. It is short and it catches the mistakes that get applications binned.
  • End with a short list of things the user must verify (numbers marked [confirm], dates, spelling of the company and contact name).

Step 6: Optional extras

Only when asked or clearly useful:

  • Interview prep pack and STAR story bank: references/interview-and-followup.md
  • Follow-up and thank-you emails: same file
  • Recruiter or hiring-manager outreach message: same file
  • Application tracker: scripts/job_tracker.py

Rules that never bend

  • Do not invent employers, titles, dates, degrees, certifications, tools, metrics, publications, awards, citizenship, visa status, language levels or references.
  • Do not hide gaps with fake dates. Handle them in the letter or with an honest line on the resume.
  • Do not stuff keywords, hide white text, or pad the skills list. It is detectable and recruiters treat it as lying.
  • Do not recommend removing or changing information about protected characteristics to game a process. Do help remove personal data that is simply irrelevant for the target market.
  • Do not promise outcomes. A better application raises the odds. Nothing removes rejection from a job search, and saying otherwise to the user is a disservice.
  • Keep the person's voice. A polished letter that sounds like a chatbot is worse than a slightly plain one that sounds like them.

Output style

Give the finished draft first, then a few lines on what changed and what needs verifying. Plain English. Short sentences. No bold labels inside the documents, no em dashes, no headings inside a cover letter.

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.