Update to Formatix AI

{
  "description": "Change a candidate profile or formatted CV that Formatix already made - rewrite or shorten the summary, correct a date or job title, add a qualification, reorder roles, or give the candidate a new photo - and get the same document back in the same template at no credit cost. Use when the user says \"fix\", \"correct\", \"change\", \"update\", \"shorten\" or \"add\" something in a CV, profile or shortlist Formatix produced.",
  "included_files": [],
  "name": "fix-a-document",
  "skill_md_contents": "---\nname: fix-a-document\ndescription: Change a candidate profile or formatted CV that Formatix already made - rewrite or shorten the summary, correct a date or job title, add a qualification, reorder roles, or give the candidate a new photo - and get the same document back in the same template at no credit cost. Use when the user says \"fix\", \"correct\", \"change\", \"update\", \"shorten\" or \"add\" something in a CV, profile or shortlist Formatix produced.\n---\n\n# Fix a document Formatix made\n\nDone when: the user has the corrected document's new download link and a one-line\nsummary of what changed - or a clear explanation of why the change needs a new\ndocument and what that costs.\n\nExplicit instructions from the user take priority over this skill.\n\n## Ground rules\n\n- Reply in the user's language; keep the document's language unless asked.\n- Changes use only facts the user gave or that are in the candidate's CV.\n- A correction is ALWAYS `edit_formatted_cv` - never `fill_template` or `format_cv`\n  again (that is a new document and charges credits again).\n- Edits are free, up to 3 per document (a photo counts as one). At most about a fifth\n  of the text may change. The candidate's name cannot change.\n- Studio documents (`template_type` `user_template`) cannot be edited this way.\n\n## Steps\n\n1. **Find the document.** Use the `record_id` from this conversation. If you do not\n   have it, ask the user which document (Formatix needs the record from the result\n   that made it).\n2. **Read it:** `get_cv_details` with the `record_id`: the details per candidate\n   (`candidate_index`), whether the photo can change, how many changes are left.\n3. **Write the change** yourself in the same shape as the details: send only the\n   fields that change (a list field is sent whole), for example\n   `[{\"candidate_index\": 0, \"details\": {\"Summary\": \"...\"}}]`.\n4. **Apply:** `edit_formatted_cv` with `record_id` and `changes`. Each call rebuilds\n   the document once and uses one of its 3 changes, so put all the corrections the\n   user asked for into one call.\n5. **Photo:** `set_candidate_photo` with the photo the user attached (`photo_file`)\n   or a public `photo_url`, and `candidate_index`. Only if `get_cv_details` says the\n   template has a photo slot; otherwise say the template has no place for a photo.\n6. **Report:** the new link (works for an hour) and what changed; ask the user to\n   check it. Earlier versions are kept in Formatix.\n\n## Ask first - never decide alone\n\n- **Rename / different candidate / big rewrite / another template / another\n  language:** this cannot be an edit. Say so, say it is a new document costing 1\n  credit per candidate, and wait for a yes. Then use format-cvs (or\n  translate-candidate-profile / blind-candidate-profile).\n- If that new fill is refused with `looks_like_correction` (same candidate, same\n  template, within the hour), re-send with `confirm_new_document=true` only after the\n  user confirms the new charge.\n- **No changes left:** say so and offer a new document (credits) or editing the\n  downloaded file by hand.\n- Never change the template itself here; template changes are build-our-template.\n"
}