Update to App Builder

{
  "description": "Create, revise, critique, or tailor a resume or CV from the user's experience, existing resume, and optional job posting; produce an editable document when requested.",
  "included_files": [],
  "name": "build-resume",
  "skill_md_contents": "---\nname: build-resume\ndescription: Create, revise, critique, or tailor a resume or CV from the user's experience, existing resume, and optional job posting; produce an editable document when requested.\n---\n\n# Build a resume\n\nHelp the user create a truthful, concise resume for their target role and location. Support a first resume, a rewrite from an existing file, a targeted version for a posting, or feedback on a draft.\n\n## Gather the material\n\n1. Read any supplied resume and job description first. If given a URL, retrieve the posting when available; otherwise ask for its text. Do not ask for information already present.\n2. Establish the target role and region, work history with titles, employers, dates and accomplishments, education, relevant skills, and contact details the user wants displayed. Ask only for the essential gaps. A useful first request is a current resume or LinkedIn text plus a target role or job posting; if none exists, interview the user in small groups of questions.\n3. Use placeholders for missing dates, metrics, or contact details and point them out clearly. Never invent jobs, qualifications, certifications, dates, metrics, software proficiency, or leadership scope. When a bullet could be stronger with a number, ask for a verified number or write it without one.\n\n## Draft and tailor\n\n- Put name and chosen contact details first, followed by a targeted summary when useful, experience, education, and relevant skills. Add projects, certifications, publications, or volunteer work only when supported and useful.\n- Write specific action and outcome bullets in plain language. Preserve the distinction between led, contributed to, and supported. Avoid generic adjectives and repeated phrases.\n- Match the terminology of a job posting where the person's evidence supports it. Surface the most relevant experience early, without keyword stuffing or hidden text. Do not claim an ATS score or guarantee interview outcomes.\n- Follow the user's preferred language, region, field, and length. If unknown, use a clean reverse chronological layout and concise length appropriate to the career stage. Do not impose one country's photo, personal details, or date conventions on another; ask when they affect the result.\n- For a career transition or employment gap, frame transferable experience accurately and neutrally. Do not fabricate continuity or imply an unearned credential.\n\n## Deliver and refine\n\n- For a quick draft, show a complete resume with clearly marked placeholders, then list the few facts needed to finalize it. For an improvement request, give a revised version plus a short list of meaningful changes.\n- If asked for an editable file, use the available document workflow to make a DOCX and inspect its rendering. For a PDF, use the configured `resume-pdf` MCP server’s `create_resume_pdf` tool only after the user approves the final resume text. Send the complete Markdown resume with the chosen contact details, use `letter` for the US and Canada or `a4` elsewhere, and share the returned link with its 60-minute expiry. If the tool reports unsupported characters, explain the limitation and use an appropriate alternative document workflow. Keep headings, dates, and bullets easy to scan.\n- When tailoring, briefly identify which evidence was emphasized and any job requirements that the user's information does not yet support. Invite the user to correct facts and supply omitted achievements before treating a draft as final.\n- Treat resume contents as personal information. Include only contact or sensitive details the user elects to share in the output; do not use external services to process them unless requested.\n"
}