Skip to main content
ClaudeWave
EN, English
Skill1.1k repo starsupdated 19d ago

resume-cover-letter

This skill generates tailored resumes, CVs, or cover letters for specific job applications, with support for regional formatting standards (AU/NZ, US, UK), ATS-friendly layouts, and achievement-focused bullet points using the CAR method. Use it when a user is applying for a role and needs a polished, targeted job application document that mirrors the language and requirements of the actual job listing.

Install in Claude Code
Copy
git clone --depth 1 https://github.com/jezweb/claude-skills /tmp/resume-cover-letter && cp -r /tmp/resume-cover-letter/plugins/writing/skills/resume-cover-letter ~/.claude/skills/resume-cover-letter
Then start a new Claude Code session; the skill loads automatically.

SKILL.md

# Resume and Cover Letter Writer

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.

## Before You Start

Gather these inputs. Ask for anything missing:

1. **Target role** — job title, company name, and the job listing or description (paste or URL)
2. **Mode** — "resume", "cover-letter", or "both"
3. **Region** — AU/NZ, US, or UK (affects format, terminology, length expectations)
4. **Candidate background** — current role, years of experience, key skills, education, career highlights
5. **Special circumstances** (if any) — career change, employment gap, overqualified, underqualified, visa/relocation

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.

---

## Resume / CV

### Regional Format Differences

| Element | AU/NZ | US | UK |
|---------|-------|----|----|
| Name | CV or resume (both accepted) | Resume | CV |
| Length | 2-3 pages standard | 1 page (<10 years exp), 2 max | 2 pages standard |
| Photo | No | No | No |
| Date of birth / age | No | No | No |
| Nationality / visa | Include if relevant (common in AU/NZ) | No (discrimination risk) | Include visa status if applicable |
| Referees | "Available on request" is outdated — omit entirely, or list 2 if specifically requested | Omit | Omit |
| Address | City/state only (no street) | City/state only | City only |

### Section Order

Adjust based on seniority and what sells the candidate best:

**Entry-level / graduate (0-3 years):**
1. Contact details
2. Professional summary (3-4 lines)
3. Education
4. Experience (internships, part-time, volunteer)
5. Skills
6. Certifications / projects

**Mid-career (3-10 years):**
1. Contact details
2. Professional summary
3. Experience
4. Skills
5. Education
6. Certifications

**Senior / executive (10+ years):**
1. Contact details
2. Executive summary
3. Key achievements (optional highlight section)
4. Experience
5. Board / advisory roles (if applicable)
6. Education
7. Professional memberships

### Writing Achievement Bullets

Use CAR format: **Challenge** (context/problem), **Action** (what you did), **Result** (measurable outcome).

Every bullet should answer: "So what? What changed because of this?"

**Too generic:**
> Managed social media accounts and created content for the company.

**Right approach (CAR):**
> 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).

Not every bullet needs hard numbers, but aim for at least 60% of bullets to include a measurable result. Acceptable result types:
- Percentages (increased, reduced, improved by X%)
- Dollar amounts (managed $X budget, saved $X, generated $X revenue)
- Volume/scale (team of X, X users, X transactions per day)
- Time (reduced from X weeks to Y days, delivered 2 weeks ahead of schedule)
- Rankings/ratings (achieved #1, rated 4.8/5, top 10%)

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".

### Action Verbs

Choose verbs that match the type of contribution:

| Category | Verbs |
|----------|-------|
| Leadership | Led, directed, managed, oversaw, mentored, championed, established |
| Creation | Developed, designed, built, launched, created, implemented, introduced |
| Improvement | Increased, improved, streamlined, optimised, reduced, enhanced, modernised |
| Analysis | Analysed, evaluated, assessed, identified, researched, investigated |
| Communication | Presented, negotiated, facilitated, coordinated, advised, authored |
| Technical | Engineered, automated, configured, deployed, integrated, migrated, architected |

Avoid weak openers: "Responsible for", "Helped with", "Assisted in", "Involved in", "Participated in". These describe proximity, not contribution.

### ATS-Friendly Formatting

Applicant Tracking Systems parse resumes before humans see them. Follow these rules:

- Use standard section headings: "Experience", "Education", "Skills" — not creative alternatives like "Where I've Made an Impact"
- No tables, columns, or text boxes — ATS reads left-to-right, top-to-bottom
- No headers or footers — ATS often ignores these entirely
- No images, icons, or graphics
- Use standard fonts (Calibri, Arial, Garamond, Georgia)
- File format: PDF unless the listing specifically requests .docx
- Include keywords from the job listing naturally in context — not keyword-stuffed in a hidden block
- Spell out acronyms on first use, then abbreviate: "Search Engine Optimisation (SEO)"

### What to Omit

- "References available upon request" — assumed and wastes space
- Objective statements — replaced by professional summaries years ago
- Every job since high school — include only relevant roles (last 10-15 years)
- High school education (if you have a degree)
- Hobbies/interests — unless directly relevant to the role or culture
- Salary expectations — never on the resume itself
- Reasons for leaving previous roles

### Professional Summary

3-4 lines at the top. Not a personality description — a positioning statement.

**Too vague:**
> Motivated professional with strong communication skills and a passion for technology seeking a challenging role.

**Right approach:**
> Operations manager with 8 years in logistics and supply chain for mid-market retailers. Track record of reducing fulfilment costs (cut 22% at current role) while maintaining 99.4% on-time delivery. Looking to bring that operational discipline to a high-growth e-commerce environment.

Formula: [Role identity] + [years/domain] + [signature achievement or strength]
ai-image-generatorSkill

Generate AI images using Gemini or GPT APIs directly. Covers model selection (Gemini for scenes; GPT Image 2 for text rendering, batch variations, multi-reference compositing; GPT Image 1.5 for transparent icons), the 5-part prompting framework, API calling patterns, multi-turn editing, and quality assurance. Produces photorealistic scenes, icons, illustrations, OG images, posters, infographics, and product shots. Use when building websites that need images, creating marketing assets, or generating visual content. Triggers: 'generate image', 'ai image', 'create hero image', 'make an icon', 'generate illustration', 'create og image', 'poster', 'infographic', 'image variations', 'gpt-image-2', 'ai art', 'image generation'.

app-docsSkill

Generate complete user documentation for a web app with screenshots. Browses the app via browser automation, screenshots every screen, and produces a structured user guide with step-by-step instructions, annotated screenshots, workflow diagrams, and reference tables. Supports quick (key screens), standard (all pages), thorough (every state and flow), and exhaustive (publishable documentation suite). Triggers: 'document the app', 'user guide', 'app documentation', 'screenshot docs', 'generate user docs', 'help docs', 'how-to guide', 'write the docs'.

aussie-business-englishSkill

Australian business English for professional writing — warm, direct, EN-AU spelling (colour, organise, centre), no filler words. Use whenever the user is writing for an Australian audience: emails, chat messages, proposals, client communications, blog posts, web copy, or any business writing. Apply to drafting, editing, and tone-checking professional text.

award-applicationSkill

Write compelling award submissions, grant applications, and competition entries. Maps achievements to selection criteria using evidence-based narratives. Use whenever the user is applying for a business award (Telstra, chamber of commerce, industry awards), a grant, a competition, or any submission demonstrating merit against defined criteria.

brains-trustSkill

Get a second opinion from leading AI models on code, architecture, strategy, prompting, or anything. Queries models via OpenRouter, Gemini, or OpenAI APIs. Supports single opinion, multi-model consensus, and devil's advocate patterns. Use whenever the user says 'brains trust', 'second opinion', 'ask gemini', 'ask gpt', 'peer review', 'consult another model', 'challenge this', or 'devil's advocate'.

cloudflare-apiSkill

Hit the Cloudflare REST API directly for operations that wrangler and MCP can't handle well. Bulk DNS, custom hostnames, email routing, cache purge, WAF rules, redirect rules, zone settings, Worker routes, D1 cross-database queries, R2 bulk operations, KV bulk read/write, Vectorize queries, Queues, and fleet-wide resource audits. Produces curl commands or scripts. Triggers: 'cloudflare api', 'bulk dns', 'custom hostname', 'email routing', 'cache purge', 'waf rule', 'd1 query', 'r2 bucket', 'kv bulk', 'vectorize query', 'audit resources', 'fleet operation'.

cloudflare-worker-builderSkill

Scaffold and deploy Cloudflare Workers with Hono routing, Vite plugin, and Static Assets. Describe project, scaffold structure, configure bindings, deploy. Use whenever the user wants to create a Worker project, set up Hono on Cloudflare, configure D1 / R2 / KV / Queues bindings, or troubleshoot Worker export syntax, API route conflicts, HMR issues, or deployment failures.

codex-reviewSkill

Run an independent code review using the OpenAI Codex CLI in headless mode. Gets a second opinion from a different model family (the current Codex models) on recent changes, a PR, a commit, or the whole app — covering bugs, regressions, security, data consistency, UX/state bugs, performance risks, and testing gaps. Saves a severity-prioritised report to .jez/reviews/. Triggers: 'codex review', 'review with codex', 'independent code review', 'what does codex think', 'get codex to review'.