review
Skill1 starsChanged 6 days agoMITView on GitHub
Run the rejection panel on a resume for one job. Picks the best base resume to start from, ten reviewers (eleven for design roles) try to reject it in parallel, a debrief merges their feedback into a fix plan, and the resume writer produces a tailored, truthful new version.
192 other projects use a version of this.
Adopted by
Most recently taken up by
- dzhng/skillstheir own version, first seen Nov 15, 2026
- muxy-app/muxytheir own version, first seen Nov 15, 2026
- macro-inc/macrotheir own version, first seen Nov 15, 2026
- yagizdo/quivertheir own version, first seen Nov 15, 2026
- markmhendrickson/neotomatheir own version, first seen Nov 15, 2026
- felipeam86/pipe-skillstheir own version, first seen Nov 15, 2026
Used with
Projects with it also use close-spec, daily-arxiv 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.
dzhngSkillclose-spec
When a spec under specs/<feature>/ is done shipping (a write-spec build, or any planned task that produced a spec), archive it to specs/done/ and rewrite it from a build-plan into a durable rationale — the why, the principles, the invariants — pointing back to the real code for the how. Use when implementation has landed and the plan no longer matches what shipped, or the user says a feature/spec is finished. Pairs with [write-spec](../write-spec/SKILL.md) (the plan this closes) and [review](../review/SKILL.md) (run before closing).
Also in 5 projects that use this
LambenthanSkilldaily-arxiv
每日从 arXiv 拉取新论文,过滤相关性,auto-ingest 高优先级论文,检测 SOTA 更新
Also in 5 projects that use this
dzhngSkilldesign-with-images
Explore UI and visual design with image generation, then iterate the real implementation against the user-selected concept. Use when brainstorming visual directions, offering mockup variants, or implementing an approved generated design; do not stop at the mockups or the first code approximation.
Also in 5 projects that use this
LambenthanSkillexp-eval
实验判决门:Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges
Also in 5 projects that use this
- +5 more from Lambenthan
- +3 more from dzhng
Other versions192 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 192
- garrytan/gstack★ 142ksame name
- ansible/ansible★ 71ksame name
- docling-project/docling★ 71ksame name
- traefik/traefik★ 66ksame name
- ClickHouse/ClickHouse★ 51ksame name
- temporalio/temporal★ 24ksame name
- ccch1mneyyy/dsh-Go★ 24ksame name
- tisfeng/Easydict★ 15ksame name
- juicedata/juicefs★ 15ksame name
- elie222/inbox-zero★ 13ksame name
182 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.
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. 0 are common, 6 are distinctive, and 7 are very specific to this project.
0
Common
Most of the 156 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Save tokens: never read a resume PDF if a text copy exists at memory/resume/.text/<file>.txt.
- Distinctive: line 17
File path: read it.
- Distinctive: line 19
Nothing given: ask the user to paste the JD and wait.
- Very specific: line 26
Write jd.md: the full job description text with page clutter removed (navigation, cookie banners, footers).
- Distinctive: line 29
A resume path was given in the arguments: use it. Skip the rest of this step.
- Distinctive: line 31
None: ask the user for a resume path.
- Very specific: line 33
Several: run the resume-picker agent and wait for it:
- Distinctive: line 38
Use the resume it picked, and tell the user in one line which one and why.
- Very specific: line 40
If memory/ doesn't exist, tell the user that /setup gives much better results (the writer can use their whole history, not just one …
- Very specific: line 43
Write resume-original.md: a faithful text copy of the chosen resume, with the same sections, wording and order.
- Distinctive: line 59
Wait until every reviewer has reported back before going on: If an agent fails, retry it once.
- Very specific: line 64
Run the debrief agent and wait for it:
- Very specific: line 82
Run these two commands, each on its own, with nothing else on the line (no cd):
“Common” is measured: kept by at least 6 in 10 of the 156 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
/review: the rejection panel
Arguments: $ARGUMENTS
Each agent's effort comes from its definition (effort: in .claude/agents/*.md): Low for quick reviewers, Medium where judgment needs depth, High for the writer. Don't override it unless the user asks. (The Shiro app doesn't use this skill: it runs its own cheaper pipeline, see ui/review-pipeline.mjs.)
Save tokens: never read a resume PDF if a text copy exists at memory/resume/.text/<file>.txt; otherwise run node tools/resume-text.mjs <file> once (it caches the text). Agents only ever read text files.
1. Get the job description
- File path: read it.
- URL: fetch it with WebFetch. Career pages are often rendered by JavaScript, so if the text comes back empty or without the actual job, and the Claude in Chrome tools are available, open it in a new tab and use
get_page_text. Otherwise ask the user to paste the JD. - Nothing given: ask the user to paste the JD and wait.
Extract the company name and the role title. If the company isn't clear, ask.
2. Create the run folder
runs/<YYYY-MM-DD>-<company>-<role>/: lowercase, hyphens, short. If it already exists, add -2, -3, and so on.
Write jd.md: the full job description text with page clutter removed (navigation, cookie banners, footers). Change nothing else. First line: Source: <URL or path>.
3. Pick the resume to start from
- A resume path was given in the arguments: use it. Skip the rest of this step.
- Otherwise, collect the base resumes: every file listed under
## Resumesinmemory/profile.md, plus any other resume file inmemory/resume/.- None: ask the user for a resume path.
- One: use it.
Several: run the
resume-pickeragent and wait for it:Job description:
<run>/jd.md Resumes: <path 1>, <path 2>, … Write your pick to:<run>/pick.mdUse the resume it picked, and tell the user in one line which one and why.
If memory/ doesn't exist, tell the user that /setup gives much better results (the writer can use their whole history, not just one resume), and continue if they want to.
4. Copy the resume as text
Write resume-original.md: a faithful text copy of the chosen resume, with the same sections, wording and order. Don't fix or improve anything. First line: Source file: <path>. Use the cached text (memory/resume/.text/<file>.txt, or run node tools/resume-text.mjs <file>) rather than reading the PDF.
5. Run the panel: all at once
Send one message containing one Agent call per reviewer so they run in parallel and none of them sees another's opinion. Subagent types:
ats, recruiter, hiring-manager, teammate, rival-applicant, ceo, technical-interviewer, skeptic, skip-level-manager, hr-screener
Add design-lead only when the job is a design role (product, UX, UI, interaction, visual or service design, design research). It judges design craft, so on other jobs it only adds noise and cost. Tell the user in one line whether it's in the panel.
Prompt for each (fill in the paths; don't paste the resume or JD text into the prompt, the agents read the files):
Review this resume for
<Role>at<Company>. Job description:<run>/jd.md Resume text:<run>/resume-original.md Write your report to:<run>/feedback/<agent-name>.md
Wait until every reviewer has reported back before going on. If an agent fails, retry it once. If it fails again, continue without it and tell the user.
Show the user the scoreboard built from the one-line replies: a table of reviewer, verdict, score, reason.
6. Debrief
Run the debrief agent and wait for it:
Feedback folder:
<run>/feedback/ Job description:<run>/jd.md Resume text:<run>/resume-original.md Write the debrief to:<run>/debrief.md
7. Rewrite
Run the resume-writer agent and wait for it:
Run folder:
<run>/ Debrief:<run>/debrief.md Job description:<run>/jd.md Resume text:<run>/resume-original.md Resume pick notes (if any):<run>/pick.md Career memory: memory/
8. Make the HTML and PDF
Run these two commands, each on its own, with nothing else on the line (no cd):
node tools/resume-html.mjs <run>/resume.md <run>/resume.html
node tools/html-to-pdf.mjs <run>/resume.html <run>/resume.pdf
They turn the writer's resume.md into the printable page and the PDF, using the Chrome or Edge on this computer. Both cost nothing. If it fails, say so in the report; the user can open resume.html and press Ctrl+P → Save as PDF instead.
9. Report to the user
Keep it short:
- Which resume it started from (and why, if the picker chose).
- Average score and the ADVANCE / MAYBE / REJECT counts.
- The 3–5 most important fixes that were made.
- Full paths to
resume.pdf,resume.md,changes.md,questions.mdanddebrief.md./applyuploadsresume.pdffrom here for this job. - The questions from
questions.md, and that they can answer them with/remember. - Offer round 2: run the same reviewers on the new
resume.mdto see whether the score went up. If they say yes, repeat step 5 with<run>/resume.mdas the resume text (and no original file), writing to<run>/round-2/feedback/, then show the before/after scoreboard side by side. Don't rewrite again unless they ask. - Offer to save it as a base resume for this kind of role: copy
resume.pdfintomemory/resume/<role>.pdf(or, if you can't run shell commands, use the run's path) and add a line- <Role>: <path>under## Resumesinmemory/profile.md, with<Role>kept to a few words (e.g.AI Engineer Intern (Acme)), never a list of what changed. Future jobs of this kind will start from it.
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.

