agentleFS
art2urlart2url/career-agent-skills/skills/resume-customizer/SKILL.md

resume-customizer

Skill9 starsChanged 7 months agoMITView on GitHub

Customize your resume for any job posting — reorder sections, integrate keywords, manage multiple versions, and score your match before applying

3 other projects use a version of this.

Adopted by

Most recently taken up by

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 3 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:

    Use when the user wants to customize their resume for a specific job posting or manage multiple resume versions.

    line 10
  2. Distinctive:

    Job order: If a less recent role is more relevant, consider reordering (keep dates visible)

    line 34
  3. Distinctive:

    Add job description keywords into existing bullets naturally.

    line 39
  4. Distinctive:

    Remove or shrink content that doesn't support this application.

    line 43
  5. Distinctive:

    When the user manages multiple versions:

    line 53
  6. Distinctive:

    Never edit the master directly for a single application

    line 58
  7. Distinctive:

    Always start from the user's real experience

    line 84
  8. Distinctive:

    Don't keyword-stuff — language must read naturally

    line 85
  9. Distinctive:

    Document changes so the user can reference them in interviews

    line 87

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

Resume Customizer

Trigger

Use when the user wants to customize their resume for a specific job posting or manage multiple resume versions.

Keywords: "customize resume", "customize resume for job", "adjust resume", "resume for this job", "target role", "specific position", "resume version", "which resume did I send", "match resume to job", "job-specific resume", "adapt resume", "resume keywords for job", "targeted resume", "resume per job"

Best used after job-fit-analyzer has identified what to emphasize.

Process

Step 1: Identify What to Emphasize

From the job description, extract:

  • Must-have skills — stated as required, appear 3+ times
  • Nice-to-have skills — stated as preferred/bonus
  • Key terminology — exact phrases the company uses
  • Priority competencies — what the role centers on

Step 2: Customize the Summary

Rewrite the professional summary to mirror the job's top 3-4 requirements. Include the exact job title or close variant. Reference the user's most relevant experience.

Step 3: Reorder for Relevance

  • Skills section: Most relevant skills first
  • Experience bullets: Lead each role with the bullet that best matches the target job
  • Job order: If a less recent role is more relevant, consider reordering (keep dates visible)
  • Sections: Move education/certs up if the role emphasizes them

Step 4: Integrate Keywords

Add job description keywords into existing bullets naturally. Use exact phrasing where it truthfully describes the user's work. Place critical keywords in multiple locations (summary, skills, experience).

Step 5: Trim and Focus

Remove or shrink content that doesn't support this application. Every line should earn its space by connecting to what this employer wants.

Customizing vs. Lying

Acceptable: Reordering true information, using the employer's terminology for things you actually did, emphasizing certain achievements, adding context to vague statements.

Not acceptable: Adding skills you don't have, changing numbers, claiming titles or certifications you don't hold, inventing experiences.

Version Management

When the user manages multiple versions:

  • Maintain one master resume with ALL bullets and experiences as source of truth
  • Each customized version pulls from the master
  • Name files: LastName_Role_Company_Date.pdf
  • Track which version went to which company
  • Never edit the master directly for a single application

Output Format

## Customization Plan: [Role] at [Company]

### Summary
**Current:** [original]
**Customized:** [rewritten]

### Skills Reorder
**New order:** [reordered list, additions noted]

### Experience Changes
**[Company/Role]:**
- Lead with: "[most relevant bullet]"
- Modify: "[original]" → "[customized version]"
- Add keyword: "[phrase]" to bullet about [topic]

### Keywords Added: [count]
### Estimated Match Score: [X]%

Rules

  • Always start from the user's real experience
  • Don't keyword-stuff — language must read naturally
  • Maintain ATS compatibility in all customized versions
  • Document changes so the user can reference them in interviews

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.