Update to Captino

{
  "description": "Act on a Captino lead or contact - set its quality (Good, NotRelevant, Spam), move it through the pipeline (Lead to Opportunity, Customer or Lost), set the deal value, add a note, or schedule a meeting. Use when the user says \"mark X as opportunity\", \"this lead is spam\", \"we closed the deal with X\", \"set the value to\", \"add a note to\", \"book a meeting with\", or otherwise wants to update a contact.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 499
    }
  ],
  "name": "lead-followup",
  "skill_md_contents": "---\nname: lead-followup\ndescription: Act on a Captino lead or contact - set its quality (Good, NotRelevant, Spam), move it through the pipeline (Lead to Opportunity, Customer or Lost), set the deal value, add a note, or schedule a meeting. Use when the user says \"mark X as opportunity\", \"this lead is spam\", \"we closed the deal with X\", \"set the value to\", \"add a note to\", \"book a meeting with\", or otherwise wants to update a contact.\n---\n\n# Lead follow-up\n\nWrites to contacts through the Captino MCP server. Every change here is visible\nto the whole Captino account, so be precise about which contact you change and\nwhat you change.\n\n## Prerequisites\n\nUses the Captino MCP tools `list_contacts`, `get_contact`, `get_contact_options`,\n`update_contact` and `create_contact_meeting`. Needs **Contact: write** access\n(write implies read), granted when connecting Captino. If `update_contact` or\n`create_contact_meeting` is not listed, only read access was granted; tell the\nuser and point them to the `captino-setup` skill instead of trying workarounds.\n\n## Domain facts\n\n- `status` values: `Contact`, `Lead`, `Opportunity`, `Customer`, `Lost`.\n- `qualityStatus` values: `Pending`, `Good`, `NotRelevant`, `Spam`.\n- `value` is the monetary deal value (plain decimal, account currency).\n- `update_contact` changes only the arguments you pass. Omitted arguments keep\n  their value. **Exception:** `note` replaces the whole note.\n- `create_contact_meeting` takes `scheduledAt` as ISO 8601 with offset, optional\n  `title` and `note`, and updates the contact's `meetingDate` automatically.\n\n## Workflow\n\n### 1. Resolve the contact\n\nCall `list_contacts` with `query` set to the name, email or phone the user gave.\nExactly one match: continue. Several matches: show them (name, email, status,\ncreated) and ask which one. None: say so; do not create contacts, there is no\ntool for it.\n\n### 2. Show the current state before changing it\n\nCall `get_contact` and keep `status`, `qualityStatus`, `value`, `note` and\n`meetingDate`. Sanity-check the request against it:\n\n- Moving backwards in the pipeline (for example `Customer` → `Lead`) or to\n  `Lost` from `Customer` is unusual. Do it if asked, but say what the current\n  status is.\n- Setting `Spam` or `NotRelevant` on a contact with a non-zero deal value or a\n  scheduled meeting deserves a one-line heads-up.\n- If the user asks to \"add\" to the note, fetch the existing note and send the\n  existing text plus the addition; sending only the addition would erase it.\n\n### 3. Apply the change\n\n- Status, quality, value, name, email, phone, note: one `update_contact` call\n  with only the fields that change.\n- Meeting: `create_contact_meeting`. If the user gave no time, ask for it; do\n  not pick one. Use the user's timezone offset. Put the agenda in `note` and a\n  short label in `title`.\n- Closing a deal usually means two things: `status: Customer` and `value`. If\n  the user gives a value, send both in the same call.\n- Several contacts at once (for example \"mark all leads from yesterday as\n  Good\"): list them first, show the list, and get an explicit go-ahead before\n  looping. There is no bulk tool; make one call per contact and report any that\n  failed.\n\n### 4. Confirm\n\nReport before → after for the fields that changed, in one line per contact:\n\n> Anna Berg: Lead → Opportunity, value 0 → 12,000. Note kept.\n> Meeting scheduled 12 Sep 2026 10:00 (+02:00), \"Intro call\".\n\nIf a call failed (404 not found, 403 no write permission, validation error),\nquote the error and stop; do not retry with guessed data.\n"
}