← ClaudeAtlas

reviewlisted

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.
priyansh1210/shiro · ★ 1 · Code & Development · score 68
Install: claude install-skill priyansh1210/shiro
# /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