Resume builder

Skill shinzoxD/knackbox/skills/documents/resume-builder

Curated, auditable, benchmark-ready Agent Skills library for Claude Code, Codex, OpenCode, Cursor, and more.

Install

npx -y skills add shinzoxD/knackbox --skill resume-builder

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

28 days oldThe repository was created 28 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
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.

What its author says it does

Copied from the file, not written here

Build or rewrite resumes and tailor them to a specific job description, with achievement-focused bullets that pass ATS screening. Use whenever the user shares a resume or CV, asks to improve or tailor one, wants bullets rewritten, or says "help me apply for this job" with a job posting — even if they only paste their work history as rough notes.

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.7 KB, 506 tokens by cl100k_base, as published. Nobody here has run it

Resume Builder

Turn duties into evidence. Every line should answer the hiring manager's only question: "what happens if I hire this person?"

Process

If a job description is provided, extract its top 5–8 requirements and keywords first; mirror the JD's exact terms where truthful (ATS matching is literal).
Rewrite experience as achievement bullets using action verb + what you did + measurable outcome:
- Weak: "Responsible for managing social media accounts."
- Strong: "Grew Instagram following 12k→38k in 9 months by shifting to reels-first content, driving 22% of site traffic."
Order sections by relevance to the target role; within jobs, lead with the bullet most relevant to the JD.
Output in clean, ATS-safe formatting: standard section headings (Experience, Education, Skills), no tables, no text boxes, no graphics.

Rules

Never fabricate. No invented metrics, titles, dates, or tools. Where a number would strengthen a bullet, insert [X% / how many? — fill in] and move on.
Quantify with what exists: team size, frequency, scale, time saved, revenue, error reduction. "How many? How often? Compared to what?"
One page per ~10 years of experience; cut oldest and least relevant first. Every bullet ≤ 2 lines.
Ban empty adjectives: "results-driven", "team player", "hard-working". Show it in a bullet or drop it.
Tense: past roles in past tense, current role in present tense.
Summary section only if senior or career-changing — 2 lines max, tailored to the JD, no first-person pronouns.

Edge cases

Employment gap: don't hide dates; if the user did anything relevant (freelance, courses, caregiving with transferable skills) list it plainly. Never invent cover stories.
Career change: lead with transferable achievements and a tailored skills section; de-emphasize domain-specific jargon from the old field.
No job description given: ask for the target role/industry in one question; if none, optimize for the user's stated goal and say which assumptions you made.