Content workflow
Job application tailoring
Researches the company, maps every job requirement to evidence on your resume, rewrites the resume for the role with a line-by-line change log and no invented experience, writes a cover letter from verifiable company hooks, checks ATS keyword coverage and preps interview answers.
Running it here
Every step runs here with Claude when you're signed in, and in your own agent.
- TriggerPaste resume and job postPaste {{resume}} and {{job_description}}, name the {{company}}, and add {{seniority}}, {{constraints}} and any {{extra_facts}} that are true but missing from the resume.→ manual
- AgentResearch the companyResearch {{company}} for the role in {{job_description}}. Find: the mission in their own words, main products and customers, business model, news from the last 12 months with dates (launches, funding, leadership changes, layoffs), how they write (tone of their blog, careers page and docs), stated values, and the team this role sits in if that is public. Cite a URL for every fact. If the company name is ambiguous or you can't find the right one, say so and list what you found. End with 3 cover letter hooks: each a specific, recent, verifiable fact about the company that connects to something in {{resume}}.
- PromptMap requirements to evidenceFrom {{job_description}}, list every requirement and mark it must-have or nice-to-have using the post's own signals ('required', 'you have', 'bonus', 'nice to have'). For each, quote the matching line from {{resume}} or {{extra_facts}} and rate it: strong (direct, recent, with a result), weak (related, old, or no result) or missing. Then list the ATS keywords: exact phrases from the post for skills, tools, certifications and the job title, with how many times each appears. Finish with a fit summary: counts of strong, weak and missing must-haves, and the 3 biggest gaps. If the fit is poor for {{seniority}}, say so plainly.
- PromptTailor the resumeRewrite {{resume}} for this job using {{gaps}}. Hard rules: do not add employers, titles, dates, degrees, certifications, tools, numbers or responsibilities that are not in {{resume}} or {{extra_facts}}. Missing requirements stay missing. You may: reorder sections and bullets, cut irrelevant bullets, merge bullets, rewrite wording, and use the job post's exact term where the resume shows the same thing in other words ('Postgres' → 'PostgreSQL'). Start each bullet with a verb and keep any result the original states. Add a 2–3 line summary aimed at the role. Respect {{constraints}}. Return: (0) two lines at the top: 'Target: <the seniority>' and 'Constraints: <the constraints, in one line>'; (1) the full tailored resume as plain text with standard headings (Summary, Experience, Skills, Education); (2) a change log table: Section | Before (exact original text, or 'new') | After | Why (the requirement it serves). Mark any row that uses extra facts with '(from extra facts)'.
- Review loopRecruiter critiqueAct as a recruiter screening for the role named on the draft's 'Target:' line. 1. In the top third of the resume, a reader can see the target role and the 2–3 strongest matching qualifications. 2. Every bullet starts with a verb and states scope or a result; none say 'responsible for'. 3. Check the change log row by row: an 'After' must not contain any number, tool, employer, title, date or claim that is absent from its 'Before', unless the row is marked '(from extra facts)'. Fail any such row; the fix is to revert it to the 'Before' wording. 4. No keyword appears more than 3 times in the resume. 5. Plain text with standard headings; no tables or columns in the resume itself (the change log is separate). 6. The resume meets every item on the draft's 'Constraints:' line (for example, page length). Feedback names the exact line and the fix. Keep the 'Target:' and 'Constraints:' lines and the change log in the revised draft.
- PromptWrite the cover letterWrite a cover letter for the role in {{job_description}} at {{company}}, using {{company_brief}}, {{gaps}} and {{resume_tailored}}. 250–350 words in four short paragraphs: (1) why this company, using one hook from the research with a specific detail; (2–3) the top 3 must-haves, each matched to one piece of resume evidence and its result; (4) if a weak or missing requirement is likely to come up, one honest sentence about it, then a plain close. Match the tone of the company's own writing as described in the research. Use only facts from the resume and {{extra_facts}}. Do not write 'I am writing to apply', 'I believe I would be a great fit', 'passionate', 'dynamic' or 'leverage'.
- PromptATS keyword checkCompare the ATS keywords in {{gaps}} with {{resume}} (before) and {{resume_tailored}} (after). 1. Table: Keyword | Times in post | Before (yes/no) | After (yes/no, and where) | Note. 2. Coverage before and after, as a percentage of must-have keywords and of all keywords. 3. Keywords still missing, split into 'you may have this but it isn't on the resume: confirm before adding' and 'genuine gap'. Do not add them yourself. 4. Format checks on the text, each marked pass or fix: standard section headings, one consistent date format, contact details as plain text at the top, no key information that would sit in a table, column, text box, header or footer. 5. One line of export advice: save as .docx or a text-based PDF (not a scanned image), and keep the plain-text layout when you paste it into a template.
- PromptInterview prepUsing {{gaps}}, {{company_brief}} and {{resume_tailored}}: 1. 8 likely interview questions: 4 on must-haves, 2 probing weak or missing items, 2 about the company or its recent news. For each, name the resume story to use (role and bullet) and give a 3-line STAR outline built only from facts on the resume. 2. 4 questions to ask the interviewer, each tied to something in the research. 3. The one gap to prepare for, with a suggested answer that is honest and does not overclaim.
- ApprovalCheck every changeRead the change log in {{resume_tailored}} line by line: only you know what's true. Then review {{cover_letter}}, {{ats}} and {{prep}}. Approve or edit before sending anything.→ chat
- OutputSave the application packReturn {{resume_tailored}}, {{cover_letter}}, {{ats}}, {{prep}} and {{company_brief}}.→ file
Good for
Job seekers tailoring a resume and cover letter to one role without inventing experience.
Last reviewed
Install as a skill
The whole workflow as one SKILL.md. Install it in Claude Code, Codex or Copilot and ask your agent to run “Job application tailoring”.
Get the job-application-tailoring skillWhat each step does
1. Paste resume and job post (Trigger)
Paste {{resume}} and {{job_description}}, name the {{company}}, and add {{seniority}}, {{constraints}} and any {{extra_facts}} that are true but missing from the resume.
2. Research the company (Agent)
Research {{company}} for the role in {{job_description}}. Find: the mission in their own words, main products and customers, business model, news from the last 12 months with dates (launches, funding, leadership changes, layoffs), how they write (tone of their blog, careers page and docs), stated values, and the team this role sits in if that is public. Cite a URL for every fact. If the company name is ambiguous or you can't find the right one, say so and list what you found. End with 3 cover letter hooks: each a specific, recent, verifiable fact about the company that connects to something in {{resume}}.
3. Map requirements to evidence (Prompt)
From {{job_description}}, list every requirement and mark it must-have or nice-to-have using the post's own signals ('required', 'you have', 'bonus', 'nice to have'). For each, quote the matching line from {{resume}} or {{extra_facts}} and rate it: strong (direct, recent, with a result), weak (related, old, or no result) or missing. Then list the ATS keywords: exact phrases from the post for skills, tools, certifications and the job title, with how many times each appears. Finish with a fit summary: counts of strong, weak and missing must-haves, and the 3 biggest gaps. If the fit is poor for {{seniority}}, say so plainly.
4. Tailor the resume (Prompt)
Rewrite {{resume}} for this job using {{gaps}}. Hard rules: do not add employers, titles, dates, degrees, certifications, tools, numbers or responsibilities that are not in {{resume}} or {{extra_facts}}. Missing requirements stay missing. You may: reorder sections and bullets, cut irrelevant bullets, merge bullets, rewrite wording, and use the job post's exact term where the resume shows the same thing in other words ('Postgres' → 'PostgreSQL'). Start each bullet with a verb and keep any result the original states. Add a 2–3 line summary aimed at the role. Respect {{constraints}}. Return: (0) two lines at the top: 'Target: <the seniority>' and 'Constraints: <the constraints, in one line>'; (1) the full tailored resume as plain text with standard headings (Summary, Experience, Skills, Education); (2) a change log table: Section | Before (exact original text, or 'new') | After | Why (the requirement it serves). Mark any row that uses extra facts with '(from extra facts)'.
5. Recruiter critique (Review loop)
Act as a recruiter screening for the role named on the draft's 'Target:' line. 1. In the top third of the resume, a reader can see the target role and the 2–3 strongest matching qualifications. 2. Every bullet starts with a verb and states scope or a result; none say 'responsible for'. 3. Check the change log row by row: an 'After' must not contain any number, tool, employer, title, date or claim that is absent from its 'Before', unless the row is marked '(from extra facts)'. Fail any such row; the fix is to revert it to the 'Before' wording. 4. No keyword appears more than 3 times in the resume. 5. Plain text with standard headings; no tables or columns in the resume itself (the change log is separate). 6. The resume meets every item on the draft's 'Constraints:' line (for example, page length). Feedback names the exact line and the fix. Keep the 'Target:' and 'Constraints:' lines and the change log in the revised draft.
6. Write the cover letter (Prompt)
Write a cover letter for the role in {{job_description}} at {{company}}, using {{company_brief}}, {{gaps}} and {{resume_tailored}}. 250–350 words in four short paragraphs: (1) why this company, using one hook from the research with a specific detail; (2–3) the top 3 must-haves, each matched to one piece of resume evidence and its result; (4) if a weak or missing requirement is likely to come up, one honest sentence about it, then a plain close. Match the tone of the company's own writing as described in the research. Use only facts from the resume and {{extra_facts}}. Do not write 'I am writing to apply', 'I believe I would be a great fit', 'passionate', 'dynamic' or 'leverage'.
7. ATS keyword check (Prompt)
Compare the ATS keywords in {{gaps}} with {{resume}} (before) and {{resume_tailored}} (after). 1. Table: Keyword | Times in post | Before (yes/no) | After (yes/no, and where) | Note. 2. Coverage before and after, as a percentage of must-have keywords and of all keywords. 3. Keywords still missing, split into 'you may have this but it isn't on the resume: confirm before adding' and 'genuine gap'. Do not add them yourself. 4. Format checks on the text, each marked pass or fix: standard section headings, one consistent date format, contact details as plain text at the top, no key information that would sit in a table, column, text box, header or footer. 5. One line of export advice: save as .docx or a text-based PDF (not a scanned image), and keep the plain-text layout when you paste it into a template.
8. Interview prep (Prompt)
Using {{gaps}}, {{company_brief}} and {{resume_tailored}}: 1. 8 likely interview questions: 4 on must-haves, 2 probing weak or missing items, 2 about the company or its recent news. For each, name the resume story to use (role and bullet) and give a 3-line STAR outline built only from facts on the resume. 2. 4 questions to ask the interviewer, each tied to something in the research. 3. The one gap to prepare for, with a suggested answer that is honest and does not overclaim.
9. Check every change (Approval)
Read the change log in {{resume_tailored}} line by line: only you know what's true. Then review {{cover_letter}}, {{ats}} and {{prep}}. Approve or edit before sending anything.
10. Save the application pack (Output)
Return {{resume_tailored}}, {{cover_letter}}, {{ats}}, {{prep}} and {{company_brief}}.
Use it in your own agent
Paste into ChatGPT, Claude or Gemini. Parallel steps run one after another, and approvals become “wait for my OK”.
You're going to run a multi-step workflow: Job application tailoring.
Inputs:
- resume: Paste your current resume as plain text
- job_description: Paste the full job post, including requirements and 'nice to have'
- company: Linear (linear.app)
- seniority: Senior software engineer, individual contributor
- constraints: Remote, EU only. Keep the resume to 2 pages. No relocation.
- extra_facts: True things not on the resume: led the move to PostgreSQL 15 in 2024; mentor two junior engineers. (or 'none')
Work through these steps in order. Label each step's output with its number. Where a step says to wait for my OK, stop and wait.
1. **Research the company** — Research Linear (linear.app) for the role in Paste the full job post, including requirements and 'nice to have'. Find: the mission in their own words, main products and customers, business model, news from the last 12 months with dates (launches, funding, leadership changes, layoffs), how they write (tone of their blog, careers page and docs), stated values, and the team this role sits in if that is public. Cite a URL for every fact. If the company name is ambiguous or you can't find the right one, say so and list what you found. End with 3 cover letter hooks: each a specific, recent, verifiable fact about the company that connects to something in Paste your current resume as plain text. Save the result as `company_brief`.
2. **Map requirements to evidence** — From Paste the full job post, including requirements and 'nice to have', list every requirement and mark it must-have or nice-to-have using the post's own signals ('required', 'you have', 'bonus', 'nice to have'). For each, quote the matching line from Paste your current resume as plain text or True things not on the resume: led the move to PostgreSQL 15 in 2024; mentor two junior engineers. (or 'none') and rate it: strong (direct, recent, with a result), weak (related, old, or no result) or missing.
Then list the ATS keywords: exact phrases from the post for skills, tools, certifications and the job title, with how many times each appears.
Finish with a fit summary: counts of strong, weak and missing must-haves, and the 3 biggest gaps. If the fit is poor for Senior software engineer, individual contributor, say so plainly. Save the result as `gaps`.
3. **Tailor the resume** — Rewrite Paste your current resume as plain text for this job using {{gaps}}.
Hard rules: do not add employers, titles, dates, degrees, certifications, tools, numbers or responsibilities that are not in Paste your current resume as plain text or True things not on the resume: led the move to PostgreSQL 15 in 2024; mentor two junior engineers. (or 'none'). Missing requirements stay missing.
You may: reorder sections and bullets, cut irrelevant bullets, merge bullets, rewrite wording, and use the job post's exact term where the resume shows the same thing in other words ('Postgres' → 'PostgreSQL'). Start each bullet with a verb and keep any result the original states. Add a 2–3 line summary aimed at the role. Respect Remote, EU only. Keep the resume to 2 pages. No relocation..
Return: (0) two lines at the top: 'Target: <the seniority>' and 'Constraints: <the constraints, in one line>'; (1) the full tailored resume as plain text with standard headings (Summary, Experience, Skills, Education); (2) a change log table: Section | Before (exact original text, or 'new') | After | Why (the requirement it serves). Mark any row that uses extra facts with '(from extra facts)'. Save the result as `resume_tailored`.
4. **Recruiter critique** — Review loop (max 3 passes): Act as a recruiter screening for the role named on the draft's 'Target:' line.
1. In the top third of the resume, a reader can see the target role and the 2–3 strongest matching qualifications.
2. Every bullet starts with a verb and states scope or a result; none say 'responsible for'.
3. Check the change log row by row: an 'After' must not contain any number, tool, employer, title, date or claim that is absent from its 'Before', unless the row is marked '(from extra facts)'. Fail any such row; the fix is to revert it to the 'Before' wording.
4. No keyword appears more than 3 times in the resume.
5. Plain text with standard headings; no tables or columns in the resume itself (the change log is separate).
6. The resume meets every item on the draft's 'Constraints:' line (for example, page length).
Feedback names the exact line and the fix. Keep the 'Target:' and 'Constraints:' lines and the change log in the revised draft. Save the result as `resume_tailored`.
5. **Write the cover letter** — Write a cover letter for the role in Paste the full job post, including requirements and 'nice to have' at Linear (linear.app), using {{company_brief}}, {{gaps}} and {{resume_tailored}}. 250–350 words in four short paragraphs: (1) why this company, using one hook from the research with a specific detail; (2–3) the top 3 must-haves, each matched to one piece of resume evidence and its result; (4) if a weak or missing requirement is likely to come up, one honest sentence about it, then a plain close. Match the tone of the company's own writing as described in the research. Use only facts from the resume and True things not on the resume: led the move to PostgreSQL 15 in 2024; mentor two junior engineers. (or 'none'). Do not write 'I am writing to apply', 'I believe I would be a great fit', 'passionate', 'dynamic' or 'leverage'. Save the result as `cover_letter`.
6. **ATS keyword check** — Compare the ATS keywords in {{gaps}} with Paste your current resume as plain text (before) and {{resume_tailored}} (after).
1. Table: Keyword | Times in post | Before (yes/no) | After (yes/no, and where) | Note.
2. Coverage before and after, as a percentage of must-have keywords and of all keywords.
3. Keywords still missing, split into 'you may have this but it isn't on the resume: confirm before adding' and 'genuine gap'. Do not add them yourself.
4. Format checks on the text, each marked pass or fix: standard section headings, one consistent date format, contact details as plain text at the top, no key information that would sit in a table, column, text box, header or footer.
5. One line of export advice: save as .docx or a text-based PDF (not a scanned image), and keep the plain-text layout when you paste it into a template. Save the result as `ats`.
7. **Interview prep** — Using {{gaps}}, {{company_brief}} and {{resume_tailored}}:
1. 8 likely interview questions: 4 on must-haves, 2 probing weak or missing items, 2 about the company or its recent news. For each, name the resume story to use (role and bullet) and give a 3-line STAR outline built only from facts on the resume.
2. 4 questions to ask the interviewer, each tied to something in the research.
3. The one gap to prepare for, with a suggested answer that is honest and does not overclaim. Save the result as `prep`.
8. **Check every change** — Show me the result and wait for my OK before the next step: Read the change log in {{resume_tailored}} line by line: only you know what's true. Then review {{cover_letter}}, {{ats}} and {{prep}}. Approve or edit before sending anything.
9. **Save the application pack** — Finish: Return {{resume_tailored}}, {{cover_letter}}, {{ats}}, {{prep}} and {{company_brief}}.Want different steps? Open it in the workflow builder.