mcpbeat

Resume Writing

cosmicstack-labs/resume-writing

ATS optimization, achievement frameworks (STAR, CAR), formatting, tailoring, and portfolio presentation

400 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
365
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/cosmicstack-labs/mercury-agent-skills --skill resume-writing

The instruction itself

8 sections, as written by the author

Resume Writing

Craft resumes that pass ATS filters and impress human reviewers.

ATS Optimization

Must-Do

  • Use standard section headings: Experience, Education, Skills
  • No tables, columns, or graphics in the main content
  • Save as .docx (preferred) or plain PDF (not scanned)
  • Use standard fonts: Arial, Calibri, Helvetica
  • Include keywords from the job description verbatim

Avoid

  • Headers/footers (ATS may miss content there)
  • Icons, logos, or images
  • Text boxes or floating elements
  • Fancy formatting (templates with sidebars often fail ATS)

Achievement Frameworks

STAR (Situation, Task, Action, Result)

Situation: Legacy system had 15s page load times
Task: Reduce to <2s for ecommerce conversion
Action: Implemented CDN caching, lazy loading, DB indexing
Result: Page load reduced to 1.2s, conversion up 23%

CAR (Challenge, Action, Result) — shorter variant

Challenge: 40% customer churn in first 90 days
Action: Built onboarding sequence with 5 touchpoints and milestone tracking
Result: Churn reduced to 12%, NPS improved from 32 to 64

Formatting Rules

  • One page for <10 years experience, two pages max for senior
  • Bullet points: 4-6 per role, 1-2 lines each
  • Quantify everything: %, $, time saved, scale
  • Present tense for current role, past tense for previous

How to use it

Copy the folder

Take cosmicstack-labs/resume-writing from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.