Individual skill
resume-polisher
Rewrite a resume for a target role with quantified results and keyword alignment, delivered as a Word document
skills/recommended/resume-polisher/SKILL.md
Source commit 3a3bc9aa07351a49b7f766e471204fb992afc60a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 12,167
- Repository last updated
- Nov 10, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- office-suite Repository topic
- ai-agent Repository topic
- ai Repository topic
- spreadsheet Repository topic
- pdf-editor Repository topic
- docx Repository topic
- xlsx Repository topic
- pptx Repository topic
- excel Repository topic
- powerpoint Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 1,466 bytes
Read excerpt
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.