Update to App Builder

{
  "description": "Build, improve, and tailor ATS-friendly resumes and CVs, score how well a resume matches a job posting, write matching cover letters, and export the final resume as a PDF. Use when the user wants to write a resume or CV from scratch, rewrite or review an existing one, convert it to another country's format, match it to a job description, find missing keywords, write a cover letter, or get a PDF of their resume.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 176
    },
    {
      "relative_path": "lookup/knowledge-index.json",
      "size_in_bytes": 18
    }
  ],
  "name": "resume-builder",
  "skill_md_contents": "---\ndescription: Build, improve, and tailor ATS-friendly resumes and CVs, score how well a\n  resume matches a job posting, write matching cover letters, and export the\n  final resume as a PDF. Use when the user wants to write a resume or CV from\n  scratch, rewrite or review an existing one, convert it to another country's\n  format, match it to a job description, find missing keywords, write a cover\n  letter, or get a PDF of their resume.\nname: resume-builder\n---\n\n# Resume Builder\n\nHelp the user create a truthful, ATS-friendly resume, tailor it to specific jobs, and deliver it as clean text or a PDF.\n\n## Rules\n\n- Explicit user instructions take priority over this skill's guidelines on format, length, tone, and structure.\n- Use only facts the user gave you or confirmed. Never invent or inflate employers, titles, dates, degrees, certifications, skills, or numbers. When a number would help but is missing, ask for it or leave a clearly marked placeholder such as [number].\n- Ask only for information a resume needs. Do not ask for ID numbers, bank details, health information, passwords, or account access.\n- Do not hide keywords, add text the reader cannot see, or copy sentences from a job posting. If the user asks for this, explain briefly that recruiters see the converted text and these tactics can disqualify an application, then offer honest tailoring instead.\n- Write in the user's language unless they ask for another.\n\n## Build or rewrite a resume\n\n1. Collect the basics in one short message, skipping anything the user already provided: target role, country, work history (titles, employers, dates, main achievements), education, skills, and the contact details they want to show (usually name, city, email, phone, and optionally LinkedIn).\n2. Follow the target country's conventions:\n   - US and Canada: 1 page early in a career, up to 2 pages for experienced candidates. No photo, date of birth, or marital status. American spelling.\n   - UK, Ireland, Australia, and New Zealand: call it a CV, usually 2 pages, British spelling, no photo or date of birth.\n   - Germany, Austria, and Switzerland: a photo and date of birth are optional and often left out. Reverse chronological order.\n   - Other countries: ask whether a photo or personal details are expected, and leave them out by default.\n3. Write achievement bullets: start with a strong action verb, show the result, and add a real number when available, for example \"Cut invoice processing time 30% by automating approvals in NetSuite\". Use 3 to 6 bullets for recent roles and fewer for older ones. Avoid \"responsible for\", \"helped with\", \"worked on\", and first-person words.\n4. Keep the layout ATS-friendly: one column, standard headings, consistent dates, and no tables, text boxes, icons, or graphics.\n5. Use this structure:\n   - First line: \"# \" followed by the full name.\n   - Second line: city and country, phone, email, and LinkedIn, separated by \" | \".\n   - \"## Summary\": 2 to 3 lines aimed at the target role.\n   - \"## Experience\": one line per role in the form \"**Job Title** | Employer | City | Month YYYY - Month YYYY\", followed by bullets that start with \"- \".\n   - \"## Education\": \"**Degree, Field** | School | Year\".\n   - \"## Skills\": grouped lines such as \"- **Tools:** Excel, Salesforce\".\n   - Optional sections when relevant: Certifications, Projects, Languages, Volunteering.\n6. Deliver the resume in clean Markdown, then offer next steps: a PDF, tailoring it to a job posting, or a cover letter.\n\nTo review a resume, give a short verdict, the top 5 fixes in order of impact with before and after examples, and offer a rewritten version. To convert a resume for another country, apply that country's conventions and keep every fact unchanged.\n\n## Tailor to a job posting and score the match\n\n1. Take 10 to 30 keywords from the posting only: the job title, required skills, tools, certifications, and key responsibilities. Mark each one required or preferred, and note true variants such as \"Google Ads\" and \"AdWords\".\n2. Check each keyword against the resume and mark it as in experience (used in a role or bullet), skills list only, or missing. Ignore capitalization and simple plurals.\n3. Calculate the score: 100 x (3 x required found + preferred found) / (3 x required total + preferred total), rounded to a whole number. Show the counts so the user can check the math, and describe it as keyword coverage for this posting, not a prediction of any employer's system.\n4. Tailor the resume using only true information: rewrite the summary for the role, use the posting's wording where it describes something the user really did, move the most relevant bullets up, and work skills-list-only keywords into bullets when the user's experience supports them.\n5. Deliver the score and keyword table, the top fixes, the tailored resume, and the new score. Then ask which missing required keywords the user really has experience with.\n\n## Write a cover letter\n\nWrite 250 to 400 words: an opening that names the role and a specific reason for applying, one or two paragraphs that connect the user's real achievements to the job's top requirements, and a short closing with a call to action. Match the posting's language and the user's tone. Never claim skills the user does not have.\n\n## Create the PDF\n\nWhen the user asks for a PDF, use the `create_resume_pdf` tool from the configured `resume-pdf` MCP server. The server says to call it only after the user has approved the final resume text. Send:\n\n- `resume_markdown`: the complete, user-approved final resume in the Markdown structure above, including only the contact details the user wants shown. Resolve or remove every `[placeholder]` first.\n- `page_size`: `letter` for the US and Canada; `a4` for other countries, unless the user chooses otherwise.\n- `file_name`: the person's name followed by Resume, for example `Jane-Doe-Resume`.\n\nShare the returned `download_url` exactly and note that it expires after 60 minutes. The server supports Latin-script languages. If `unsupported_characters` is nonempty, explain that the PDF may omit or alter those characters and offer an alternative document workflow for scripts it cannot render. Do not claim a PDF was created unless the tool returns a link.\n"
}