Update to Breakthrough

{
  "description": "Looks up one company in Breakthrough by name, website domain, or LinkedIn company URL and returns its stored profile. Answers \"is this account already in the system\" and pins down which company the user means before acting.",
  "included_files": [],
  "name": "find-business",
  "skill_md_contents": "---\nname: find-business\ndescription: >-\n  Looks up one company in Breakthrough by name, website domain, or LinkedIn company URL\n  and returns its stored profile. Answers \"is this account already in the system\" and\n  pins down which company the user means before acting.\nwhen_to_use: >-\n  Use when the user says \"pull up Acme\", \"do we have anything on acme.com\", \"look up\n  this company\", \"are we already working with them\", \"what do we have on that account\".\n  Do NOT use to find a person; that is find-contact. Do NOT use for what was said on\n  calls with the account; that is research-transcripts. Do NOT use for questions\n  needing judgment about the account rather than its record; that is answer.\n---\n\n# Find a business\n\nWraps the `business_profile` MCP tool.\n\n## Usage\n\nPass the user's phrasing as `query`. The tool extracts domains and LinkedIn company URLs\nfrom the text itself, so a full sentence works.\n\n`limit_candidates` defaults to 5.\n\nFor \"who do we know at X\", call `resolve_prompt_context` instead — it cross-references\nbusinesses to contacts in one pass, which `business_profile` alone does not do.\n\n## Reporting\n\nReport the resolved business and, where the data includes them, the contacts tied to it.\n\nIf several candidates come back, present them and ask. If nothing resolves, say so —\ndon't substitute web results for CRM data without labelling them as such.\n"
}