Update to Formatix AI

{
  "description": "Turn a new search's intake or briefing-meeting notes, a job description or a call transcript into a branded position specification (role profile, candidate brief, job spec) and, if wanted, a \"we have been retained\" LinkedIn announcement draft. Use when a recruiter or executive search consultant says \"write the position spec\", \"new search intake\", \"turn my client meeting notes into a role profile\", \"draft the job spec for the CFO search\" or \"announce that we've been retained\".",
  "included_files": [],
  "name": "position-specification",
  "skill_md_contents": "---\nname: position-specification\ndescription: Turn a new search's intake or briefing-meeting notes, a job description or a call transcript into a branded position specification (role profile, candidate brief, job spec) and, if wanted, a \"we have been retained\" LinkedIn announcement draft. Use when a recruiter or executive search consultant says \"write the position spec\", \"new search intake\", \"turn my client meeting notes into a role profile\", \"draft the job spec for the CFO search\" or \"announce that we've been retained\".\n---\n\n# Position specification from intake notes\n\nDone when: the user has a position specification (Word + PDF) built only from their\nnotes, a list of the gaps to confirm with the client, and - only if asked - the\nretained-search announcement drafts. Nothing is posted.\n\nExplicit instructions from the user take priority over this skill.\n\n## Ground rules\n\n- Reply in the user's language. Write the brief in the language the user wants the\n  document in (default: the language of their notes).\n- Use only facts in the notes, JD or transcript. Never invent salary, bonus, equity,\n  reporting lines, team size, location, company facts or the client's name.\n- Cost: position specification 1 credit; announcement 1 credit. Say so before a step\n  the user did not ask for.\n- `request_id` on every credit-using call; reuse on retry.\n\n## Steps\n\n1. **Read the material** (pasted notes, attached file, or a meeting transcript or\n   email the user points to in a connected app such as Gmail, Outlook, OneDrive or\n   Google Drive - only what they point to).\n2. **Build the brief.** `role` (required - ask if missing), and only what the notes\n   support: `location`, `salary`, `reporting_line`, `must_haves` (short list),\n   `organisation_overview`, `search_reference`, `jd_text` (the user's JD text as\n   given), `consultants` (name, title, email, phone only as the user gives them),\n   `apply_url`. Ask whether the search is confidential if the notes do not say.\n3. **Confidential search:** `brief.confidential = true`, `client_name` (used only to\n   check the output) and `client_descriptor` (for example \"a PE-backed UK healthcare\n   group\"). Never write the client's name in your reply or any draft.\n4. **Show the brief** in two to six lines and the gaps you left out (\"no salary\n   given\"). If the user already asked for the document, go straight on.\n5. **Render.** `render_search_document` with `template_key`\n   `position-specification` and the brief; `kit_id` only if the user wants a client's\n   brand (`list_brand_kits`). Takes up to a few minutes.\n6. **Announcement (only if asked).** `create_launch_announcement` with the same brief:\n   two post drafts and graphics. Formatix does not post; the user posts after the\n   client agrees. Never post or publish for them.\n7. **Report.** Download links, the gaps to confirm with the client, and the offer to\n   draft the announcement or a candidate outreach teaser later\n   (formatix-recruitment-documents: appointment brief, role teaser).\n\n## Optional connected apps\n\nIf the user asks and has a CRM or ATS connected (HubSpot, Salesforce, Recruit CRM,\nManatal), you may read the job record to fill gaps the user confirms, or attach a\nnote that the specification was drafted. Do not create or change records unasked.\n"
}