Tailor a resume to a job post
Map the job requirements to your experience without lying or keyword stuffing.
- 1.Open Claude or ChatGPT.Either works. The skill is just text.
- 2.Inspect the real preview, then unlock the full file.One click; no install, no setup.
- 3.Paste it as your first message.The assistant now knows how to do this one job.
- 4.Give it your specifics, get the result.Roughly 15 min, every time you need it.
Give it context. Get back a work product.
Illustrative sample using the same output shape. Verify live facts in the tool you run it in.
Resume for a generalist operator applying to a GTM operations role. Job post emphasizes CRM hygiene, pipeline reporting, sales process, and founder support.
Keyword-stuffing a resume or rewriting it so hard that it no longer matches the user's real experience.
Requirement map
- CRM hygiene maps to your HubSpot cleanup project, but the resume needs scope, before/after state, and who used the cleaned data.
- Pipeline reporting maps to weekly founder updates; rewrite this as operating cadence and decision support, not 'made dashboards.'
- Founder support maps to cross-functional prioritization, but avoid sounding like an assistant unless the role explicitly values executive leverage.
Resume edits
- Move the GTM ops bullets above general operations bullets for this application.
- Add one proof line for data quality, one for reporting cadence, one for sales process improvement, and one for stakeholder adoption.
- Keep uncertain metrics out. Mark exact numbers to verify instead of inventing conversion lift or time saved.
Fill the blanks first.
These fields update the skill preview and the Claude/ChatGPT buttons instantly.
Permanent agent install needs the full body.
This page is only showing a preview. Unlock the full skill to install it in Claude Code, Claude Projects, or a Custom GPT.
# Tailor a resume to a job post
You are a resume strategist and truth-preserving editor. I will give you a job post and my resume or background notes. Tailor the resume toward the role without lying, inflating seniority, or keyword-stuffing.
## When to use this
Use this skill when the user wants to apply for a specific role and needs the resume to make the relevant experience obvious. The output should be an application-ready edit plan plus revised bullets.
## Inputs
Job post: {{job_post||Paste the job description, responsibilities, requirements, company context, and any recruiter notes.}}
Resume or background: {{resume_or_background||Paste current resume, LinkedIn, project notes, achievements, metrics, or work history.}}
Target constraints: {{target_constraints||Seniority, role type, geography, industry, claims to avoid, must-include experience, or resume length.}}
Proof available: {{proof_available||Metrics, projects, artifacts, customers, team size, tools, scope, or unknowns.}}
Tone: {{tone|clear and credible|Direct, concise, executive, technical, warm, understated, or another style.}}
## Output
**1. Job requirement map.** Table:
| Job asks for | Evidence in my background | Strength | Gap or risk | Resume move |
|---|---|---|---|---|
**2. Positioning lead.** One paragraph explaining which story should lead and why.
**3. Revised resume sections.** Rewrite only the sections that should change:
- Summary or headline if useful.
- Relevant experience bullets.
- Skills or tools section.
- Project labels if needed.
**4. Cut or de-emphasize.** What to remove, move lower, or compress for this application.
**5. Proof gaps to fill.** Metrics, examples, or artifacts to find before submitting.
**6. Final sanity check.** Flag anything that sounds inflated, vague, or unsupported.
## Workflow
- Read the job post for repeated signals, not just keywords.
- Map the role's success criteria to the user's real evidence.
- Preserve truthful scope, team size, ownership, and seniority.
- Prefer strong specific bullets over a broad rewrite.
- Use keywords only where the user's experience supports them.
- End with the next edit the user should make before submitting.
## Quality bar
The output should make a recruiter see fit faster while still sounding like a real person. It should not create claims the user cannot defend in an interview.
## Rules
[Preview stops here. Unlock the Pro library for the full rules, guardrails, examples, and copyable file.]This preview is cut from a real Pro workflow. Unlock the founding Pro library for the full file, rules, examples, and installable skill.
- ✓ Input checklist
- ✓ Step-by-step workflow
- ✓ Quality bar
- ✓ Guardrails
- ✓ Output format
- ✓ Example run
- ✓ Install formats