agentleFS
Faizee-AsadFaizee-Asad/job-seeker-claude-skills/.claude/skills/resume-optimizer/SKILL.md

resume-optimizer

Skill0 starsChanged 7 months agoMITView on GitHub

Tailor a resume or CV to a specific job description with ATS keyword audit, truthful bullet rewrites, summary rewrite, and gap notes.

16 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

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

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 7

    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 this skill when the user asks to improve, tailor, rewrite, or optimize a resume/CV for a specific role or job description.

    line 8
  2. Distinctive:

    Do not invent experience, metrics, tools, degrees, employers, dates, certifications, or outcomes.

    line 12
  3. Distinctive:

    Use job-description keywords only when they truthfully fit the candidate.

    line 13
  4. Distinctive:

    Keep the result easy to copy into a resume document.

    line 16
  5. Distinctive:

    Read the resume/CV and job description.

    line 20
  6. Distinctive:

    Create an ATS keyword audit:

    line 22
  7. Distinctive:

    Create a role-match matrix.

    line 27

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

Use this skill when the user asks to improve, tailor, rewrite, or optimize a resume/CV for a specific role or job description.

Rules

  • Do not invent experience, metrics, tools, degrees, employers, dates, certifications, or outcomes.
  • Use job-description keywords only when they truthfully fit the candidate.
  • Preserve the candidate's actual career history.
  • Mark missing proof with placeholders such as [add metric if true].
  • Keep the result easy to copy into a resume document.

Workflow

  1. Read the resume/CV and job description.
  2. Identify the target role, company, must-have skills, nice-to-have skills, tools, and business outcomes.
  3. Create an ATS keyword audit:
    • matched terms
    • missing terms
    • unsupported terms
    • alternative phrasing
  4. Create a role-match matrix.
  5. Rewrite the resume headline and summary.
  6. Rewrite the most relevant bullets using action + scope + tool/method + result.
  7. Suggest skills section changes.
  8. List facts the user must verify before submitting.

Output format

# Resume Optimization for [Role] at [Company]

## ATS Keyword Audit

## Role Match Matrix

## Recommended Headline

## Rewritten Summary

## Rewritten Experience Bullets

## Skills Section Suggestions

## Gaps and Honest Bridges

## Verification Checklist

Bullet rewrite pattern

Action verb + scope/context + tool/method + measurable result or business value.

Example:

Built Tableau dashboards for sales and operations teams, helping stakeholders monitor weekly revenue, pipeline, and customer trends.

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.