Resume Tailor — JD-Matched Resume & Cover Letter

Customize resumes and generate cover letters based on a specific job description (JD). Use this skill whenever the user wants to tailor their resume to a job...

MIT-0 · Free to use, modify, and redistribute. No attribution required.
1 · 106 · 2 current installs · 2 all-time installs
MIT-0
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (tailoring resumes + cover letters) match the skill's contents: the SKILL.md and reference docs focus on JD parsing, keyword matching, formatting, and writing. There are no declared env vars, binaries, or install steps that are extraneous to this purpose.
Instruction Scope
Instructions stay within the domain: request resume and JD text/files, extract keywords, rewrite resume and a cover letter, and produce gap analysis and tips. Note: the skill expects uploaded files (.docx, .pdf, .txt) and to 'parse' them — as an instruction-only skill there is no code shown for parsing, so actual file handling depends on the platform agent. The SKILL.md explicitly forbids fabrication and limits actions to user-provided content.
Install Mechanism
No install spec, no code files to run, and no external downloads. This is instruction-only, which minimizes on-disk/executable risk.
Credentials
No environment variables, credentials, or config paths are requested. The skill does not ask for unrelated secrets or platform tokens.
Persistence & Privilege
always is false and there are no indications the skill requests persistent system-wide privileges or modifies other skills. The default ability for the agent to invoke the skill autonomously is set to platform defaults (disable-model-invocation: false), which is normal.
Assessment
This skill appears coherent and limited to resume/JD text processing. Before using it: (1) Remove or redact highly sensitive personal data (SSN/national ID, passport number, bank details); resumes often contain DOB, home address, or photos — include only what’s needed for the application. (2) Avoid pasting proprietary/confidential employer data or full private project artifacts. (3) Review the output carefully to ensure nothing was fabricated and all metrics/claims are accurate. (4) Note the skill's source is unknown; if you want stronger assurance, prefer skills from a known publisher or inspect the source/approval history. Finally, remember the platform may handle uploaded files — check platform privacy/storage policies if you’re uploading attachments.

Like a lobster shell, security has layers — review code before you run it.

Current versionv1.0.0
Download zip
ATSvk97drtw40am03gz923yf2bcxq982m1baCVvk97drtw40am03gz923yf2bcxq982m1bacareervk97drtw40am03gz923yf2bcxq982m1bacover-lettervk97drtw40am03gz923yf2bcxq982m1bahiringvk97drtw40am03gz923yf2bcxq982m1bajob-applicationvk97drtw40am03gz923yf2bcxq982m1bajob-searchvk97drtw40am03gz923yf2bcxq982m1balatestvk97drtw40am03gz923yf2bcxq982m1baproductivityvk97drtw40am03gz923yf2bcxq982m1baresumevk97drtw40am03gz923yf2bcxq982m1ba

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

📄 Clawdis

SKILL.md

Resume Tailor

Transform a generic resume into a targeted, compelling job application package — tailored resume + cover letter — matched to a specific job description.

When This Skill Activates

Use this skill when the user provides:

  • A resume (text, file, or paste) + a job description/posting
  • A request to write a cover letter for a specific role
  • A request to optimize/tailor their resume for a job

If the user hasn't provided both resume and JD yet, ask for them before proceeding.


Workflow

Step 1: Gather Inputs

Collect (or request) the following:

  1. Resume – full text or uploaded file (.docx, .pdf, .txt)
  2. Job Description – full JD text, URL, or paste
  3. Target Role/Company – confirm if not obvious from JD
  4. Optional extras – user's preferred tone (formal/casual), language (EN/ZH), or specific aspects to emphasize

If any of these are missing, ask the user before continuing.


Step 2: Analyze the JD

Parse the JD for:

  • Required skills – hard skills, tools, technologies, certifications
  • Preferred skills – nice-to-haves the user can highlight if they have them
  • Key responsibilities – what the role actually does day-to-day
  • Culture signals – tone of JD, company values, keywords that suggest what they value
  • Red flags to address – experience gaps, unusual requirements

Create a mental "keyword map" from these. You will use this to rewrite the resume.


Step 3: Tailor the Resume

Rewrite/restructure the resume with these rules:

Core Principles

  • Mirror the JD's language: use the exact keywords and phrasing from the JD where the user has relevant experience. ATS systems match keywords literally.
  • Lead with relevance: reorder bullet points so the most relevant accomplishments appear first.
  • Quantify everything possible: transform vague bullets into impact statements with metrics.
  • Cut irrelevant content: if something doesn't support this specific application, trim it or remove it.
  • Never fabricate: only use skills/experience the user actually has. If a required skill is missing, note it but don't invent it.

Section-by-section guidance

Summary/Objective

  • Rewrite to mention the target role, company (if desired), and top 2-3 qualifications that match the JD.
  • Keep it to 2-4 sentences.

Work Experience

  • For each role, keep only bullets relevant to the JD.
  • Start bullets with strong action verbs that echo JD language.
  • Add quantified outcomes wherever possible (%, $, time saved, team size, etc.)
  • If the user has experience that's tangential but transferable, frame it using the JD's vocabulary.

Skills Section

  • Reorder to put JD-matched skills first.
  • Add any skills from the JD that the user has but didn't list.
  • Remove skills that are completely irrelevant.

Education / Certifications

  • Highlight relevant coursework, projects, or certifications that match JD requirements.

Step 4: Write the Cover Letter

Structure:

[Opening paragraph]
Hook: mention the role + one strong reason you're excited / a specific thing about the company.
Tie your background to their mission/product briefly.

[Body paragraph 1: "Why me"]
Highlight 2-3 specific accomplishments that directly address their top requirements.
Use metrics. Reference the JD explicitly ("Your posting mentions X — here's my experience with X").

[Body paragraph 2: "Why them" (optional but powerful)]
Show you've done research. Reference a product, initiative, recent news, or company value.
Explain why this role at this company, not just any company.

[Closing paragraph]
Express enthusiasm. State your next step (happy to discuss, available for an interview).
Thank them for their time.

Tone guidelines:

  • Default: professional but personable, not robotic
  • Tech startups: more casual, show personality
  • Finance/law/enterprise: more formal
  • Follow user preferences if specified

Length: 3-4 paragraphs, max 400 words. Hiring managers skim.


Step 5: Output Format

Present results clearly in this order:

  1. Gap Analysis (brief) — list JD requirements the user's resume currently doesn't address well, and how you handled each
  2. Tailored Resume — full rewritten resume in clean markdown or the user's preferred format
  3. Cover Letter — complete, ready-to-send letter
  4. Quick tips (optional) — 2-3 specific things the user should be prepared to discuss in an interview based on the JD

Output Quality Checklist

Before presenting output, verify:

  • JD keywords appear naturally throughout resume (not keyword-stuffed)
  • Each resume bullet starts with an action verb
  • At least 60% of experience bullets have quantifiable outcomes
  • Cover letter mentions company by name and a specific role/detail
  • No fabricated skills or experiences
  • Cover letter is under 400 words
  • Tone is consistent throughout

Edge Cases

User has significant skill gaps: Be honest. Note which requirements they don't meet, suggest how to frame adjacent skills, and recommend whether to apply or upskill first.

JD is vague: Ask the user for more context about the company/team. If not available, make reasonable inferences and note your assumptions.

Multiple JDs: If the user wants to apply to many roles, create a "master resume" with all bullets, then a targeted subset for each role. Document which sections to activate per role type.

No resume provided, starting from scratch: Ask the user for their work history, skills, and education. Build a resume from scratch following modern standards, then tailor it.

Non-English job applications: Adapt language, phrasing norms, and CV format to the target country's conventions. See references/regional-cv-formats.md for country-specific guidance.


Reference Files

  • references/ats-keywords.md — Tips on ATS optimization and keyword matching
  • references/regional-cv-formats.md — Country/region-specific resume conventions (EU, Asia, UK, etc.)
  • references/cover-letter-examples.md — Example cover letters for different industries

Files

4 total
Select a file
Select a file to preview.

Comments

Loading comments…