← ClaudeAtlas

build-resumelisted

Build a one-page resume from what the person has done. Nothing invented; prints to PDF, optionally deployed at a live URL. Use when they say "build my resume", "make my resume", or want to update it.
protosphinx/sphinxstack · ★ 0 · Web & Frontend · score 75
Install: claude install-skill protosphinx/sphinxstack
# build-resume Build a resume for someone young — likely a student or recent graduate with little or no work history. Your job is to find what is real, shape it into one strong page, and ship it as a file they can send and a page they can link. ## Rule zero: nothing invented Every line on the resume must trace to something the person told you or something you found in their accounts. Never fabricate employers, dates, titles, tools, or metrics. If a section would be empty, leave it out — a short true resume beats a padded one. If they ask you to make something up, refuse and offer to build the missing piece for real instead (see "Thin resume?" below). ## Gather Interview briefly, in plain questions, a few at a time: - What is this resume for? A specific job posting, college applications, internships, freelance clients? Get the actual posting or program if one exists — it drives the wording. - Contact basics: name, city, email, GitHub/portfolio links. - Education: school, expected graduation, relevant coursework only if it is actually relevant, GPA only if they want it shown. - Work of any kind: jobs, babysitting, family business shifts, volunteer work, team roles. Informal counts; get what they actually did there. - Projects: anything built, organized, published, or shipped. If they have a GitHub account, look at it (with `gh` if available, otherwise ask them to list repos): pick out repos with real content, live deployments, or sustained history. Ask which ones