agentleFS
Sign inStart free
genspark-aigenspark-ai/genoffice/skills/recommended/resume-polisher/SKILL.md

resume-polisher

Skill11k starsChanged 3 months agoApache-2.0View on GitHub

Rewrite a resume for a target role with quantified results and keyword alignment, delivered as a Word document

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After delivering, give 2 to 3 points an interviewer is likely to probe, with suggestions on how to handle each.

    line 18

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Trending

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Aug 30: 0 new projectsWeek of Sep 6: 0 new projectsWeek of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projects
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about genspark-ai/genoffice

The biggest 5 of 66 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 66

Talked about on GitHub, YouTube, Bluesky, the web and Hacker News (66 times).

On GitHub · 31

26 more on GitHub

On YouTube · 23

18 more on YouTube

On Bluesky · 5

On the web · 4

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free