R

resume-builder

Verified

by amruthpillai · Updated Apr 16, 2026

claude-opus-4-6
1.7Kin4.6Kout
$0.361m 35s

Generate professional resumes that conform to the Reactive Resume schema. Use when the user wants to create, build, or generate a resume through conversational AI, or asks about resume structure, sections, or content. This skill guides the agent to ask clarifying questions, avoid hallucination, and produce valid JSON output for https://rxresu.me.

resumejsonreactive-resumecareerwritingschema

See It In Action

1 turns·claude
The project codebase is in your current working directory. Explore the files to understand the code before making changes. recruiting needs my resume in Reactive Resume JSON format for an internal move today — generate it directly from the details below, don't ask follow-ups. Use today's date (2026-04-14) for any 'present' role end date. Personal: Alex Chen, alex.chen@brightriver.co, +1-503-555-0142, Portland OR 97201, https://alexchen.dev, https://linkedin.com/in/alexchen-pdx, https://github.com/alexchen Summary: Senior product engineer (8 yrs) focused on developer tools and growth infrastructure. Shipped the self-serve tier at Bright River that reached $1.4M ARR in Q1 2026. Previously led billing platform migration at Mapbox. Work experience: 1. Bright River LLC — Staff Product Engineer — Portland, OR — 2024-03 to present. Led self-serve launch (free->paid conversion 9.2%, 3x industry benchmark). Built activation telemetry pipeline cutting onboarding friction debug time from 6 weeks to 2 days. Manages 3 ICs. 2. Mapbox — Senior Software Engineer — Remote — 2020-05 to 2024-02. Led billing platform migration ($28M ARR, zero-downtime cutover). Introduced OpenAPI-first contract testing across 14 services. 3. Stripe — Software Engineer — San Francisco, CA — 2018-01 to 2020-04. Built dispute-evidence upload product. Shipped webhook retry overhaul (p99 delivery 45min -> 90sec). Education: 1. Carnegie Mellon University — B.S. Computer Science — 2014-08 to 2018-05 — GPA 3.8. Undergrad thesis on incremental query planners. Skills: TypeScript, Python, Go, PostgreSQL, Kubernetes, product analytics, API design, growth instrumentation, technical writing. Languages: English (native), Mandarin (fluent). Certifications: AWS Solutions Architect Associate (2022). Projects: 'litejson' — OSS JSON stream parser (2.1k GitHub stars, 2023). Generate the complete Reactive Resume JSON now with valid UUIDs for section/item ids.

Let me first explore the codebase to understand the Reactive Resume JSON schema, then generate the file directly.

Now I have the full schema. Let me generate valid UUIDs and create the resume JSON.

The file is ready at:

alex-chen-reactive-resume.json (5.2 KB, valid Reactive Resume JSON)

Here's what's in it:

SectionDetails
BasicsAlex Chen, alex.chen@brightriver.co, Portland OR 97201, with GitHub + LinkedIn as custom fields
Summary8-year senior product engineer blurb with the $1.4M ARR highlight
Experience3 roles — Bright River (Mar 2024 – Apr 2026), Mapbox (May 2020 – Feb 2024), Stripe (Jan 2018 – Apr 2020)
EducationCMU B.S. CS, 3.8/4.0, with thesis note
Skills3 grouped items — Languages (TS/Python/Go), Infrastructure (PG/K8s), Engineering Practices (API design, analytics, etc.)
Projectslitejson (2.1k stars)
CertificationsAWS SAA (2022)
LanguagesEnglish (Native), Mandarin (Fluent)
Empty sectionsAwards, Publications, Volunteer, Interests, References — all present but hidden: true
Metadataonyx template, Letter format, Open Sans fonts, indigo primary color

All id fields use valid v4 UUIDs, descriptions use HTML (<ul><li> for bullets), and the "present" end date on the Bright River role is set to Apr 2026 per today's date. Recruiting can import this directly at rxresu.me → Import → JSON.

Claude Sonnet 4.6

SKILL.md

Resume Builder for Reactive Resume

Build professional resumes through conversational AI for Reactive Resume, a free and open-source resume builder.

Core Principles

  1. Never hallucinate - Only include information explicitly provided by the user
  2. Ask questions - When information is missing or unclear, ask before assuming
  3. Be concise - Use clear, direct language; avoid filler words
  4. Validate output - Ensure all generated JSON conforms to the schema

Workflow

Step 1: Gather Basic Information

Ask for essential details first, unless the user has already provided them:

  • Full name
  • Professional headline/title
  • Email address
  • Phone number
  • Location (city, state/country)
  • Website (optional)

Step 2: Collect Section Content

For each section the user wants to include, gather specific details. Never invent dates, company names, or achievements.

Experience: company, position, location, period (e.g., "Jan 2020 - Present"), description of responsibilities/achievements

Education: school, degree, area of study, grade (optional), location, period

Skills: name, proficiency level (Beginner/Intermediate/Advanced/Expert), keywords

Projects: name, period, website (optional), description

Other sections: languages, certifications, awards, publications, volunteer work, interests, references

Step 3: Configure Layout and Design

Ask about preferences:

  • Template preference (13 available: azurill, bronzor, chikorita, ditto, ditgar, gengar, glalie, kakuna, lapras, leafish, onyx, pikachu, rhyhorn)
  • Page format: A4 or Letter
  • Which sections to include and their order

Step 4: Generate Valid JSON

Output must conform to the Reactive Resume schema. See references/schema.md for the complete schema structure.

Key requirements:

  • All item id fields must be valid UUIDs
  • Description fields accept HTML-formatted strings
  • Website fields require both url and label properties
  • Colors use rgba(r, g, b, a) format
  • Fonts must be available on Google Fonts

Resume Writing Tips

Share these tips when helping users craft their resume content:

Content Guidelines

  • Lead with impact: Start bullet points with action verbs (Led, Developed, Increased, Managed)
  • Quantify achievements: Use numbers when possible ("Increased sales by 25%", "Managed team of 8")
  • Tailor to the role: Emphasize relevant experience for the target position
  • Be specific: Replace vague terms with concrete examples
  • Keep it concise: 1-2 pages maximum for most professionals

Section Order Recommendations

For most professionals:

  1. Summary (if experienced)
  2. Experience
  3. Education
  4. Skills
  5. Projects (if relevant)
  6. Certifications/Awards

For students/recent graduates:

  1. Education
  2. Projects
  3. Skills
  4. Experience (if any)
  5. Activities/Volunteer

Common Mistakes to Avoid

  • Including personal pronouns ("I", "my")
  • Using passive voice
  • Listing job duties instead of achievements
  • Including irrelevant personal information
  • Inconsistent date formatting

Output Format

When generating the resume, output a complete JSON object that conforms to the Reactive Resume schema. The user can then import this JSON directly into Reactive Resume at https://rxresu.me.

Example minimal structure:

{
  "picture": { "hidden": true, "url": "", "size": 80, "rotation": 0, "aspectRatio": 1, "borderRadius": 0, "borderColor": "rgba(0, 0, 0, 0.5)", "borderWidth": 0, "shadowColor": "rgba(0, 0, 0, 0.5)", "shadowWidth": 0 },
  "basics": { "name": "", "headline": "", "email": "", "phone": "", "location": "", "website": { "url": "", "label": "" }, "customFields": [] },
  "summary": { "title": "Summary", "columns": 1, "hidden": false, "content": "" },
  "sections": { ... },
  "customSections": [],
  "metadata": { "template": "onyx", "layout": { ... }, ... }
}

For the complete schema, see references/schema.md.

Asking Good Questions

When information is missing, ask specific questions:

  • "What was your job title at [Company]?"
  • "What dates did you work there? (e.g., Jan 2020 - Dec 2022)"
  • "What were your main responsibilities or achievements in this role?"
  • "Do you have a specific target role or industry in mind?"

Avoid compound questions. Ask one thing at a time for clarity.

FAQ

What does resume-builder do?

Generate professional resumes that conform to the Reactive Resume schema. Use when the user wants to create, build, or generate a resume through conversational AI, or asks about resume structure, sections, or content. This skill guides the agent to ask clarifying questions, avoid hallucination, and produce valid JSON output for https://rxresu.me.

When should I use resume-builder?

Use it when you need a repeatable workflow that produces text report.

What does resume-builder output?

In the evaluated run it produced text report.

How do I install or invoke resume-builder?

Ask the agent to use this skill when the task matches its documented workflow.

Which agents does resume-builder support?

Agent support is inferred from the source, but not explicitly declared.

What tools, channels, or permissions does resume-builder need?

It uses no extra tools; channels commonly include text; permissions include no explicit permission scopes.

Is resume-builder safe to install?

Static analysis marked this skill as low risk; review side effects and permissions before enabling it.

How is resume-builder different from an MCP or plugin?

A skill packages instructions and workflow conventions; tools, MCP servers, and plugins are dependencies the skill may call during execution.

Does resume-builder outperform not using a skill?

About resume-builder

When to use resume-builder

When a user wants to build a resume for import into Reactive Resume. When resume details need to be collected conversationally without inventing missing facts. When the output must follow a specific JSON schema.

When resume-builder is not the right choice

When the user wants automatic enrichment from LinkedIn or other external profiles. When the task is general graphic resume design outside the Reactive Resume schema.

What it produces

Produces text report.