resume-cover-letter

Name: resume-cover-letter
Author: jezweb

937stars96forks

How to install resume-cover-letter?

jezweb/claude-skills/resume-cover-letter

$npx -y skills add jezweb/claude-skills --skill resume-cover-letter

Installs into the current project.

Summary

Write a resume / CV or cover letter tailored to a specific role. Handles regional format differences (AU/NZ, US, UK), ATS-friendly formatting, achievement-focused bullets, and cover letter structure. Use whenever the user mentions a job application, resume, CV, cover letter, care

Files · 1

View on GitHub

SKILL.md

1	# Resume and Cover Letter Writer
2
3	Produces job application documents: a resume/CV, a cover letter, or both. Every output is tailored to a specific role at a specific company — generic documents are not useful.
4
5	## Before You Start
6
7	Gather these inputs. Ask for anything missing:
8
9	1. Target role — job title, company name, and the job listing or description (paste or URL)
10	2. Mode — "resume", "cover-letter", or "both"
11	3. Region — AU/NZ, US, or UK (affects format, terminology, length expectations)
12	4. Candidate background — current role, years of experience, key skills, education, career highlights
13	5. Special circumstances (if any) — career change, employment gap, overqualified, underqualified, visa/relocation
14
15	If the user provides a job listing, extract the key requirements and tailor everything to match them. Mirror the language the listing uses for skills and responsibilities.
16
17	---
18
19	## Resume / CV
20
21	### Regional Format Differences
22
23	\| Element \| AU/NZ \| US \| UK \|
24	\|---------\|-------\|----\|----\|
25	\| Name \| CV or resume (both accepted) \| Resume \| CV \|
26	\| Length \| 2-3 pages standard \| 1 page (<10 years exp), 2 max \| 2 pages standard \|
27	\| Photo \| No \| No \| No \|
28	\| Date of birth / age \| No \| No \| No \|
29	\| Nationality / visa \| Include if relevant (common in AU/NZ) \| No (discrimination risk) \| Include visa status if applicable \|
30	\| Referees \| "Available on request" is outdated — omit entirely, or list 2 if specifically requested \| Omit \| Omit \|
31	\| Address \| City/state only (no street) \| City/state only \| City only \|
32
33	### Section Order
34
35	Adjust based on seniority and what sells the candidate best:
36
37	Entry-level / graduate (0-3 years):
38	1. Contact details
39	2. Professional summary (3-4 lines)
40	3. Education
41	4. Experience (internships, part-time, volunteer)
42	5. Skills
43	6. Certifications / projects
44
45	Mid-career (3-10 years):
46	1. Contact details
47	2. Professional summary
48	3. Experience
49	4. Skills
50	5. Education
51	6. Certifications
52
53	Senior / executive (10+ years):
54	1. Contact details
55	2. Executive summary
56	3. Key achievements (optional highlight section)
57	4. Experience
58	5. Board / advisory roles (if applicable)
59	6. Education
60	7. Professional memberships
61
62	### Writing Achievement Bullets
63
64	Use CAR format: Challenge (context/problem), Action (what you did), Result (measurable outcome).
65
66	Every bullet should answer: "So what? What changed because of this?"
67
68	Too generic:
69	> Managed social media accounts and created content for the company.
70
71	Right approach (CAR):
72	> Rebuilt the social media strategy for a stagnant B2B account (Challenge), shifting from product-focused posts to customer case studies with a consistent weekly publishing schedule (Action), growing LinkedIn engagement 340% and generating 12 qualified leads in the first quarter (Result).
73
74	Not every bullet needs hard numbers, but aim for at least 60% of bullets to include a measurable result. Acceptable result types:
75	- Percentages (increased, reduced, improved by X%)
76	- Dollar amounts (managed $X budget, saved $X, generated $X revenue)
77	- Volume/scale (team of X, X users, X transactions per day)
78	- Time (reduced from X weeks to Y days, delivered 2 weeks ahead of schedule)
79	- Rankings/ratings (achieved #1, rated 4.8/5, top 10%)
80
81	When the user does not have specific numbers, ask if they can estimate. If not, use qualitative results: "significantly reduced", "consistently exceeded targets", "recognised by leadership for".
82
83	### Action Verbs
84
85	Choose verbs that match the type of contribution:
86
87	\| Category \| Verbs \|
88	\|----------\|-------\|
89	\| Leadership \| Led, directed, managed, oversaw, mentored, championed, established \|
90	\| Creation \| Developed, designed, built, launched, created, implemented, introduced \|
91	\| Improvement \| Increased, improved, streamlined, optimised, reduced, enhanced, modernised \|
92	\| Analysis \| Analysed, evaluated, assessed, identified, researched, investigated \|
93	\| Communication \| Presented, negotiated, facilitated, coordinated, advised, authored \|
94	\| Technical \| Engineered, automated, configured, deployed, integrated, migrated, architected \|
95
96	Avoid weak openers: "Responsible for", "Helped with", "Assisted in", "Involved in", "Participated in". These describe proximity, not contribution.
97
98	### ATS-Friendly Formatting
99
100	Applicant Tracking Systems parse resumes before humans see them. Follow these rules:
101
102	- Use standard section headings: "Experience", "Education", "Skills" — not creative alternatives like "Where I've Made an Impact"
103	- No tables, columns, or text boxes — ATS reads left-to-right, top-to-bottom
104	- No headers or footers — ATS often ignore

People who liked this also viewed

6 picks

Type

resume-cover-letter

937stars96forks

View on GitHub

How to install resume-cover-letter?

jezweb/claude-skills/resume-cover-letter

$npx -y skills add jezweb/claude-skills --skill resume-cover-letter

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Resume and Cover Letter Writer
2
3	Produces job application documents: a resume/CV, a cover letter, or both. Every output is tailored to a specific role at a specific company — generic documents are not useful.
4
5	## Before You Start
6
7	Gather these inputs. Ask for anything missing:
8
9	1. Target role — job title, company name, and the job listing or description (paste or URL)
10	2. Mode — "resume", "cover-letter", or "both"
11	3. Region — AU/NZ, US, or UK (affects format, terminology, length expectations)
12	4. Candidate background — current role, years of experience, key skills, education, career highlights
13	5. Special circumstances (if any) — career change, employment gap, overqualified, underqualified, visa/relocation
14
15	If the user provides a job listing, extract the key requirements and tailor everything to match them. Mirror the language the listing uses for skills and responsibilities.
16
17	---
18
19	## Resume / CV
20
21	### Regional Format Differences
22
23	\| Element \| AU/NZ \| US \| UK \|
24	\|---------\|-------\|----\|----\|
25	\| Name \| CV or resume (both accepted) \| Resume \| CV \|
26	\| Length \| 2-3 pages standard \| 1 page (<10 years exp), 2 max \| 2 pages standard \|
27	\| Photo \| No \| No \| No \|
28	\| Date of birth / age \| No \| No \| No \|
29	\| Nationality / visa \| Include if relevant (common in AU/NZ) \| No (discrimination risk) \| Include visa status if applicable \|
30	\| Referees \| "Available on request" is outdated — omit entirely, or list 2 if specifically requested \| Omit \| Omit \|
31	\| Address \| City/state only (no street) \| City/state only \| City only \|
32
33	### Section Order
34
35	Adjust based on seniority and what sells the candidate best:
36
37	Entry-level / graduate (0-3 years):
38	1. Contact details
39	2. Professional summary (3-4 lines)
40	3. Education
41	4. Experience (internships, part-time, volunteer)
42	5. Skills
43	6. Certifications / projects
44
45	Mid-career (3-10 years):
46	1. Contact details
47	2. Professional summary
48	3. Experience
49	4. Skills
50	5. Education
51	6. Certifications
52
53	Senior / executive (10+ years):
54	1. Contact details
55	2. Executive summary
56	3. Key achievements (optional highlight section)
57	4. Experience
58	5. Board / advisory roles (if applicable)
59	6. Education
60	7. Professional memberships
61
62	### Writing Achievement Bullets
63
64	Use CAR format: Challenge (context/problem), Action (what you did), Result (measurable outcome).
65
66	Every bullet should answer: "So what? What changed because of this?"
67
68	Too generic:
69	> Managed social media accounts and created content for the company.
70
71	Right approach (CAR):
72	> Rebuilt the social media strategy for a stagnant B2B account (Challenge), shifting from product-focused posts to customer case studies with a consistent weekly publishing schedule (Action), growing LinkedIn engagement 340% and generating 12 qualified leads in the first quarter (Result).
73
74	Not every bullet needs hard numbers, but aim for at least 60% of bullets to include a measurable result. Acceptable result types:
75	- Percentages (increased, reduced, improved by X%)
76	- Dollar amounts (managed $X budget, saved $X, generated $X revenue)
77	- Volume/scale (team of X, X users, X transactions per day)
78	- Time (reduced from X weeks to Y days, delivered 2 weeks ahead of schedule)
79	- Rankings/ratings (achieved #1, rated 4.8/5, top 10%)
80
81	When the user does not have specific numbers, ask if they can estimate. If not, use qualitative results: "significantly reduced", "consistently exceeded targets", "recognised by leadership for".
82
83	### Action Verbs
84
85	Choose verbs that match the type of contribution:
86
87	\| Category \| Verbs \|
88	\|----------\|-------\|
89	\| Leadership \| Led, directed, managed, oversaw, mentored, championed, established \|
90	\| Creation \| Developed, designed, built, launched, created, implemented, introduced \|
91	\| Improvement \| Increased, improved, streamlined, optimised, reduced, enhanced, modernised \|
92	\| Analysis \| Analysed, evaluated, assessed, identified, researched, investigated \|
93	\| Communication \| Presented, negotiated, facilitated, coordinated, advised, authored \|
94	\| Technical \| Engineered, automated, configured, deployed, integrated, migrated, architected \|
95
96	Avoid weak openers: "Responsible for", "Helped with", "Assisted in", "Involved in", "Participated in". These describe proximity, not contribution.
97
98	### ATS-Friendly Formatting
99
100	Applicant Tracking Systems parse resumes before humans see them. Follow these rules:
101
102	- Use standard section headings: "Experience", "Education", "Skills" — not creative alternatives like "Where I've Made an Impact"
103	- No tables, columns, or text boxes — ATS reads left-to-right, top-to-bottom
104	- No headers or footers — ATS often ignore

People who liked this also viewed

6 picks

Type