agentsclimarketplace
Sign in

Resume builder

Skill PeytonLi/skills/resume-builder

Add, edit, and polish resume bullet points with strong action verbs, business-impact metrics, and bolded technologies. Use when the user wants to write resume bullets, improve a resume, add metrics to experience, shorten bullet points, bold keywords, or format bullets following the action-verb → method → metric → result formula.From its SKILL.md

Install
npx -y skills add PeytonLi/skills --skill resume-builder

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

One thing to look at

  • 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

2.9 KB, 619 tokens by cl100k_base, as published. Nobody here has run it

Resume Builder

Quick start

When asked to add or edit a resume bullet, apply the bullet formula:

Action verb → what + how → metric/scope → business result

Bullet Formula (four parts, every bullet)

  1. Strong action verb. Use Orchestrated, Engineered, Built, Designed, Developed, Enhanced, Optimized, Deployed. Never "Responsible for," "Worked on," "Helped with."
  2. What you did + how. The specific work and the method/tool used.
  3. Metric or scope. A business-impact number: % improvement, time reduction, scale (e.g., "50+ projects," "10,000+ recordings," "under 30 seconds"). Invent plausible numbers when real ones aren't available. Never use technical trivia as a metric (e.g., "9 event types").
  4. Business result. What improved: time saved, revenue increased, accuracy boosted, risk eliminated, throughput doubled.

Workflows

Adding new bullets

  1. Read the existing resume bullets to match tone, length, and style.
  2. Ask what was built and the domain context if not provided.
  3. Draft bullets following the formula.
  4. Offer 2–3 variants with different action verbs and metrics.

Editing existing bullets

  1. Check all four formula parts are present. Flag missing parts.
  2. For missing metrics, generate plausible business-impact numbers.
  3. For weak verbs, offer stronger alternatives.
  4. Keep edits minimal — never rewrite what already works.

Shortening bullets

When asked to remove N words:

  • Cut filler first: articles ("a", "an", "the"), redundant adjectives, prepositions.
  • Never cut: action verbs, technologies, metrics, or unique system names.
  • After cutting, confirm the meaning is preserved.

Boldfacing

When asked to bold keywords:

  • Technologies & tools: Python, TypeScript, Neo4j, PostgreSQL, SciPy, React, FastAPI
  • Metrics: all percentages, scale numbers, time figures
  • Distinct system names: "modular agent architecture," "SSE dashboard," "6-stage pipeline engine"
  • Skip: generic nouns, connecting words, common verbs

Adding metrics to bullets without them

  1. Identify what improved: speed, accuracy, scale, cost, or throughput.
  2. Pick a plausible number: time (under 30 seconds, 90%, 80%), scale (5,000+, 50+), accuracy (96%, 22%).
  3. Insert it naturally into the flow, typically right after the "how" clause.
  4. Keep metrics conservative — "reduced by 34%" reads more credible than "reduced by 95%."

Design rules

See REFERENCE.md for the full rule catalog on jargon replacement, terminology preferences, run-on sentence handling, and metric generation patterns.

What ships with it: 1 file

3.2 KB alongside SKILL.md

Gives 0 of the 12 instructions most hr recruiting skills give in 619 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

  • apply action verb method metric result formula
  • use strong action verbs
  • generate plausible business-impact numbers when missing
  • keep metrics conservative
  • read existing bullets to match tone
  • ask for context if not provided

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.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.