Apex Generate Cv

apex-generate-cv

Purpose

This skill constructs a full CV using the candidate’s history and the recommendations from earlier analysis phases. It follows best practices for international organizations: clear sections, action oriented bullets and appropriate keyword embedding.

Shared definitions

Apply the expert lens, collaboration rules, guardrails, quality loop protocol, guiding principles, and error handling patterns defined in apex-guardrails.

Format profile: cv_document.

Inputs

Required:

• USER_JOB_HISTORY_TEXT: the user’s work experience.
• JOB_DESCRIPTION_TEXT: the target role description.

Optional:

• USER_ADMIN_PROFILE_TEXT: to align entries with the Admin Profile.
• TERM_EXTRACTOR: ive high-priority terms from a job description with star ratings, ATS synonyms, JD-grounded rationale, and resume-ready examples in a strict four-line format.
• JD_KEYWORD_BANK: an expanded 20–40 phrase keyword bank.
• apex-keyword-insertion-map: a list of must‑use JD phrases and specify where to insert them across Phase 8 outputs.
• apex-bullet-enhancer Enhanced 2–3 existing job history bullet points by rewriting them using strong action verbs, quantifiable outcomes, and integration of high-priority JD terms (from TERM_EXTRACTOR).
• apex-uvp-statement A concise 1–2 sentence Unique Value Proposition (UVP) statement tailored to the role and organization using only the candidate’s evidence.
• SKILLS_TAXONOMY: A structured list of skills.

Output format

Produce plain text with the following sections:

1. Header: Candidate’s name and contact details (use placeholders such as [Full Name], [Email], [Phone] if absent).
2. Summary Statement: A concise 1–2 sentence summary derived from the UVP (or create one aligned with the role if not available).
3. Experience: List roles in reverse‑chronological order. For each role:
   • Start with Job Title, Organization, Location, Dates on one line (use placeholders if information is missing).
   • Follow with 2–4 bullet points highlighting achievements and responsibilities, using strong action verbs and quantifiable outcomes. Incorporate high‑priority keywords naturally. Each bullet should be one concise sentence. Use the enhanced bullets where available.
4. Education: If provided in the inputs, list degrees, institutions, and graduation years. Use one line per degree.
5. Skills/Certifications: Include technical skills, languages, tools and certifications relevant to the role. List them in categories if helpful. Only include skills present in the user’s inputs or the approved taxonomy.

Rules

• Do not invent job titles, employers, dates or qualifications. Use placeholders instead.
• Keep section headings simple (e.g., Experience, Education, Skills). Do not include any Markdown headings (e.g., #, ##) in the final CV text; the output should be ready to copy-paste into a document.
• Use a dash - to start each CV bullet.
• Ensure verb tense consistency (past tense for past roles; present for current roles).
• Integrate keywords identified in Phase 2 naturally; avoid obvious keyword stuffing.
• Maintain a professional and factual tone throughout.
• Do not include star symbols (★).

Recursive self-evaluation (internal only; do not print)

Apply the recursive self-evaluation loop protocol from apex-guardrails.

Domain-specific checks for this skill: verify clear headings, consistent formatting (no markdown headers in output), and keyword integration.

Steps

1. Compile the candidate’s roles from USER_JOB_HISTORY_TEXT and USER_ADMIN_PROFILE_TEXT (if provided).
2. Draft the summary statement using the UVP or derive one from the strongest matches between the candidate’s experience and the job’s needs.
3. For each role, write 2–6 bullets mixing:
   • impact achievements (prefer metrics),
   • key responsibilities aligned to the JD.
4. Build the education and skills/certifications sections from available data.
5. Output the CV with clear headings and consistent formatting.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.