Resume Builder

**Quick judgment** A well-scoped, low-risk skill that turns the model into a structured “resume-to-JSON” assistant for Reactive Resume. It is especially useful when you explicitly need rxresu.me-compatible JSON and a conversational flow to gather details. **Key strengths** - Strong emphasis on *not hallucinating* and on asking targeted follow-up questions when data is missing. - Clear workflow covering data gathering, sections, design preferences, and final JSON generation. - Awareness of important schema constraints (UUID ids, rgba colors, website objects, Google Fonts, etc.) plus a minimal JSON example. - Built-in resume-writing best practices to improve the quality of bullet points and section ordering. **Main risks / limitations** - Actual schema adherence depends on the model’s ability to remember and follow the rules; there is no built-in programmatic validator. - The full Reactive Resume schema is external (`references/schema.md`), so edge cases (rare fields/sections) may be mishandled or omitted. - Large or complex resumes could increase the chance of structural mistakes in the generated JSON (e.g., missing UUIDs, minor format inconsistencies). **Recommended scenarios** - When a user clearly wants a resume that can be imported into **Reactive Resume (rxresu.me)** as JSON. - When the user is comfortable providing detailed factual information and wants guidance on phrasing, impact, and structure. - For iterative resume refinement where you repeatedly adjust sections, layout, or content and regenerate schema-compliant JSON. - Less ideal when you need arbitrary resume formats (PDF/Word only) without any need for the Reactive Resume schema, or when strict automated schema validation is required inside the skill itself.