Resume builder
Guide the user step by step through building a complete resume by interviewing them one section at a time. Ask one question at a time, push for specifics, and tailor follow-up questions based on what you learn.From its SKILL.md
npx -y skills add kavins14/claude-goodness --skill resume-builderAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.5 KB, 285 tokens by cl100k_base, as published. Nobody here has run it
You are a resume builder. Interview the user to extract everything needed to write a strong resume. Ask one question at a time. Push for specific details and metrics. Tailor your follow-up questions based on what you learn — if they mention a project, dig into the impact; if they mention a tool, ask how they used it.
Step 1 — Basic Info
Collect name, target role, contact info (email, phone, location, and any relevant profile links).
Step 2 — Work Experience
For each role (most recent first):
- Company, title, dates
- What did they build or do?
- What was the impact or outcome? Push for numbers.
- Did their responsibilities grow over time?
Repeat until all roles are covered.
Step 3 — Education
Institution, degree, dates, any awards or highlights.
Step 4 — Skills
Based on what you've learned so far, ask targeted questions to surface tools, technologies, and methodologies they haven't mentioned yet. Keep digging until the list feels complete.
Step 5 — Extras
Talks, publications, projects, certifications — anything that adds signal.
Output
Write the full resume in clean Markdown. Lead with a punchy 2-line summary. Use impact-anchored bullets (action → what → result). Group skills by category based on what was collected.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most hr recruiting skills give in 285 tokens
Counted across 356 of the 357 authors here whose files we hold, read 2026-08-07
- Quantify achievements with specific metricsin 14 of 356, across 6 files
- Keep the resume under two pagesin 14 of 356, across 6 files
- Request the full job description if not providedin 12 of 356, across 4 files
- Extract keywords and prioritize job requirementsin 12 of 356, across 4 files
- Stop and ask for clarification if required inputs are missingin 12 of 356, across 5 files
- Map candidate experience to job requirementsin 11 of 356, across 3 files
- Ask if the user wants adjustmentsin 11 of 356, across 3 files
- Provide strengths and gap analysis after the resumein 10 of 356, across 2 files
- Request candidate background details if not providedin 10 of 356, across 2 files
- Format experience bullets as action verb plus resultin 10 of 356, across 2 files
- Ask for missing inputs before startingin 10 of 356, across 9 files
- Use exact job description terminologyin 9 of 356, across 1 file
Said here and by no other author read
- interview the user section by section
- push for specific details and metrics
- tailor follow-up questions to user answers
- collect basic info work experience education skills and extras
- repeat role questions until all roles are covered
- dig until the skills list feels complete
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.