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.
Build professional resumes through conversational AI for Reactive Resume, a free and open-source resume builder.
Core Principles
Never hallucinate - Only include information explicitly provided by the user
Ask questions - When information is missing or unclear, ask before assuming
Be concise - Use clear, direct language; avoid filler words
Validate output - Ensure all generated JSON conforms to the schema
Workflow
MCP Application Tracking
Reactive Resume MCP can manage job applications as well as resumes. When the user wants to track applications through an agent, use the application tools instead of asking them to open the web UI.
Use list_applications before changing existing records.
Use create_application for one new opportunity or import_applications for spreadsheet/CSV rows.
Use update_application to move stages, archive/unarchive, edit contacts, set follow-ups, link a resume, or update job details.
Use add_application_note to log timeline activity.
Use attach_application_document and remove_application_document for sent resume or cover-letter PDFs.
Use score_application_match, tailor_resume_for_application, and draft_application_message for Application Copilot workflows after a linked resume and job description exist.
Review AI-generated cover letters and follow-ups before sending them.
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
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:
Summary (if experienced)
Experience
Education
Skills
Projects (if relevant)
Certifications/Awards
For students/recent graduates:
Education
Projects
Skills
Experience (if any)
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.
