Update to Unify

{
  "name": "crm",
  "description": "CRM and record management with Unify, read Salesforce/HubSpot (owners, stages, deals, custom fields, \"what's in my CRM\"), write CRM records, upsert companies/people into Unify, and export to Lists. Use when the user asks about CRM data, wants records saved or updated, or wants a result set exported to a List or their CRM.",
  "included_files": [],
  "skill_md_contents": "---\nname: crm\ndescription: CRM and record management with Unify, read Salesforce/HubSpot (owners, stages, deals, custom fields, \"what's in my CRM\"), write CRM records, upsert companies/people into Unify, and export to Lists. Use when the user asks about CRM data, wants records saved or updated, or wants a result set exported to a List or their CRM.\n---\n\n# CRM and records\n\nCRM briefs go through `run_agent` (see `agent-runs`). Unify connects to Salesforce\nand HubSpot and also keeps its own canonical company/person records and Lists.\n\n> **Deterministic alternative.** If the user wants exact, repeatable reads/writes\n> of their **Unify objects and records** — not a natural-language task — the\n> public API exposes direct tools: `list_objects` / `get_object` and their\n> attributes, `get_object_record` / `create_object_record` / `update_object_record`\n> / `upsert_object_record` / `find_unique_object_record` / `delete_object_record`,\n> and the async **Bulk API** tools for exporting or syncing many records at once.\n> The agent briefs below remain the path for complex workflows and anything\n> needing reasoning.\n\n## Reads (free, live)\n\nIf the workspace has a connected CRM, briefs like these work directly:\n\n- \"Which of these accounts exist in our Salesforce, and who owns them?\"\n- \"Open opportunities past stage 2 closing this quarter.\"\n- \"What picklist values does the deal-stage field have?\"\n- Joins with Unify signals are free too: \"CRM accounts with website intent this\n  month that have no open opportunity.\"\n\n## Writes\n\nCRM writes are available on Unify's Business plan and behave as\nsearch-then-create-or-update (matching by domain, email, or record ID; the agent\nhandles dedupe). Rules:\n\n- Log activities too: \"log this call/email against the contact in HubSpot.\"\n\n## Unify records and Lists\n\n- **Save to Unify**: \"save these companies/people as Unify records.\" Companies\n  need a domain; people need an email. The agent previews EXISTING/NEW/INVALID\n  classifications before committing.\n- **Lists**: named, saved collections in the Unify app. \"Export this DataTable to\n  a List called Q3 targets\" (the export previews counts: new, already in list,\n  duplicates, invalid) before committing. Say whether creating brand-new records\n  is allowed or the export should only link existing ones.\n- **Personas**: tenant-level title sets. \"Update our 'economic buyer' persona to\n  include VP Finance titles\" is a valid brief; edits are versioned and reversible.\n"
}