Career-Ops Job Search Center
career-ops-hq/career-ops
Routes job-search requests to modes for evaluating offers, scanning portals, generating tailored CVs, tracking applications and drafting outreach, starting from a pasted job URL or description.
Write a resume / CV or cover letter tailored to a specific role.
$ npx skills add jezweb/claude-skills --skill resume-cover-letter -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jezweb/claude-skills resume-cover-letter --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jezweb/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/writing/skills/resume-cover-letter .claude/skills/resume-cover-letter && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "resume-cover-letter" agent skill from https://github.com/jezweb/claude-skills/tree/main/plugins/writing/skills/resume-cover-letter into .claude/skills/resume-cover-letter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resume-cover-letter", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jezweb/claude-skills/tree/main/plugins/writing/skills/resume-cover-letterType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jezweb/claude-skills --skill resume-cover-letter -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jezweb/claude-skills resume-cover-letter --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jezweb/claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/writing/skills/resume-cover-letter .agents/skills/resume-cover-letter && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "resume-cover-letter" agent skill from https://github.com/jezweb/claude-skills/tree/main/plugins/writing/skills/resume-cover-letter into .agents/skills/resume-cover-letter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resume-cover-letter", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jezweb/claude-skills --skill resume-cover-letter -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jezweb/claude-skills resume-cover-letter --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jezweb/claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/writing/skills/resume-cover-letter .cursor/skills/resume-cover-letter && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "resume-cover-letter" agent skill from https://github.com/jezweb/claude-skills/tree/main/plugins/writing/skills/resume-cover-letter into .cursor/skills/resume-cover-letter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resume-cover-letter", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jezweb/claude-skills.git --path plugins/writing/skills/resume-cover-letter--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jezweb/claude-skills --skill resume-cover-letter -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jezweb/claude-skills resume-cover-letter --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jezweb/claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/writing/skills/resume-cover-letter .gemini/skills/resume-cover-letter && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "resume-cover-letter" agent skill from https://github.com/jezweb/claude-skills/tree/main/plugins/writing/skills/resume-cover-letter into .gemini/skills/resume-cover-letter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resume-cover-letter", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jezweb/claude-skills resume-cover-letterInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jezweb/claude-skills --skill resume-cover-letter -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jezweb/claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/writing/skills/resume-cover-letter .github/skills/resume-cover-letter && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "resume-cover-letter" agent skill from https://github.com/jezweb/claude-skills/tree/main/plugins/writing/skills/resume-cover-letter into .github/skills/resume-cover-letter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resume-cover-letter", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jezweb/claude-skills --skill resume-cover-letter -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jezweb/claude-skills resume-cover-letter --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jezweb/claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/writing/skills/resume-cover-letter .opencode/skills/resume-cover-letter && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "resume-cover-letter" agent skill from https://github.com/jezweb/claude-skills/tree/main/plugins/writing/skills/resume-cover-letter into .opencode/skills/resume-cover-letter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resume-cover-letter", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
resume-cover-letterWrite a resume / CV or cover letter tailored to a specific role.
Resume Cover Letter is an agent skill from jezweb/claude-skills. 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, career document, applying for a role, or needs help framing their experience for a specific job.
Its SKILL.md is about 3.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Business, Finance & HR, covering Resume and CV writing. The repository describes itself as: Skills for Claude Code CLI such as full stack dev Cloudflare, React, Tailwind v4, and AI integrations. The licence is MIT.
5 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 1260fa7. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Resume Cover Letter loads about 3.1k tokens when it runs. Until then it costs about 98 tokens; SKILL.md has 1,703 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from jezweb/claude-skills at commit 1260fa7, republished under its MIT licence (© jezweb). 1,703 words, ~3,127 tokens.
.claude/skills/resume-cover-letter/SKILL.md (or your agent's skills folder).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.
Gather these inputs. Ask for anything missing:
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.
| 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 |
Adjust based on seniority and what sells the candidate best:
Entry-level / graduate (0-3 years):
Mid-career (3-10 years):
Senior / executive (10+ years):
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:
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".
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.
Applicant Tracking Systems parse resumes before humans see them. Follow these rules:
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] + [what you're looking for].
Three to four paragraphs, under one page. Every paragraph earns its place.
Paragraph 1 — Opening hook: Why this role, why now, why you noticed. Reference something specific about the company or role. No "I am writing to express my interest in the position of..." — that is the most wasted sentence in job applications.
Paragraph 2 — Why you (the match): Two to three specific examples of how your experience maps to their requirements. This is not a resume summary — pick the two strongest matches and give brief context. Use language from the job listing.
Paragraph 3 — Why this company (the fit): Show you have done your homework. Reference their product, mission, recent news, company culture, or a specific project. Explain why this matters to you personally. Generic flattery ("I admire your innovative approach") does not count.
Paragraph 4 — Close: Clear call to action. "I'd welcome the chance to discuss how my experience in X could support your team's work on Y. I'm available for a conversation at your convenience." Confident, not desperate.
Read the job listing and company website to calibrate tone:
| Company type | Tone | Example phrasing |
|---|---|---|
| Startup / tech | Conversational, direct | "I've spent the last 3 years building exactly this kind of thing" |
| Corporate / enterprise | Professional, measured | "My experience in enterprise integration aligns closely with your stated objectives" |
| Government / public sector | Formal, criteria-driven | "I address each of the key selection criteria below" |
| Creative agency | Personality forward | "Your work on the X campaign is what made me pay attention" |
| Non-profit | Mission-aligned | "I've followed your work in X for several years and share your commitment to Y" |
Too generic:
Dear Hiring Manager,
I am writing to express my interest in the Marketing Manager position. I have 5 years of marketing experience and am a strong communicator with excellent organisational skills. I believe I would be a great addition to your team.
Right approach:
Hi Sarah,
Your job listing mentioned you are looking for someone to rebuild the content strategy from the ground up — that is exactly what I did at Redgum Digital over the past two years, taking their blog from 400 monthly visitors to 12,000 and making it their primary lead channel.
The two things that stood out in the listing were the focus on SEO-driven content and the need to work closely with the sales team on case studies. At Redgum, I built both of those functions: a keyword-driven editorial calendar that targeted commercial intent terms, and a case study pipeline where I partnered with account managers to document client wins monthly. Five of those case studies became our top-converting landing pages.
I have been following [Company]'s expansion into the SME market since the product launch in October. The positioning challenge — making enterprise-grade software feel approachable for smaller teams — is something I find genuinely interesting, and it is the kind of messaging work I do best.
I would welcome the chance to talk through how I could help build out your content operation. Happy to chat whenever suits.
Lead with transferable skills, not job titles. The professional summary should bridge the gap: "Project manager transitioning from construction to software delivery — 6 years of managing cross-functional teams, budgets, and tight deadlines." Emphasise skills that translate directly.
Do not hide them or get creative with dates. If there is a gap, briefly explain it in the cover letter (caring responsibilities, study, travel, health — one sentence is enough). On the resume, list any relevant activity during the gap: freelance work, volunteering, courses, personal projects.
The cover letter must address the obvious question: "Why do you want this role?" Be direct about your motivation. Scaling back for work-life balance, pivoting into a new area, genuinely interested in the company — whatever the reason, name it.
Focus on adjacent experience and learning velocity. Show you have done something similar at a smaller scale or in a different context. The cover letter should acknowledge the stretch honestly while demonstrating you have closed similar gaps before.
List the company once with each role as a sub-entry showing clear progression. This signals growth and loyalty.
Deliver the document as clean markdown. If the user needs a formatted file, offer to create it as a .md or .txt that they can paste into their preferred tool (Google Docs, Word, Canva). Do not attempt to generate .docx or .pdf files directly.
For "both" mode, deliver the resume first, then the cover letter, in the same response.
© jezweb, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in plugins/writing/skills/resume-cover-letter of jezweb/claude-skills.
Open the folder on GitHubat commit 1260fa7
Resume Cover Letter next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Resume Cover Letter this skilljezweb/claude-skills | 1.1k | — | ~3.1k | Automated safety check: Pass | MIT | |
| Career-Ops Job Search Centercareer-ops-hq/career-ops | 74k | — | ~3.6k | Automated safety check: Pass | MIT | |
| Reactive Resume Builderreactive-resume/reactive-resume | 44k | — | ~2k | Automated safety check: Pass | MIT | |
| Internship Project Preparation ToolLiuMengxuan04/shushu-internship-tool | 2.1k | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| Resume Tailoringvarunr89/resume-tailoring-skill | 769 | 1 repos | ~8.9k | Automated safety check: Pass | MIT | |
| Offer Negotiationreactive-resume/reactive-resume | 44k | — | ~10k | Automated safety check: Pass | MIT |
career-ops-hq/career-ops
Routes job-search requests to modes for evaluating offers, scanning portals, generating tailored CVs, tracking applications and drafting outreach, starting from a pasted job URL or description.
reactive-resume/reactive-resume
Builds resumes as valid JSON for the open-source Reactive Resume app by interviewing you, and can track job applications through its MCP tools.
LiuMengxuan04/shushu-internship-tool
Turns a target internship job description into a resume-ready, interview-ready project by finding and auditing GitHub projects and drafting resume bullets and interview Q&A.
varunr89/resume-tailoring-skill
A skill your agent uses when creating tailored resumes for job applications - researches company/role, creates optimized templates, conducts branching experience discovery to surface undocumented…
reactive-resume/reactive-resume
Evaluates and negotiates job offers. An agent skill from reactive-resume/reactive-resume.
Rimagination/good-story
A skill your agent uses when the user asks to find, sharpen, evaluate, rewrite, or explain the story in scientific or scholarly materials across disciplines, including manuscripts, grants, paper…
jezweb/claude-skills
Generate custom favicons from logos, text, or brand colours.
jezweb/claude-skills
Set up Tailwind v4 + shadcn/ui themed UI with dark mode. An agent skill from jezweb/claude-skills.
jezweb/claude-skills
Build conversational AI voice agents on the ElevenLabs platform.
jezweb/claude-skills
Test website responsiveness across viewport widths using browser automation.
jezweb/claude-skills
Build MCP servers in Python with FastMCP. An agent skill from jezweb/claude-skills.
jezweb/claude-skills
Prepare and publish GitHub releases. An agent skill from jezweb/claude-skills.
Categories
Write a resume / CV or cover letter tailored to a specific role. Resume Cover Letter is an agent skill from jezweb/claude-skills. Write a resume / CV or cover letter tailored to a specific role.
Resume Cover Letter fits situations like: the user mentions a job application; career document; applying for a role; needs help framing their experience for a specific job.
Run `npx skills add jezweb/claude-skills --skill resume-cover-letter -a claude-code`. Or copy the skill folder (plugins/writing/skills/resume-cover-letter in jezweb/claude-skills) into .claude/skills/resume-cover-letter in your project. Claude Code loads it when a task matches its description.
Run `npx skills add jezweb/claude-skills --skill resume-cover-letter -a codex`. Or copy the skill folder (plugins/writing/skills/resume-cover-letter in jezweb/claude-skills) into .agents/skills/resume-cover-letter in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jezweb/claude-skills --skill resume-cover-letter -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/resume-cover-letter, .gemini/skills/resume-cover-letter, .github/skills/resume-cover-letter and .opencode/skills/resume-cover-letter in your project.
SKILL.md names no scripts, command-line tools or credentials: Resume Cover Letter is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Resume Cover Letter is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.1k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Resume Cover Letter: Career-Ops Job Search Center (career-ops-hq/career-ops, 74k stars), Reactive Resume Builder (reactive-resume/reactive-resume, 44k stars), Internship Project Preparation Tool (LiuMengxuan04/shushu-internship-tool, 2.1k stars) and Resume Tailoring (varunr89/resume-tailoring-skill, 769 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
jezweb (a GitHub user) maintains it in jezweb/claude-skills, which has 1,055 GitHub stars. The repository holds 52 skills in this directory. The repository was last updated on October 9, 2026.
Source: jezweb/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.