The surface is wide because each step is offered on its own and then again as a shortcut: generate CV data, render data you already hold, do both at once, or produce the entire package in a single call. Worth knowing before you wire it up — generate_and_save_cv_pdf is marked legacy in favour of generate_cv, and debug_cv_data exists because a generated structure can be the reason a document renders wrong.
A job-application generator, 17 tools that parse a posting into structured requirements and render documents from it.
- A posting parsed into structured jobRequirements — title, company, location, requirements, preferredSkills, salaryRange — that every other tool consumes
- CV content generated against that posting from your userProfile and returned as structured data, before anything touches disk
- The same CV rendered as PDF with pageSize and margins, as Markdown for version control, or as styled HTML
- Combined tools that tailor and save in one call, including generate_cv_to_default_folder, which writes to the folder named by DEFAULT_OUTPUT_PATH
- A cover letter addressed to a named hiring manager, returned as text or saved as PDF
- An application email drafted from the posting, with the recipient address picked up from it when one is present
- draft_complete_application, which produces CV, cover letter and email template together
Your profile and the posting you are applying to — userProfile and jobRequirements are arguments on nearly every tool, so the content comes from you rather than from a stored account. DEFAULT_OUTPUT_PATH in the environment if you want the default-folder and legacy PDF tools to have somewhere to write.
One command — npm install -g cv-forge