resume-builder

Files (7)

• QUICK_REFERENCE.md
• README.md
• SKILL.md
• cover_letter_template.txt · assets/
• ACTION_VERBS.json · references/
• ATS_KEYWORDS.json · references/
• keyword_matcher.py · scripts/

SKILL.md (first lines)

# Resume Builder

Build or optimize a resume that passes ATS screening, reads compellingly to human recruiters, and is precisely tailored to the target role. Every bullet point should prove impact, not just describe a duty.

## When to Use

- User shares their resume and asks to improve it
- User shares a job description and wants their resume tailored to it
- User describes their work experience and needs help building a resume from scratch
- User says "make my resume better", "tailor this to the job", "I'm not getting callbacks"
- User needs a cover letter to accompany the application

## Inputs

- **Required:** Current resume text, OR a description of work experience
- **Optional via `$ARGUMENTS`:**
  - Target job description (strongly recommended for tailoring)
  - Target role or company name
  - Career level (entry, mid, senior, executive)
  - Output format preference (one-page, two-page, academic CV)

## Process

### Step 1: Audit the Existing Resume

Analyze the provided resume for the following gaps:

**Content gaps:**

- Missing quantified impact (% improvement, revenue generated, users served, time saved)
- Duties written as responsibilities rather than achievements
- Missing skills required by the target job description
- Redundant or irrelevant experience for this role

**ATS gaps:**

- Missing keywords from the job description (job title, required skills, tools, certifications)
- Non-standard section headings that ATS parsers misread (use: Summary, Experience, Education, Skills, Certifications)
- Tables, columns, text boxes, headers/footers that ATS systems cannot parse
- Missing or inconsistent date formatting

**Readability gaps:**

- Bullet points longer than 2 lines
- Inconsistent tense (use past tense for all previous roles, present tense for current role)
- Weak opening verbs (avoid "Responsible for", "Helped with", "Worked on")
- Lack of a compelling professional summary

### Step 2: Keyword Alignment (if job description provided)

- Extract required skills, tools, and qualifications from the job description
- Map each against the resume — mark as Present, Partially Present, or Missing
- Flag the top 5 missing keywords that are critical to include
- Suggest where in the resume each missing keyword can be naturally integrated

### Step 3: Rewrite Bullet Points Using the CAR / XYZ Framework

Every bullet point must follow one of:

- **CAR:** Challenge → Action → Result
  - "Reduced API response time by 40% by introducing Redis caching, enabling the team to support 3× traffic without infrastructure changes"
- **XYZ (Google formula):** Accomplished [X] as measured by [Y], by doing [Z]
  - "Grew enterprise ARR from $2M to $5.1M (155% YoY) by redesigning outbound sales process and hiring 3 account executives"

Rules for rewriting:

- Lead with a strong action verb (Built, Led, Reduced, Increased, Launched, Negotiated, Designed, Automated)
- Include at least one metric per bullet (%, $, time saved, headcount, scale)
- If the user cannot provide exact metrics, use ranges or relative indicators ("~30% reduction", "across a team of 12")
- Cut bullets describing routine tasks with no differentiated impact
- Cap bullets at 2 lines

### Step 4: Write or Improve the Professional Summary

- 3–5 sentences maximum
- Lead with role title + years of experience + most distinctive credential
- Include 2–3 core strengths most relevant to the target role
- Close with what you bring to this specific type of company or challenge
- Never use generic filler ("results-driven professional", "team player", "passionate about...")

### Step 5: Optimize Skills Section

- Group by category: Technical Skills, Tools & Platforms, Methodologies, Languages, Certifications
- Include every tool and skill mentioned in the job description that the user genuinely has
- Remove skills that are universally expected and add no signal (Microsoft Word, Google Search)
- Order within categories by relevance to the target role (most relevant first)

### Step 6: Format for ATS + Human Readability

**Structure:**

1. Contact Info (Name, Email, Phone, LinkedIn, GitHub/Portfolio if relevant)
2. Professional Summary
3. Skills
4. Work Experience (reverse chronological)
5. Education
6. Certifications (if any)
7. Projects / Publications / Awards (if relevant)

**Formatting rules:**

- Single-column layout only (ATS-safe)
- No tables, no text boxes, no headers/footers
- Standard fonts: Calibri, Arial, Garamond (11–12pt body, 14–16pt name)
- Consistent date format: MMM YYYY (e.g., "Jan 2022 – Present")
- Section headings in ALL CAPS or Title Case — one style throughout
- Margins: 0.5–1 inch
- Length: 1 page for <10 years experience; 2 pages acceptable for 10+ years

### Step 7: Generate Cover Letter (if requested or ≥1 job description provided)

Structure:

- **Opening:** Why this company and this role specifically (not generic flattery)
- **Body (2 paragraphs):** Your 2 most relevant achievements directly mapped to the job's key requirements
- **Closing:** Clear call to action + availability for interview
- Tone: Confident, specific, human — matches the company's voice if discernible
- Length: 3–4 short paragraphs, fits one page

From baralmanish/AI-Agent-Skills, MIT.

More from baralmanish/AI-Agent-Skills