resume-formatter

paramchoudhary/resumeskills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/paramchoudhary/resumeskills --skill resume-formatter
0 commentsdiscussion
summary

Use this skill when the user:

skill.md

Resume Formatter

When to Use This Skill

Use this skill when the user:

  • Needs help with resume layout and formatting
  • Has a messy or hard-to-read resume
  • Wants to ensure ATS compatibility through formatting
  • Needs a clean, professional design
  • Mentions: "format resume", "resume layout", "resume design", "clean resume", "professional format"

Core Capabilities

  • Structure resumes for optimal readability
  • Ensure ATS compatibility through formatting
  • Create visual hierarchy
  • Optimize white space and margins
  • Select appropriate fonts and sizes
  • Balance aesthetic appeal with functionality

Formatting Fundamentals

The Dual Audience Challenge

Your resume must work for:

  1. ATS (Applicant Tracking Systems) - Robots that parse text
  2. Human Readers - Recruiters who scan quickly

The Solution: Clean, simple formatting that satisfies both.

Document Setup

Page Length

  • Entry Level (0-5 years): 1 page
  • Mid-Level (5-15 years): 1-2 pages
  • Senior/Executive (15+ years): 2 pages (max 3 for executives)

Margins

  • Recommended: 0.5" - 1" all sides
  • Minimum: 0.5" (don't go smaller)
  • Maximum: 1" (don't waste space)

Font Selection

Safe, ATS-Friendly Fonts:

  • Sans-serif: Arial, Calibri, Helvetica, Verdana
  • Serif: Times New Roman, Georgia, Garamond

Font Sizes:

  • Name: 16-20pt
  • Section Headers: 12-14pt
  • Body Text: 10-12pt
  • Minimum readable: 10pt

Spacing

  • Line spacing: 1.0 to 1.15
  • Space after paragraphs: 6-12pt
  • Section spacing: 12-16pt between sections

ATS-Safe Formatting Rules

DO:

  • ✅ Use standard fonts
  • ✅ Use simple bullet points (•, -, *)
  • ✅ Use bold and italic sparingly
  • ✅ Use standard section headers
  • ✅ Save as .docx or text-based .pdf
  • ✅ Put contact info in body (not header)
  • ✅ Use single column layout
  • ✅ Use consistent formatting throughout

DON'T:

  • ❌ Use tables (except simple ones for contact info)
  • ❌ Use text boxes
  • ❌ Use columns (multi-column layouts)
  • ❌ Use headers/footers for important info
  • ❌ Use images or graphics
  • ❌ Use unusual fonts
  • ❌ Use skill bars or progress indicators
  • ❌ Use special characters or emojis
  • ❌ Use color for essential information

Section Organization

Standard Section Order

1. Contact Information
2. Professional Summary (optional)
3. Skills/Technical Skills
4. Professional Experience
5. Education
6. Certifications (if relevant)
7. Additional (volunteer, languages, etc.)

Section Header Formatting

ATS-Recognized Headers:

  • PROFESSIONAL EXPERIENCE or WORK EXPERIENCE
  • EDUCATION
  • SKILLS or TECHNICAL SKILLS
  • PROFESSIONAL SUMMARY or SUMMARY
  • CERTIFICATIONS
  • PROJECTS

Format Options:

PROFESSIONAL EXPERIENCE
━━━━━━━━━━━━━━━━━━━━━━

or

Professional Experience
_______________________

or

PROFESSIONAL EXPERIENCE

Contact Information Layout

Recommended Format

JOHN SMITH
[email protected] | (555) 123-4567 | linkedin.com/in/johnsmith
San Francisco, CA

Alternative Format

JOHN SMITH
San Francisco, CA
[email protected] | (555) 123-4567
LinkedIn: linkedin.com/in/johnsmith | GitHub: github.com/johnsmith

What to Include

  • ✅ Full name
  • ✅ Professional email
  • ✅ Phone number
  • ✅ City, State (no full address needed)
  • ✅ LinkedIn URL
  • ✅ Portfolio/GitHub (if relevant)

What to Exclude

  • ❌ Full street address
  • ❌ Photo
  • ❌ Date of birth
  • ❌ Marital status
  • ❌ Multiple phone numbers
  • ❌ Personal social media

Experience Section Formatting

Standard Format

COMPANY NAME | City, ST
Job Title | Month Year - Month Year

• Achievement bullet with metrics and results
• Achievement bullet with metrics and results
• Achievement bullet with metrics and results

Alternative Format

Job Title
COMPANY NAME, City, ST                    Month Year - Month Year

• Achievement bullet with metrics and results
• Achievement bullet with metrics and results

Date Formatting

  • Consistent format: Use same format throughout
  • Recommended: Month Year (Jan 2020 - Present)
  • Also acceptable: MM/YYYY (01/2020 - Present)
  • Avoid: Full dates (January 15, 2020)

Bullet Point Guidelines

  • Length: 1-2 lines each
  • Format: Start with action verb, end with result
  • Quantity: 3-6 bullets per role (more for recent, fewer for old)
  • Symbol: Use standard bullets (•, -, *)

Skills Section Formatting

Option 1: Simple List

SKILLS
Python, JavaScript, SQL, React, Node.js, AWS, Docker, Git, Agile, JIRA

Option 2: Categorized

TECHNICAL SKILLS
Languages: Python, JavaScript, TypeScript, SQL
Frameworks: React, Node.js, Django, Flask
Tools: AWS, Docker, Kubernetes, Git, Jenkins

Option 3: Columns (Careful with ATS)

SKILLS
Languages        Frameworks       Tools
Python           React            AWS
JavaScript       Node.js          Docker
SQL              Django           Git

Note: Multi-column layouts may cause ATS issues. Test before using.

Education Section Formatting

Standard Format

EDUCATION
Bachelor of Science in Computer Science
University of California, Berkeley | 2018
GPA: 3.8/4.0 (include if 3.5+)

With Honors/Details

EDUCATION
MBA, Finance & Strategy | Stanford Graduate School of Business | 2020
• Graduated with Distinction
• Relevant Coursework: Corporate Finance, M&A Strategy

Visual Hierarchy Principles

Hierarchy Order

  1. Name - Largest, most prominent
  2. Section Headers - Clear divisions
  3. Job Titles/Company Names - Easy to scan
  4. Bullet Points - The details

Creating Hierarchy

  • Use font SIZE to create levels
  • Use BOLD for emphasis (names, titles, headers)
  • Use CAPS for section headers
  • Use consistent spacing to separate sections

White Space Management

Good White Space:

  • Between sections (clear separation)
  • After headings (visual breathing room)
  • Between bullets (don't cram)
  • Around margins (frame the content)

Bad White Space:

  • Huge gaps between sections
  • Inconsistent spacing
  • Half-empty pages
  • Excessive margins eating space

Common Formatting Mistakes

Mistake 1: Wall of Text

Problem: Dense paragraphs with no bullets Solution: Use bullet points, keep paragraphs short

Mistake 2: Inconsistent Formatting

Problem: Different fonts, sizes, or styles throughout Solution: Pick one format and stick to it

Mistake 3: Trying to Be Creative

Problem: Fancy designs that break ATS Solution: Save creativity for portfolio, not resume

Mistake 4: Too Much Information

Problem: Cramming everything onto one page Solution: Edit ruthlessly, prioritize relevance

Mistake 5: Not Enough Information

Problem: Half-page resume with massive margins Solution: Add detail, reduce margins (to 0.5")

File Format Guidelines

For Online Applications

  • .docx - Best for ATS parsing
  • .pdf - Good if created from Word (not scanned)

For Email/Direct Send

  • .pdf - Preserves formatting

File Naming

FirstName_LastName_Resume.pdf
JohnSmith_Resume_ProductManager.pdf

Avoid:

  • resume_final_v2_updated_FINAL.docx
  • resume (1).pdf
  • Untitled document.docx

Output Format

When formatting a resume:

# RESUME FORMATTING REVIEW

## Current Issues
- [ ] [Issue 1]
- [ ] [Issue 2]
- [ ] [Issue 3]

## Recommended Changes

### Document Setup
- Margins: [Current] → [Recommended]
- Font: [Current] → [Recommended]
- Font sizes: [Current] → [Recommended]

### Section Order
**Current:** [Current order]
**Recommended:** [New order and why]

### Visual Improvements
- [Specific change 1]
- [Specific change 2]

### ATS Compatibility Fixes
- [Fix 1]
- [Fix 2]

## Before/After Preview

### Before:
[Description or example of current formatting]

### After:
[Description or example of improved formatting]

Quick Formatting Checklist

Before submitting any resume:

  • ✅ One page (or two if warranted)
  • ✅ Standard font (10-12pt body)
  • ✅ Consistent formatting throughout
  • ✅ Clear section headers
  • ✅ Appropriate white space
  • ✅ No tables, text boxes, or columns
  • ✅ Contact info in body (not header)
  • ✅ Saved as .docx or .pdf
  • ✅ Proper file name
  • ✅ Proofread for consistency
how to use resume-formatter

How to use resume-formatter on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add resume-formatter
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/paramchoudhary/resumeskills --skill resume-formatter

The skills CLI fetches resume-formatter from GitHub repository paramchoudhary/resumeskills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/resume-formatter

Reload or restart Cursor to activate resume-formatter. Access the skill through slash commands (e.g., /resume-formatter) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.541 reviews
  • James Johnson· Dec 24, 2024

    Registry listing for resume-formatter matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Dhruvi Jain· Dec 20, 2024

    Useful defaults in resume-formatter — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Tariq Martinez· Dec 16, 2024

    resume-formatter is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Nikhil Abbas· Dec 4, 2024

    resume-formatter fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Oshnikdeep· Nov 11, 2024

    resume-formatter is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Henry Torres· Nov 7, 2024

    Useful defaults in resume-formatter — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Ishan Garcia· Oct 22, 2024

    I recommend resume-formatter for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Ganesh Mohane· Oct 2, 2024

    Keeps context tight: resume-formatter is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Sakshi Patil· Sep 21, 2024

    resume-formatter has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Arya Menon· Sep 13, 2024

    resume-formatter fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

showing 1-10 of 41

1 / 5