agentleFS
leakyhoseleakyhose/resumekit/.claude/skills/tailor/SKILL.md

tailor

Skill1 starsChanged 3 months agoMITView on GitHub

Tailor the resume to a specific job posting — extract what the posting values, map it against the candidate's bullets, then reorder, re-keyword, and swap content to match. Use when the user shares a job posting, link, or company they are applying to.

10 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use inbox.

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.
  • kv0906Skill

    inbox

    Quick capture mode (with content) or batch processing mode (no content). GTD-style routing of inbox items to proper folders. Use "/inbox thought to capture" or "/inbox" to process.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read rules/core.md, rules/profile.md, rules/style.md, and rules/my-rules.md first if you haven't this session.

    line 8
  2. Distinctive:

    Must-have skills and technologies (repeated or listed as requirements)

    line 20
  3. Very specific:

    Read resume/resume.tex. For each bullet, note which of the posting's keywords and qualities it already demonstrates, which it could …

    line 27

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

Tailoring the resume to a posting

Read rules/core.md, rules/profile.md, rules/style.md, and rules/my-rules.md first if you haven't this session.

Hard rule: never fabricate. Tailoring means re-emphasizing and re-wording real experience, never inventing skills or inflating scope. If the posting wants something the candidate genuinely lacks, say so — that gap is information for the user, not something to paper over.

1. Digest the posting

From the posting (ask for it if not provided), extract:

  • Role, team, seniority
  • Must-have skills and technologies (repeated or listed as requirements)
  • Nice-to-haves
  • Recurring language and values ("ownership", "ships fast", "cross-functional") — this is the vocabulary the resume should echo

2. Inventory the resume

Read resume/resume.tex. For each bullet, note which of the posting's keywords and qualities it already demonstrates, which it could honestly demonstrate with rewording, and which it can't.

3. Propose before editing

Present a tailoring plan and get agreement before touching the file:

  • Reorder: most posting-relevant experience/projects/bullets first (first bullet per role = the one this hiring manager cares about most)
  • Reword: truthful keyword swaps (e.g. their stack's terminology where the candidate's experience genuinely matches)
  • Swap: bullets or projects to bench for this application, and what replaces them
  • Gaps: requirements nothing in the resume covers

4. Apply and verify

  • Suggest a git branch named after the application (e.g. apply/company-role) so the main branch stays the canonical resume.
  • Make the edits, then make check (must PASS) and make render + view the png.
  • Summarize what changed and which posting keywords the resume now hits.

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.