Builds a complete resume from scratch as Reactive Resume JSON that conforms to the schema and imports at https://rxresu.me. Asks for each missing detail instead of inventing it, then produces valid JSON (UUIDs, HTML descriptions, template and layout). Use when the user wants to create, build or generate a new resume, turn their work history into Reactive Resume JSON, or asks about the Reactive Resume schema, sections, templates or layout. For what belongs on a resume or a resume audit use resume-content-guide; for rewriting bullets, resume-bullet-writer; for fitting one job posting, resume-tailor; for tracking applications, job-application-manager; for interviews, interview-prep or mock-interview.
Permissions
Files
Builds a complete resume from scratch as Reactive Resume JSON that conforms to the schema and imports at https://rxresu.me. Asks for each missing detail instead of inventing it, then produces valid JSON (UUIDs, HTML descriptions, template and layout). Use when the user wants to create, build or generate a new resume, turn their work history into Reactive Resume JSON, or asks about the Reactive Resume schema, sections, templates or layout. For what belongs on a resume or a resume audit use resume-content-guide; for rewriting bullets, resume-bullet-writer; for fitting one job posting, resume-tailor; for tracking applications, job-application-manager; for interviews, interview-prep or mock-interview.
Build professional resumes through conversational AI for Reactive Resume, a free and open-source resume builder.
Version history
This skill builds the document. Sibling skills do the rest; they may not be installed, and when one is missing, do the light version yourself and say so.
Ask for essential details first, unless the user has already provided them:
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
Ask about preferences:
Output must conform to the Reactive Resume schema. See references/schema.md for the complete schema structure.
Key requirements:
id fields must be valid UUIDs<ul><li><p>…</p></li></ul>, never Markdown)dates ({ "start": "2020-01", "end": null, "present": true }); the legacy period and date text is rewritten from them on saveurl and label propertiesrgba(r, g, b, a) formatFor deeper content work, hand off to resume-content-guide (what to include, country norms, audits) and resume-bullet-writer (achievement bullets). If neither is installed, apply these core rules:
picture.hidden: true), date of birth, marital status, full street address and ID numbers. Other countries differ.level to 0 to hide proficiency dots.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. With the Reactive Resume MCP server connected, offer to create it with import_resume {data} instead, after the user approves; if the payload is too large for the client, give the JSON file.
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.
The Reactive Resume MCP server also manages job applications. For pipeline work (adding jobs, moving stages, follow-ups, recording the resume version sent, weekly reviews, messages), use the job-application-manager skill. If it isn't installed:
list_applications before changing existing records; create_application for a new opportunity.update_application to move a stage or link a resume; add_application_note to log activity.score_application_match, tailor_resume_for_application, draft_application_message) send the resume and posting to the user's AI provider: ask first, and review their output before the user sends anything.When information is missing, ask specific questions:
Avoid compound questions. Ask one thing at a time for clarity.
In these kits
More from @amruthpillai
Works with
Claude, Codex, Cursor & more