Update to Breakthrough

{
  "description": "Looks up one person in Breakthrough by name, email address, or LinkedIn URL and returns their stored record — role, employer, linked company. Answers \"is this person already in the system\" and pins down which person the user means before acting. For a factual question about who a named person is, what they do, or where they work, this returns the user's own record of them. An open-ended \"what do we know about\" or \"how should I approach\" them is answer; so is writing them an email or LinkedIn message, or notes on a call with them; what they said on a call is research-transcripts.",
  "included_files": [],
  "name": "find-contact",
  "skill_md_contents": "---\nname: find-contact\ndescription: >-\n  Looks up one person in Breakthrough by name, email address, or LinkedIn URL and\n  returns their stored record — role, employer, linked company. Answers \"is this person\n  already in the system\" and pins down which person the user means before acting. For\n  a factual question about who a named person is, what they do, or where they work,\n  this returns the user's own record of them.\n  An open-ended \"what do we know about\" or \"how should I approach\" them is answer; so\n  is writing them an email or LinkedIn message, or notes on a call with them; what they\n  said on a call is research-transcripts.\nwhen_to_use: >-\n  Use when the user says \"who is this\", \"do we have Jane\", \"look up jane@acme.com\",\n  \"what's her title\", \"is he in the system\", \"which Jane do we know\", \"pull up her\n  record\", \"where does Matt work\". Also use for a factual question about someone the\n  user sells to or works with (a contact, prospect or customer): Breakthrough holds the\n  user's own record of them. Do NOT use to add\n  someone new; that is import-contact. Do NOT use to update a record that has gone\n  stale; that is refresh-contact. Do NOT use for what was said\n  on calls with them; that is research-transcripts. Do NOT use for questions needing\n  judgment about the person rather than their record; that is answer.\n---\n\n# Find a contact\n\nWraps the `contact_profile` MCP tool.\n\n## Usage\n\nPass the user's phrasing as `query`. The tool extracts embedded email addresses and\nLinkedIn URLs itself, so `\"do we have anything on jane@acme.com\"` works as well as\n`\"jane@acme.com\"` — no need to strip the sentence down first.\n\n`limit_candidates` defaults to 5. Raise it when a common name returns an ambiguous set.\n\nWhen the request is vague about who is meant, call `resolve_prompt_context` first — it\ncross-references contacts against businesses and returns concrete recommendations, which\ndisambiguates \"the CTO at that fintech\" better than a name search can.\n\n## Reporting\n\nReport what resolved: full name, contact ID, role, employer, LinkedIn URL.\n\n**If several candidates come back, present them and ask.** Do not pick the top hit and\nproceed — the downstream action is usually an email to a real person, and picking wrong\nmeans writing to the wrong one.\n\n**If nothing resolves, say so plainly.** \"No contact matching that in Breakthrough\" is\nthe first thing to say. If the user asked what *they* have on file, stop there. If they\nasked a factual question about the person (where someone works, what their title is),\nthe web may still answer it: do so, but label it as not from Breakthrough, never as if\nit came from the CRM. Either way, offer the import path (the import-contact skill) if a\nLinkedIn URL or email is available.\n"
}