Update to CVEmber - Resume & CV Builder
Snapshot Nov 9, 2026 · 01:22 UTC · version 1.0.3
Collection source: downloaded plugin package.
Payment or plan references changed
Skill instructions — Now says: Offer only what is on CVEmber's menu (the `menu` that `get_started` returns). Never offer anything else, such as a LinkedIn import or job search. - *CVEmber,...
Observed in published text. Live prices and checkout terms have not been verified by this change.
Up to 3 plugins free · no card required.
All fields and original values.
Skill instructions
Nov 5, 2026 · 18:11 UTC
If a CVEmber card is shown above your reply, don't repeat what it says. Add only the next step in one or two lines. - *CVEmber, menu* or *CVEmber, help*: don't restart setup. Call `get_started` so the card shows where they are now. If th...
Nov 9, 2026 · 01:22 UTC
Offer only what is on CVEmber's menu (the `menu` that `get_started` returns). Never offer anything else, such as a LinkedIn import or job search. - *CVEmber, menu* or *CVEmber, help*: don't restart setup. Call `get_started` and show its ...
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -17,23 +17,23 @@ - Show links as a named link, like [Download PDF](link). Never paste a raw URL. - Use at most one emoji in a message, and only these: 👋 ✅ 🎉 - Never show tool names, ids, JSON or error codes. -- If a CVEmber card is shown above your reply, don't repeat what it says. Add only the next step in one or two lines. +- Offer only what is on CVEmber's menu (the `menu` that `get_started` returns). Never offer anything else, such as a LinkedIn import or job search. ## When it's asked for again The person can bring this guide back any time. -- *CVEmber, menu* or *CVEmber, help*: don't restart setup. Call `get_started` so the card shows where they are now. If there's no card, show the four steps with a ✅ on finished ones, then offer the one next step. Keep it to one message. +- *CVEmber, menu* or *CVEmber, help*: don't restart setup. Call `get_started` and show its `menu` items as written, as a numbered list, with one line on where they are now (their latest resume, if any). Then ask what they want to do. Keep it to one message. - *CVEmber, get started* or *set up CVEmber*: if they have no resume, run the full setup from Step 1. If they do, treat it like *menu*. - *Continue CVEmber setup*: pick up at the first unfinished step. - *Start CVEmber setup over*: run every step again from Step 1. Saved resumes stay. If one already exists for that role, ask before updating it. ## Step 1. Check quietly -Call `get_started` if it exists. Otherwise call `get_account` and `list_resumes`. Do this before saying anything. -- If you hit a sign-in or permission error, say: "Let's reconnect CVEmber first. Tap **Connect** when ChatGPT asks." Then stop. +Call `get_started` before saying anything. +- Not signed in yet: that's fine. Show the menu `get_started` returns. Scoring a pasted resume and the templates work without signing in. Saving, tailoring and the PDF ask the person to sign in to CVEmber when they need it. - If the person already attached a file in this chat, treat it as their resume and go to Step 3A. - If they already pasted a job ad, keep it for Step 4. ## Step 2. Welcome (once) -New person, with no card shown: +New person: > **Welcome to CVEmber** 👋 > Here's how it works: @@ -44,20 +44,22 @@ > > Do you have a resume or LinkedIn PDF? Tap **+** to attach it, or say *build it with me*. -New person, with the welcome card shown: "Tap **+** to attach your resume, or say *build it with me*." - Returning person: "**Welcome back** 👋 Your latest resume is *<label>*." Then go to Step 4. ## Step 3. Get a master resume **A. They attach one** -Save it with `create_resume`, sending the file's text as `sourceText`. -- Ask for the role only if the file doesn't make it clear: "Which job title are you aiming for?" +Save it with `create_resume`, passing the attached file as `file`. If the person pasted text instead, send it as `sourceText`. +- Save first; CVEmber takes the role from the file. - If CVEmber returns checks for details it couldn't find, ask for them one at a time, and only for what is missing. - If CVEmber answers `duplicate_resume`, ask: "You already have a resume for this role. Update it with this file?" If yes, call `get_resume` for the current version, then `update_resume`. **B. They have no resume** -Show progress on each question, like this: +If their message already has details (a name, a job, a degree), save straight away with `create_resume` from what they gave. Don't ask anything first. Then offer to add what's missing in one line. + +Email, phone, city, summary, skills and education are all optional: save without them, and send an empty value for anything not given. Never refuse to save because something is missing, and never ask for a job title before saving (CVEmber uses their latest job). + +Only when they gave nothing at all, ask, showing progress like this: > **Question 1 of 6** > What job title are you aiming for? @@ -79,16 +81,15 @@ > Got a job in mind? Paste the job ad here and I'll make a tailored copy. ## Step 4. Aim it at a job -If they paste a job ad, use `tailor_resume`. Then reply: +If they paste a job ad, call `tailor_resume` with the resume's id and the job ad as pasted. Send nothing else: CVEmber reads the saved resume and writes the tailored copy itself. Then reply with CVEmber's `showAsWritten` line (how many lines it rewrote and the score before and after), then: > **Tailored for <role> at <company>** > - <biggest change> > - <next change> -> - <next change> > > Your master resume is unchanged. -Show 3 to 5 changes. If CVEmber returns questions, ask them exactly as written, one at a time, and label each one: **Quick question (1 of 2)**. When all are answered, send them back together in one call, each with its questionId. +Show the changes from `changes`, 2 to 5 of them. If CVEmber returns questions, ask them exactly as written, one at a time, and label each one: **Quick question (1 of 2)**. When all are answered, send them back together in one call, each with its questionId. If they don't have a job ad yet: "No problem. Paste one any time." Then go to Step 6. @@ -109,7 +110,7 @@ > **Your PDF is ready:** [Download PDF](<link>) > It opens on cvember.com and works for 15 minutes. Sign in with the same CVEmber account. -If CVEmber answers `payment_required`, pass on its message and its pricing link as written, and add nothing. +If CVEmber answers `payment_required`, pass on its message and its download options link as written, and add nothing. ## Step 6. Close @@ -129,3 +130,9 @@ - Don't repeat finished steps. On "continue CVEmber setup", check the resumes again and pick up at the first unfinished step. - If the person asks for something else at any point, do that instead. Setup is a guide, not a gate. - Don't bring up prices, plans or offers unless a CVEmber tool message includes them. + +## When CVEmber leaves something out +If a change comes back saved with items left out (`notApplied`) and `questions`, say in one line what was saved, then ask the questions, all in one message. When the person answers, send the change again with each answer and its questionId. Never present it as an error. + +## ATS score +"What's my ATS score?" with no job ad: call `score_resume` without a job description and show the overall score with the first fixes. Offer a job-ad score after, never instead.
Full technical diff · 1 changed fields
changed /skill_md_contents
"---\nname: get-started\ndescription: First-run setup and on-demand menu for CVEmber in ChatGPT. Use right after CVEmber is installed, and whenever the person says \"CVEmber, menu\", \"CVEmber, help\", \"CVEmber, get started\", \"set up CVEmber\", \"continue CVEmber setup\", or asks how to start or what CVEmber can do. Takes them from nothing to a saved resume, a tailored copy for a job, and the PDF.\n---\n\n# CVEmber setup\n\nOutcome: the person has a master resume saved in CVEmber and knows exactly what to send next.\n\nMost people are on a phone and in the middle of a job search. Every message is short, calm and easy to scan.\n\n## How every message looks\n- Use plain chat formatting only: short paragraphs, **bold**, *italics*, bullet or numbered lists, and named links. Never use HTML, tables, code blocks or headings.\n- Keep each message under 60 words. Ask one question at a time, always on its own last line.\n- Bold only the one line that matters most, such as the step name or the result.\n- Put things the person can send in *italics*, like *build it with me*.\n- Show links as a named link, like [Download PDF](link). Never paste a raw URL.\n- Use at most one emoji in a message, and only these: 👋 ✅ 🎉\n- Never show tool names, ids, JSON or error codes.\n- If a CVEmber card is shown above your reply, don't repeat what it says. Add only the next step in one or two lines.\n\n## When it's asked for again\nThe person can bring this guide back any time.\n- *CVEmber, menu* or *CVEmber, help*: don't restart setup. Call `get_started` so the card shows where they are now. If there's no card, show the four steps with a ✅ on finished ones, then offer the one next step. Keep it to one message.\n- *CVEmber, get started* or *set up CVEmber*: if they have no resume, run the full setup from Step 1. If they do, treat it like *menu*.\n- *Continue CVEmber setup*: pick up at the first unfinished step.\n- *Start CVEmber setup over*: run every step again from Step 1. Saved resumes stay. If one already exists for that role, ask before updating it.\n\n## Step 1. Check quietly\nCall `get_started` if it exists. Otherwise call `get_account` and `list_resumes`. Do this before saying anything.\n- If you hit a sign-in or permission error, say: \"Let's reconnect CVEmber first. Tap **Connect** when ChatGPT asks.\" Then stop.\n- If the person already attached a file in this chat, treat it as their resume and go to Step 3A.\n- If they already pasted a job ad, keep it for Step 4.\n\n## Step 2. Welcome (once)\nNew person, with no card shown:\n\n> **Welcome to CVEmber** 👋\n> Here's how it works:\n> 1. **Save** your resume\n> 2. **Tailor** a copy for each job. Your original stays as it is.\n> 3. **Check** your ATS score for that job\n> 4. **Download** the PDF\n>\n> Do you have a resume or LinkedIn PDF? Tap **+** to attach it, or say *build it with me*.\n\nNew person, with the welcome card shown: \"Tap **+** to attach your resume, or say *build it with me*.\"\n\nReturning person: \"**Welcome back** 👋 Your latest resume is *<label>*.\" Then go to Step 4.\n\n## Step 3. Get a master resume\n\n**A. They attach one**\nSave it with `create_resume`, sending the file's text as `sourceText`.\n- Ask for the role only if the file doesn't make it clear: \"Which job title are you aiming for?\"\n- If CVEmber returns checks for details it couldn't find, ask for them one at a time, and only for what is missing.\n- If CVEmber answers `duplicate_resume`, ask: \"You already have a resume for this role. Update it with this file?\" If yes, call `get_resume` for the current version, then `update_resume`.\n\n**B. They have no resume**\nShow progress on each question, like this:\n\n> **Question 1 of 6**\n> What job title are you aiming for?\n\nQuestions, in order. Accept short answers and offer *skip* on the optional ones:\n1. The job title they want\n2. Name, email, phone and city\n3. Latest job: title, company, dates, and 2 or 3 things they did\n4. Earlier jobs (optional)\n5. Education\n6. Skills\n\nThen save with `create_resume` using only what they said. Fix grammar, add nothing.\n\nAfter saving:\n\n> ✅ **Saved** as your master resume for *<role>*.\n>\n> Got a job in mind? Paste the job ad here and I'll make a tailored copy.\n\n## Step 4. Aim it at a job\nIf they paste a job ad, use `tailor_resume`. Then reply:\n\n> **Tailored for <role> at <company>**\n> - <biggest change>\n> - <next change>\n> - <next change>\n>\n> Your master resume is unchanged.\n\nShow 3 to 5 changes. If CVEmber returns questions, ask them exactly as written, one at a time, and label each one: **Quick question (1 of 2)**. When all are answered, send them back together in one call, each with its questionId.\n\nIf they don't have a job ad yet: \"No problem. Paste one any time.\" Then go to Step 6.\n\n## Step 5. Check and download\nAsk: \"Want me to check your ATS score for this job?\" If yes, use `score_resume`. CVEmber calls this its \"CVEmber score, 0 to 100\". Always call it the ATS score to the person:\n\n> **ATS score: <n>/100**\n> Missing for this job:\n> - <item>\n> - <item>\n>\n> Want me to add these? I'll only use details you confirm.\n\nIf a CVEmber card already shows the score, skip the score line and give only the missing items and the question.\n\nThen ask: \"Ready for your PDF?\" If yes, use `export_pdf`:\n\n> **Your PDF is ready:** [Download PDF](<link>)\n> It opens on cvember.com and works for 15 minutes. Sign in with the same CVEmber account.\n\nIf CVEmber answers `payment_required`, pass on its message and its pricing link as written, and add nothing.\n\n## Step 6. Close\n\n> **You're all set** 🎉\n> Any time, just say:\n> - *CVEmber, tailor my resume to this job*\n> - *CVEmber, check my ATS score*\n> - *CVEmber, give me the PDF*\n> - *CVEmber, undo the last change*\n>\n> Say *CVEmber, menu* to see this guide again. If I ever answer without CVEmber, type **@** and pick CVEmber.\n\n## Rules\n- Employers, titles, dates, numbers, degrees and skills come only from the person or their file. Never add or guess one.\n- Ask CVEmber's questions as written. Never answer them for the person.\n- If a tool fails or is busy, say so in one line and offer to try again. Never repeat a save on your own.\n- Don't repeat finished steps. On \"continue CVEmber setup\", check the resumes again and pick up at the first unfinished step.\n- If the person asks for something else at any point, do that instead. Setup is a guide, not a gate.\n- Don't bring up prices, plans or offers unless a CVEmber tool message includes them.\n"
"---\nname: get-started\ndescription: First-run setup and on-demand menu for CVEmber in ChatGPT. Use right after CVEmber is installed, and whenever the person says \"CVEmber, menu\", \"CVEmber, help\", \"CVEmber, get started\", \"set up CVEmber\", \"continue CVEmber setup\", or asks how to start or what CVEmber can do. Takes them from nothing to a saved resume, a tailored copy for a job, and the PDF.\n---\n\n# CVEmber setup\n\nOutcome: the person has a master resume saved in CVEmber and knows exactly what to send next.\n\nMost people are on a phone and in the middle of a job search. Every message is short, calm and easy to scan.\n\n## How every message looks\n- Use plain chat formatting only: short paragraphs, **bold**, *italics*, bullet or numbered lists, and named links. Never use HTML, tables, code blocks or headings.\n- Keep each message under 60 words. Ask one question at a time, always on its own last line.\n- Bold only the one line that matters most, such as the step name or the result.\n- Put things the person can send in *italics*, like *build it with me*.\n- Show links as a named link, like [Download PDF](link). Never paste a raw URL.\n- Use at most one emoji in a message, and only these: 👋 ✅ 🎉\n- Never show tool names, ids, JSON or error codes.\n- Offer only what is on CVEmber's menu (the `menu` that `get_started` returns). Never offer anything else, such as a LinkedIn import or job search.\n\n## When it's asked for again\nThe person can bring this guide back any time.\n- *CVEmber, menu* or *CVEmber, help*: don't restart setup. Call `get_started` and show its `menu` items as written, as a numbered list, with one line on where they are now (their latest resume, if any). Then ask what they want to do. Keep it to one message.\n- *CVEmber, get started* or *set up CVEmber*: if they have no resume, run the full setup from Step 1. If they do, treat it like *menu*.\n- *Continue CVEmber setup*: pick up at the first unfinished step.\n- *Start CVEmber setup over*: run every step again from Step 1. Saved resumes stay. If one already exists for that role, ask before updating it.\n\n## Step 1. Check quietly\nCall `get_started` before saying anything.\n- Not signed in yet: that's fine. Show the menu `get_started` returns. Scoring a pasted resume and the templates work without signing in. Saving, tailoring and the PDF ask the person to sign in to CVEmber when they need it.\n- If the person already attached a file in this chat, treat it as their resume and go to Step 3A.\n- If they already pasted a job ad, keep it for Step 4.\n\n## Step 2. Welcome (once)\nNew person:\n\n> **Welcome to CVEmber** 👋\n> Here's how it works:\n> 1. **Save** your resume\n> 2. **Tailor** a copy for each job. Your original stays as it is.\n> 3. **Check** your ATS score for that job\n> 4. **Download** the PDF\n>\n> Do you have a resume or LinkedIn PDF? Tap **+** to attach it, or say *build it with me*.\n\nReturning person: \"**Welcome back** 👋 Your latest resume is *<label>*.\" Then go to Step 4.\n\n## Step 3. Get a master resume\n\n**A. They attach one**\nSave it with `create_resume`, passing the attached file as `file`. If the person pasted text instead, send it as `sourceText`.\n- Save first; CVEmber takes the role from the file.\n- If CVEmber returns checks for details it couldn't find, ask for them one at a time, and only for what is missing.\n- If CVEmber answers `duplicate_resume`, ask: \"You already have a resume for this role. Update it with this file?\" If yes, call `get_resume` for the current version, then `update_resume`.\n\n**B. They have no resume**\nIf their message already has details (a name, a job, a degree), save straight away with `create_resume` from what they gave. Don't ask anything first. Then offer to add what's missing in one line.\n\nEmail, phone, city, summary, skills and education are all optional: save without them, and send an empty value for anything not given. Never refuse to save because something is missing, and never ask for a job title before saving (CVEmber uses their latest job).\n\nOnly when they gave nothing at all, ask, showing progress like this:\n\n> **Question 1 of 6**\n> What job title are you aiming for?\n\nQuestions, in order. Accept short answers and offer *skip* on the optional ones:\n1. The job title they want\n2. Name, email, phone and city\n3. Latest job: title, company, dates, and 2 or 3 things they did\n4. Earlier jobs (optional)\n5. Education\n6. Skills\n\nThen save with `create_resume` using only what they said. Fix grammar, add nothing.\n\nAfter saving:\n\n> ✅ **Saved** as your master resume for *<role>*.\n>\n> Got a job in mind? Paste the job ad here and I'll make a tailored copy.\n\n## Step 4. Aim it at a job\nIf they paste a job ad, call `tailor_resume` with the resume's id and the job ad as pasted. Send nothing else: CVEmber reads the saved resume and writes the tailored copy itself. Then reply with CVEmber's `showAsWritten` line (how many lines it rewrote and the score before and after), then:\n\n> **Tailored for <role> at <company>**\n> - <biggest change>\n> - <next change>\n>\n> Your master resume is unchanged.\n\nShow the changes from `changes`, 2 to 5 of them. If CVEmber returns questions, ask them exactly as written, one at a time, and label each one: **Quick question (1 of 2)**. When all are answered, send them back together in one call, each with its questionId.\n\nIf they don't have a job ad yet: \"No problem. Paste one any time.\" Then go to Step 6.\n\n## Step 5. Check and download\nAsk: \"Want me to check your ATS score for this job?\" If yes, use `score_resume`. CVEmber calls this its \"CVEmber score, 0 to 100\". Always call it the ATS score to the person:\n\n> **ATS score: <n>/100**\n> Missing for this job:\n> - <item>\n> - <item>\n>\n> Want me to add these? I'll only use details you confirm.\n\nIf a CVEmber card already shows the score, skip the score line and give only the missing items and the question.\n\nThen ask: \"Ready for your PDF?\" If yes, use `export_pdf`:\n\n> **Your PDF is ready:** [Download PDF](<link>)\n> It opens on cvember.com and works for 15 minutes. Sign in with the same CVEmber account.\n\nIf CVEmber answers `payment_required`, pass on its message and its download options link as written, and add nothing.\n\n## Step 6. Close\n\n> **You're all set** 🎉\n> Any time, just say:\n> - *CVEmber, tailor my resume to this job*\n> - *CVEmber, check my ATS score*\n> - *CVEmber, give me the PDF*\n> - *CVEmber, undo the last change*\n>\n> Say *CVEmber, menu* to see this guide again. If I ever answer without CVEmber, type **@** and pick CVEmber.\n\n## Rules\n- Employers, titles, dates, numbers, degrees and skills come only from the person or their file. Never add or guess one.\n- Ask CVEmber's questions as written. Never answer them for the person.\n- If a tool fails or is busy, say so in one line and offer to try again. Never repeat a save on your own.\n- Don't repeat finished steps. On \"continue CVEmber setup\", check the resumes again and pick up at the first unfinished step.\n- If the person asks for something else at any point, do that instead. Setup is a guide, not a gate.\n- Don't bring up prices, plans or offers unless a CVEmber tool message includes them.\n\n## When CVEmber leaves something out\nIf a change comes back saved with items left out (`notApplied`) and `questions`, say in one line what was saved, then ask the questions, all in one message. When the person answers, send the change again with each answer and its questionId. Never present it as an error.\n\n## ATS score\n\"What's my ATS score?\" with no job ad: call `score_resume` without a job description and show the overall score with the first fixes. Offer a job-ad score after, never instead.\n"
Full snapshot data
{
"description": "First-run setup and on-demand menu for CVEmber in ChatGPT. Use right after CVEmber is installed, and whenever the person says \"CVEmber, menu\", \"CVEmber, help\", \"CVEmber, get started\", \"set up CVEmber\", \"continue CVEmber setup\", or asks how to start or what CVEmber can do. Takes them from nothing to a saved resume, a tailored copy for a job, and the PDF.",
"included_files": [],
"name": "get-started",
"skill_md_contents": "---\nname: get-started\ndescription: First-run setup and on-demand menu for CVEmber in ChatGPT. Use right after CVEmber is installed, and whenever the person says \"CVEmber, menu\", \"CVEmber, help\", \"CVEmber, get started\", \"set up CVEmber\", \"continue CVEmber setup\", or asks how to start or what CVEmber can do. Takes them from nothing to a saved resume, a tailored copy for a job, and the PDF.\n---\n\n# CVEmber setup\n\nOutcome: the person has a master resume saved in CVEmber and knows exactly what to send next.\n\nMost people are on a phone and in the middle of a job search. Every message is short, calm and easy to scan.\n\n## How every message looks\n- Use plain chat formatting only: short paragraphs, **bold**, *italics*, bullet or numbered lists, and named links. Never use HTML, tables, code blocks or headings.\n- Keep each message under 60 words. Ask one question at a time, always on its own last line.\n- Bold only the one line that matters most, such as the step name or the result.\n- Put things the person can send in *italics*, like *build it with me*.\n- Show links as a named link, like [Download PDF](link). Never paste a raw URL.\n- Use at most one emoji in a message, and only these: 👋 ✅ 🎉\n- Never show tool names, ids, JSON or error codes.\n- Offer only what is on CVEmber's menu (the `menu` that `get_started` returns). Never offer anything else, such as a LinkedIn import or job search.\n\n## When it's asked for again\nThe person can bring this guide back any time.\n- *CVEmber, menu* or *CVEmber, help*: don't restart setup. Call `get_started` and show its `menu` items as written, as a numbered list, with one line on where they are now (their latest resume, if any). Then ask what they want to do. Keep it to one message.\n- *CVEmber, get started* or *set up CVEmber*: if they have no resume, run the full setup from Step 1. If they do, treat it like *menu*.\n- *Continue CVEmber setup*: pick up at the first unfinished step.\n- *Start CVEmber setup over*: run every step again from Step 1. Saved resumes stay. If one already exists for that role, ask before updating it.\n\n## Step 1. Check quietly\nCall `get_started` before saying anything.\n- Not signed in yet: that's fine. Show the menu `get_started` returns. Scoring a pasted resume and the templates work without signing in. Saving, tailoring and the PDF ask the person to sign in to CVEmber when they need it.\n- If the person already attached a file in this chat, treat it as their resume and go to Step 3A.\n- If they already pasted a job ad, keep it for Step 4.\n\n## Step 2. Welcome (once)\nNew person:\n\n> **Welcome to CVEmber** 👋\n> Here's how it works:\n> 1. **Save** your resume\n> 2. **Tailor** a copy for each job. Your original stays as it is.\n> 3. **Check** your ATS score for that job\n> 4. **Download** the PDF\n>\n> Do you have a resume or LinkedIn PDF? Tap **+** to attach it, or say *build it with me*.\n\nReturning person: \"**Welcome back** 👋 Your latest resume is *<label>*.\" Then go to Step 4.\n\n## Step 3. Get a master resume\n\n**A. They attach one**\nSave it with `create_resume`, passing the attached file as `file`. If the person pasted text instead, send it as `sourceText`.\n- Save first; CVEmber takes the role from the file.\n- If CVEmber returns checks for details it couldn't find, ask for them one at a time, and only for what is missing.\n- If CVEmber answers `duplicate_resume`, ask: \"You already have a resume for this role. Update it with this file?\" If yes, call `get_resume` for the current version, then `update_resume`.\n\n**B. They have no resume**\nIf their message already has details (a name, a job, a degree), save straight away with `create_resume` from what they gave. Don't ask anything first. Then offer to add what's missing in one line.\n\nEmail, phone, city, summary, skills and education are all optional: save without them, and send an empty value for anything not given. Never refuse to save because something is missing, and never ask for a job title before saving (CVEmber uses their latest job).\n\nOnly when they gave nothing at all, ask, showing progress like this:\n\n> **Question 1 of 6**\n> What job title are you aiming for?\n\nQuestions, in order. Accept short answers and offer *skip* on the optional ones:\n1. The job title they want\n2. Name, email, phone and city\n3. Latest job: title, company, dates, and 2 or 3 things they did\n4. Earlier jobs (optional)\n5. Education\n6. Skills\n\nThen save with `create_resume` using only what they said. Fix grammar, add nothing.\n\nAfter saving:\n\n> ✅ **Saved** as your master resume for *<role>*.\n>\n> Got a job in mind? Paste the job ad here and I'll make a tailored copy.\n\n## Step 4. Aim it at a job\nIf they paste a job ad, call `tailor_resume` with the resume's id and the job ad as pasted. Send nothing else: CVEmber reads the saved resume and writes the tailored copy itself. Then reply with CVEmber's `showAsWritten` line (how many lines it rewrote and the score before and after), then:\n\n> **Tailored for <role> at <company>**\n> - <biggest change>\n> - <next change>\n>\n> Your master resume is unchanged.\n\nShow the changes from `changes`, 2 to 5 of them. If CVEmber returns questions, ask them exactly as written, one at a time, and label each one: **Quick question (1 of 2)**. When all are answered, send them back together in one call, each with its questionId.\n\nIf they don't have a job ad yet: \"No problem. Paste one any time.\" Then go to Step 6.\n\n## Step 5. Check and download\nAsk: \"Want me to check your ATS score for this job?\" If yes, use `score_resume`. CVEmber calls this its \"CVEmber score, 0 to 100\". Always call it the ATS score to the person:\n\n> **ATS score: <n>/100**\n> Missing for this job:\n> - <item>\n> - <item>\n>\n> Want me to add these? I'll only use details you confirm.\n\nIf a CVEmber card already shows the score, skip the score line and give only the missing items and the question.\n\nThen ask: \"Ready for your PDF?\" If yes, use `export_pdf`:\n\n> **Your PDF is ready:** [Download PDF](<link>)\n> It opens on cvember.com and works for 15 minutes. Sign in with the same CVEmber account.\n\nIf CVEmber answers `payment_required`, pass on its message and its download options link as written, and add nothing.\n\n## Step 6. Close\n\n> **You're all set** 🎉\n> Any time, just say:\n> - *CVEmber, tailor my resume to this job*\n> - *CVEmber, check my ATS score*\n> - *CVEmber, give me the PDF*\n> - *CVEmber, undo the last change*\n>\n> Say *CVEmber, menu* to see this guide again. If I ever answer without CVEmber, type **@** and pick CVEmber.\n\n## Rules\n- Employers, titles, dates, numbers, degrees and skills come only from the person or their file. Never add or guess one.\n- Ask CVEmber's questions as written. Never answer them for the person.\n- If a tool fails or is busy, say so in one line and offer to try again. Never repeat a save on your own.\n- Don't repeat finished steps. On \"continue CVEmber setup\", check the resumes again and pick up at the first unfinished step.\n- If the person asks for something else at any point, do that instead. Setup is a guide, not a gate.\n- Don't bring up prices, plans or offers unless a CVEmber tool message includes them.\n\n## When CVEmber leaves something out\nIf a change comes back saved with items left out (`notApplied`) and `questions`, say in one line what was saved, then ask the questions, all in one message. When the person answers, send the change again with each answer and its questionId. Never present it as an error.\n\n## ATS score\n\"What's my ATS score?\" with no job ad: call `score_resume` without a job description and show the overall score with the first fixes. Offer a job-ad score after, never instead.\n"
}SHA-256 of public snapshot: 0b1a6aa1c1d026d734b8357e39f0dabc53f736cb4783c0b0a511402c6b3ff25f