agentleFS
inspirearuninspirearun/claude-code-for-non-developers/tailor-my-resume/SKILL.md

tailor-my-resume

Skill1 starsChanged 2 months agoMITView on GitHub

Read one job description properly, interview the person about the work behind their bullets, then rewrite their resume for that one job, honestly. Use it when someone says "my resume isn't getting callbacks", "tailor this CV for this job", "make my resume match this job description", "I keep getting rejected", "does my resume pass ATS", "help me apply for this role", "update my CV", or pastes a job posting next to their resume. Also use it when they have applied to 20 roles with the same document and cannot work out why nothing comes back, because sending one generic resume everywhere is the actual problem. Not for writing a cover letter or a LinkedIn profile, and not for judging whether a draft reads well, which is make-it-readable.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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
  1. Distinctive:

    Never invent an answer to fill a gap: If a section stays thin, leave it thin and say so.

    line 53
  2. Distinctive:

    Every bullet becomes something they did, with a result attached where a real one exists.

    line 59
  3. Very specific:

    Before and after examples, including the ones where the honest rewrite is shorter and weaker-looking than the inflated version and still …

    line 69
  4. Distinctive:

    The job title they used, where it is true: If they were a "Growth Ninja" and the posting says Marketing Manager, write Marketing Manager …

    line 90
  5. Distinctive:

    When a role, a project or a number changes, add it to the answers file rather than editing whichever resume is nearest.

    line 111

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

Tailor My Resume

What this is for

Most resumes are a list of duties. They say what the person was responsible for, in the vocabulary of their old employer, written for no job in particular. Then they get sent to 40 jobs unchanged, and the person concludes the market is bad.

Two things are going wrong. The resume does not contain the good material, because the good material was never asked for. And it is not aimed at anything, so the reader has to work out the relevance themselves, and mostly does not bother.

Both are fixable in one sitting. The order below matters: read the job, then interview, then write. Writing before the interview produces a polished version of the same empty bullets.

1. Read the job description properly

Most people skim a posting and match the title. Read it the way the person who wrote it did, which means separating what they had to type from what they actually care about.

Pull out and write down:

  • The named things. Tools, systems, certifications, methods, platforms. These are the words a filtering pass looks for and the words the hiring manager scans for.
  • What repeats. A phrase that appears in the summary, again in the responsibilities and again in the requirements is the job. A line mentioned once near the bottom is somebody's wish.
  • Required against listed. "Must have" and "you will be doing this daily" is different from a bullet in a list of 14. Treat the difference as real, because the employer does.
  • The seniority signals. Whether they want someone who runs the thing or someone who does the thing. "Own", "lead", "define" is a different job from "support", "assist", "execute", even at the same title.
  • The problem behind the posting. Hiring usually starts because something hurts. A posting heavy on reporting and stakeholders is often a team that cannot explain its own results. Name the guess out loud; it shapes what to put first.

The full method, with a worked example of a real posting taken apart, is in references/reading-a-job-ad.md. Read it before the first pass.

2. Interview, because the resume does not contain the good material

This is the heart of the skill, and it is why this is worth an interview rather than a prompt.

A bullet that says "managed social media accounts" is hiding everything worth hiring. How many accounts, for whom, what the numbers were when they took it over and what they were when they left, what broke, what they did about it, what they changed that the next person kept. None of that is in the resume, and all of it is in their head.

Ask one question at a time. Stacked questions get the last one answered and the rest quietly dropped.

Chase the moment, not the responsibility. "What did you do in that role" gets a job description back. "What was the worst week in that job and what did you do" gets something usable.

Press once on every soft answer, then accept what you get.

  • "we grew the audience" becomes "from what to what, over how long?"
  • "a big client" becomes "how big, and can we name them?"
  • "I improved the process" becomes "what took how long before, and how long after?"
  • "a while ago" becomes "which year?"

Press once. Press twice and it becomes an interrogation, and people start inventing numbers to end it. That is worse than having no number.

Accept "I do not know" as a real answer. Plenty of good work was never measured. A bullet with a vivid specific and no number beats a bullet with a number that cannot be defended in a room.

Record their own words where the phrasing is vivid. When someone says "I was the only person who knew where anything was", that line is better than anything assembled out of action verbs, and it is true in a way a rewrite cannot fake. Keep it verbatim in the notes and use it.

Never invent an answer to fill a gap. If a section stays thin, leave it thin and say so. An invented detail reaches the resume, then the interview, and then it is the person sitting there explaining it.

The questions that reliably produce usable material, and the ones that produce nothing, are in references/interview-questions.md.

3. Rewrite for that job, honestly

Every bullet becomes something they did, with a result attached where a real one exists.

Order by relevance to this job, not by time. The experience the posting cares about most gets read first. Within a role, the bullet that matches the top repeated requirement goes at the top of that role.

Use the employer's own word wherever it is genuinely true of their experience. If the posting says "stakeholder management" and the person spent 3 years keeping 6 department heads aligned, write stakeholder management. That is not gaming anything; it is translating true work into the reader's vocabulary.

Where the employer's word does not describe what they did, leave it out. Padding a resume with unearned keywords gets caught by a person about 4 minutes into a conversation, and the gap you were hiding is now a credibility problem instead of a gap.

Cut what this job does not care about. A resume is not a complete record. Older and unrelated roles compress to a line each so the relevant work has room to breathe.

Before and after examples, including the ones where the honest rewrite is shorter and weaker-looking than the inflated version and still better, are in references/bullet-rewrites.md.

The line this skill does not cross

It never invents experience, never inflates a number, and never claims a tool they have not used.

The reason matters more than the rule. A resume optimised into something untrue works, in the narrow sense: it gets them into the room. Then they are in an interview being asked detailed questions about work they did not do, in front of people who do that work daily. They fail, they feel exposed, and they carry that home. The model that wrote the bullet carries none of it. That asymmetry is the whole argument, and it is why this is not negotiable even when the person asks for it directly.

When the job asks for something they do not have, do 2 things. Find the nearest true thing they do have and give it the space it deserves, because adjacent experience is genuinely persuasive when it is real. Then let the gap stand, and name it in the notes file so they walk in ready to answer it rather than hoping nobody asks.

The filtering system, in plain words

Most applications are read by software before a person sees them. It pulls the text out of the file, tries to work out which part is your job history and which part is your education, and matches you against the posting. It is unremarkable software doing an unremarkable job, and most resume advice about it is superstition.

What actually matters, in terms you can act on:

  • Plain headings. Experience, Education, Skills. A heading called "My Journey" is a heading the software cannot place.
  • No text trapped inside tables, text boxes, columns, headers or footers. Text in those places often comes out scrambled or does not come out at all, and a phone number in a header is a phone number nobody has.
  • No text inside images. A logo or a graphic skills chart reads as blank.
  • Real dates in a normal format. Month and year, or year and year. Consistent throughout.
  • A normal file type. A .docx or a straightforward PDF exported from a text document, not a design file, not a scan, not an image.
  • The job title they used, where it is true. If they were a "Growth Ninja" and the posting says Marketing Manager, write Marketing Manager and let the old title sit alongside it.

That is the whole list. Fonts, margins and clever tricks like white keyword text do nothing useful, and hidden text gets people rejected when a human spots it.

What they end up holding

Two files, in a folder they can find again.

  1. The rewritten resume, ready to send.
  2. A short notes file with 3 parts: what changed and why, the gaps between them and this job, and the vivid lines from the interview that did not fit on the page.

Tell them plainly that the second file is often worth more than the first. Every question an interviewer will ask comes from the gaps, and they now have those written down a week early. The lines that did not fit are their answers to "tell me about a time when".

Doing it again for the next job

A job hunt is 20 applications, and nobody sits through 20 interviews with a model. Split the work so only the small half repeats.

The interview answers are reusable. Keep them in the folder as a plain file of everything that came out, numbers, moments, phrasing and all, far longer than any resume could hold. That file is the asset, and it gets better every time something new surfaces.

The tailoring is not reusable. For the next job, read that posting, open the saved answers, and rewrite from the same raw material toward the new target. That takes 15 minutes rather than an hour, and it does not need another interview unless the new job reaches into work never discussed.

When a role, a project or a number changes, add it to the answers file rather than editing whichever resume is nearest. The resumes are outputs. The answers file is the thing worth keeping.

Others in this pack

  • first-build, empty folder to one working thing in an hour.
  • remember-my-rules, interviews them and writes their CLAUDE.md so Claude stops forgetting how they work.
  • prove-it, when Claude says it is done, make it show the receipt.
  • grill-my-plan, before they commit to an approach, find where it breaks.
  • extract-text, pull the words out of a screenshot, a photo or a scanned PDF. Reach for it first when the resume arrives as a scan or a photo.
  • make-it-readable, restructure a draft so people finish reading it.

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.