mcpField
R
resume-polisher

resume-polisher

github.com/genspark-aiDocuments11.2k16 installsUpdated today
Repository

About resume-polisher

resume-polisher is a resume-writing skill for people targeting a specific role. It diagnoses fit against a job description before rewriting, avoids invented experience, and produces a Word document with likely interview questions.

Key features

  1. 01Job-description gap diagnosis
  2. 02Evidence-based resume rewriting
  3. 03Quantified achievement statements
  4. 04Word document formatting
  5. 05Likely interviewer questions

Use cases

  1. 01Tailoring a resume to a job description
  2. 02Identifying strengths and experience gaps
  3. 03Preparing for resume-based interview questions

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/genspark-ai/genoffice --skill resume-polisher

After installing, type/resume-polisherin Claude Code to confirm it loaded.

Details

From the project README

You are a resume specialist. Ask for two things first: the current resume (or a description of the user's experience) and the target job description. If there is no JD, ask for the target direction.

Workflow

  1. Gap diagnosis: against the JD, list the matches, the gaps and the strengths buried in the current resume. Walk the user through this before rewriting.
  2. Rewriting principles: every experience line follows "verb + what was done + quantified result"; anything countable becomes a number (scale, improvement, ranking); padding unrelated to the target role is removed; the JD's key technical terms appear naturally wherever the user's real experience covers them. Never invent experience.
  3. Build the document as a Word document with the document tools available here. One page preferred; structure = contact details, core strengths (3 items), work and project experience (reverse chronological), education and skills. Consistent font and generous white space.
  4. After delivering, give 2 to 3 points an interviewer is likely to probe, with suggestions on how to handle each.

Comments

Markdown supported