resume
Skill0 starsChanged 3 days agoMITView on GitHub
Resume review and optimization in one skill: diagnose quality (expression, structure, credibility, JD match, truthfulness, ATS parseability) and polish/improve an existing resume while preserving facts and, optionally, a designed PDF layout. Merged from resume-review + resume-polish. Triggers on: review my resume, rate my resume, check my resume, polish my resume, optimize my resume, improve this resume, rewrite for a job.
64 other projects use a version of this.
Adopted by
Most recently taken up by
- optiflowic/keyturntheir own version, first seen Nov 16, 2026
- DeepExtrema/Tesseracttheir own version, first seen Nov 16, 2026
- kele-dev/Claude-Orchestrator-Skilltheir own version, first seen Nov 16, 2026
- netarz/gisoo-skills-registrytheir own version, first seen Nov 15, 2026
- kuldeep-jadeja/claude-handoff-plugintheir own version, first seen Nov 15, 2026
- gutohuida/AgentWeavetheir own version, first seen Nov 15, 2026
Used with
Projects with it also use pause, status and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
kennethleungtySkillpause
Pause — stop the music (alias for /stop)
Also in 7 projects that use this
AnthropicSkillstatus
Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.
Also in 15 projects that use this
MicrosoftSkillreport
Turn an exploration (threads, findings, charts) into a single Markdown report — note, blog post, executive summary, KPI dashboard, slide brief, or multi-section analytical report, with embedded charts.
Also in 7 projects that use this
MicrosoftSkillconfig
Show or change TokenEconomizer's settings: turn micro-skills, tool pruning or the loop guard on or off, or tune them, for this repository or (with --global) every repository. Use when the user asks to configure, enable or disable TokenEconomizer or one of its mechanisms.
Also in 3 projects that use this
sahinSkillexecute
Also in 4 projects that use this
u9401066Skillbug-fix
Structured bug fixing workflow with root cause analysis and regression prevention. Triggers: BF, 修 bug, fix bug, debug, 除錯, 錯誤, error, 問題, issue, 修復, fix, 故障, fault, 異常, exception, 失敗, failure, 不能用, broken, 壞掉.
Also in 3 projects that use this
- +2 more from microsoft
Other versions64 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 64
- H-mmer/pentest-agents★ 815same name
- bitwize-music-studio/claude-ai-music-skills★ 668same name
- qbeka/jev-job-search★ 368same name
- thesun4sky/jobstack★ 216same name
- EmeaAppGbb/spec2cloud★ 100same name
- saksham10arora-dotcom/everything-claude-codex★ 96same name
- thiagofinch/mega-brain★ 95same name
- nimadorostkar/Claude-Skills-collection★ 37same name
- junjiezhou1122/ideascientist-claude-code★ 35same name
- wrg32786/aigent-os★ 26same name
54 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- ai-infra-helperSkill
- humanizerSkill
- job-applicationSkill
- job-huntSkill
- portfolio-auditSkill
- pr-draftSkill
- social-mediaSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 56 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 33
review = diagnosis only: Never rewrite, never restructure, never generate.
- Very specific: line 34
polish = improve in place: Never fabricate numbers, tech stacks, hardware models, journal names, dates, or experiences.
- Very specific: line 35
Preserve a designed PDF: If the user has a custom layout or sets preserveLayout, polish may NOT emit a full markdown resume — only a …
- Very specific: line 36
Bilingual parity: If the resume is EN + 中文, every change is mirrored in both languages, not just the chosen language.
“Common” is measured: kept by at least 6 in 10 of the 56 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Resume (merged: review + polish)
One skill that does both: review (diagnose, never edit) and polish (improve, never fabricate). It is the consolidation of the upstream resume-review and resume-polish skills, with additions:
- ATS / parseability check (review): when you supply extracted PDF text (
pdfText), it flags broken/split tokens, stray hyphens, ligature artifacts, and bilingual keyword duplication. - Internal number-consistency + Summary-to-body traceability (review): credibility now has two mandatory sub-checks.
- Layout-preserving mode (polish): when the resume is a designed PDF you want kept intact, polish emits only before→after fragments, never a full rewrite.
- Bilingual (EN + 中文) handling in both modes.
Which mode to run
| User says | Mode | Full instructions |
| "review my resume", "rate this", "what's wrong" | review | references/review_SKILL.md (+ references/review_schema.json) |
| "polish my resume", "optimize", "improve", "rewrite for X" | polish | references/polish_SKILL.md (+ references/polish_schema.json) |
Load the referenced file for the full workflow, dimensions, scoring, and output contract. This file is only the router.
Key rules (both modes)
- review = diagnosis only. Never rewrite, never restructure, never generate. Output JSON per
references/review_schema.json. - polish = improve in place. Never fabricate numbers, tech stacks, hardware models, journal names, dates, or experiences. Edits trace to the original or
sourceTexts. - Preserve a designed PDF. If the user has a custom layout or sets
preserveLayout, polish may NOT emit a full markdown resume — only a compact before→after diff plus a note to apply edits in their source. - Bilingual parity. If the resume is EN + 中文, every change is mirrored in both languages, not just the chosen
language. - ATS is advisory in polish. polish outputs Markdown, so it cannot fix PDF text-layer breaks; it must list any discovered text-layer issues in
suggestionsinstead. - Never submit or regenerate the PDF. These skills produce text/diffs only.
Typical loop
review → fix issues with polish (optionally preserveLayout to keep the PDF) → review again to confirm the score rose. Supply jd for targeted optimization, sourceTexts for anti-hallucination checks, and pdfText for the ATS check.
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
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.

