agentleFS
zeiynzzeiynz/claude-skills/resume-tailor/SKILL.md

resume-tailor

Skill0 starsChanged 4 months agoMITView on GitHub

Tailor a resume to a specific job posting — rewrite bullet points to mirror the posting's language and priorities, reorder sections by relevance, and flag keyword gaps that would trip an ATS (applicant tracking system) filter. Use whenever the user shares a resume plus a job posting/description and asks to "tailor my resume", "optimize this for the job", "will this pass ATS", "rewrite my bullets for this role", or asks for feedback on a resume against a specific opportunity. Also trigger for general resume review even without a specific posting, defaulting to strong-generalist best practices.

29 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use application-tracker, job-search and 1 more.

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.
  • xiding-codeSkill

    application-tracker

    Automatically log and track all job applications submitted. Use this skill after every application submission to record the details in a tracking spreadsheet and save relevant documents. Also trigger when the user asks "application status", "what have I applied to", "tracking", or wants to review their application history. Maintains a single source of truth for all job search activity.

    Also in 3 projects that use this

  • 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

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 26 edited versions we read keep these.

  • 1

    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:

    If the person doesn't have a number for something, don't invent one — use a concrete scope descriptor instead ("managed a portfolio of 12 …

    line 30

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

Rewrites resume content to match a specific job posting without fabricating experience. The line this skill must never cross: reframe truthfully-held experience in the posting's language — never invent skills, titles, metrics, or responsibilities the person didn't have.

Core principle: mirror, don't fabricate

Job postings and resumes often describe the same underlying work in different vocabulary (the posting says "stakeholder management," the resume says "worked with clients"). This skill's job is to find those true equivalences and rewrite toward the posting's language — not to add capabilities that weren't there. If a required qualification is genuinely absent, say so plainly rather than papering over the gap with vague phrasing.

Workflow

Step 1: Parse the posting for signal

Extract three things from the job description:

  1. Hard requirements (explicitly "required," years of experience, specific tools/certifications)
  2. Repeated language/keywords — terms that appear multiple times or in the first few bullets are usually weighted more heavily by both ATS parsing and the human reviewer's mental model of the role
  3. Implicit priorities — what's listed first in "responsibilities" is usually what the role actually spends the most time on, regardless of title

Step 2: Map resume content to posting priorities

For each posting requirement, find the resume's closest true match. Where a match exists but uses different vocabulary, rewrite the bullet using the posting's terms. Where no match exists, don't force one — flag it as a gap (see Step 4).

Step 3: Rewrite bullets using the results-first pattern

Convert task-description bullets into action + method + measurable result:

  • Weak: "Responsible for managing social media accounts"
  • Strong: "Grew Instagram following 40% in 6 months by shifting to a weekly content calendar and creator partnerships"

If the person doesn't have a number for something, don't invent one — use a concrete scope descriptor instead ("managed a portfolio of 12 enterprise accounts" beats a fabricated percentage).

Step 4: ATS keyword check

List the posting's key terms (tools, certifications, exact job-title language) alongside whether the resume currently contains a matching term. For genuine gaps, tell the user directly — this is where the honesty constraint matters most; a resume that pretends to have a required certification is a liability, not a fix.

Step 5: Section ordering

Recommend reordering (not rewriting) sections so the most relevant experience for this posting appears first — a generalist resume often buries the most relevant role third or fourth.

What this skill will not do

  • Invent job titles, employers, dates, degrees, or certifications
  • Inflate metrics beyond what the user has stated or can reasonably estimate from context they've given
  • Claim proficiency in tools/skills not mentioned by the user anywhere in the conversation

Output format

Present as a before/after per bullet (not a full rewritten resume dumped without context) so the user can see exactly what changed and why, then offer the full tailored version as a follow-up if they want it as a file (use the docx skill for a downloadable version).

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.