Update to CRM Connector

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -5,27 +5,27 @@
 
 # Work with your records through AI Agents
 
-This belongs to part 2 of the plugin, **AI Agents inside one system**. With AI Agents a CRM Connector customer connects one of their own systems to the CRM Connector MCP server and the assistant works with its records: it reads their customer data and, with AI Agent, changes records when they ask and keeps automations running (see the `automate-my-system` skill). Nothing in AI Agents syncs records between two systems: that is an integration, part 1 of the plugin (`find_sync_options`, `plan_integration`). No system is open to every account. The customer requests their system, saying whether the assistant should read (AI Analyst) or also change records (AI Agent) and what it should do there; CRM Connector arranges the setup and enables it for their account, and then they sign in to it. The customer decides per system and per record type what the assistant may do: nothing, read, or read and change. Reading is the AI Analyst package; changing needs the AI Agent package and the customer's permission on the consent page.
+This belongs to part 2 of the plugin, **AI Agents inside one system**. With AI Agents a CRM Connector customer connects one of their own systems to the CRM Connector MCP server and the assistant works with its records: it reads their customer data and, with AI Agent, changes records when they ask and keeps automations running (see the `automate-my-system` skill). Nothing in AI Agents syncs records between two systems: that is an integration, part 1 of the plugin (`find_sync_options`, `plan_integration`). No system is open to every account. The customer requests their system, saying whether the assistant should read (AI Analyst) or also change records (AI Agent) and what it should do there; CRM Connector arranges the setup and enables it for their account, and then they sign in to it. The customer selects per system the record types the assistant may work with, each one read or read and change. Reading is the AI Analyst package; changing needs the AI Agent package and the customer's permission on the consent page.
 
 ## Start here
 
-- Call `list_ai_systems` first. It names the connected systems, their package (AI Analyst reads, AI Agent also changes records) and per record type what is allowed. Every other record tool takes the system id it returns.
+- Call `get_ai_agents_info` first; with `system` it also lists exactly what an agent can do in that system (per record type, its actions, what it cannot do and what its automations can use), so use that instead of guessing when someone asks what is possible. It names the connected systems, their package (AI Analyst reads, AI Agent also changes records) and per record type what is allowed. Every other record tool takes the system id it returns.
 - Always ask which AI agent the person means before you use a record tool, unless they named it in this conversation; when there is only one, name it and check. Never pick one yourself.
 - If no system is connected, pass on the tool's sentence and any link as given. Never name a system as available for AI Agents unless a tool answer names it for this account. Do not discuss prices, fees, plans or trials.
-- When the person is not signed in yet, or asks what AI Agents is, call `get_ai_access`: it explains both packages and how to request a system.
+- It also works without a sign in: it then explains both packages and how to request a system, and says the person's own AI agents are not shown. If they already have one, `search_records` asks them to sign in.
 - To ask for AI Agents for a system, offer `send_request` with kind `ai_access`: the system, `read` (AI Analyst) or `read_write` (AI Agent), and in the details what the assistant should do there. Show what will be sent and send it only after the person confirms. The form at https://crm-connector.com/platform/ai-access#request does the same. CRM Connector then arranges the setup and enables the system for their account, and they sign in to it in CRM Connector.
 
 ## Reading
 
 - "Which deals were won this month?", "Show the open quotes of this customer."
-- `describe_record_type` lists the fields of a record type, custom fields included.
-- `search_records` finds records, `get_record` reads one live.
+- `describe_record_type` lists the fields of a record type, the system's own and custom fields included; with `field_names` it gives the options of some of those fields, with `include` `stages` the pipelines and their stages, with `include` `users` the people records can be assigned to.
+- `search_records` finds records by text, by one of the system's own fields and a condition, or with `filters` for several conditions at once, and `sort_by` sorts them. To count, use `group_by` for the count per value of a field (open deals per stage), `sum_field` to add up a number field, or `count` for the total alone. `get_record` reads one live, with `fields` for some of the system's own fields.
 - `find_linked_records` finds the same record in the customer's other connected systems, through their syncs. Use it for questions across systems, such as won deals that have no invoice yet.
-- The system's own fields, stages, users, links and activities: `list_fields`, `get_record_fields`, `filter_records`, `list_stages`, `list_users`, `list_related_records` and `read_activities`. These are the same tools for every system and every record type (contacts, opportunities, invoices, estimates, jobs, appointments); a system says itself what it cannot do yet.
+- Links and activities: `list_related_records` and `read_activities`. A conversation: `list_related_records` with related conversation, then `read_conversation`. Tasks across all records: `search_tasks`. When a calendar has room: `find_free_slots`. These are the same tools for every system and every record type (contacts, opportunities, invoices, estimates, jobs, appointments); a system says itself what it cannot do yet.
 
 ## Changing (AI Agent only)
 
-1. Propose first. `propose_changes` for record fields, and `propose_field_update`, `propose_stage_move`, `propose_note`, `propose_task`, `propose_link` or `propose_unlink` for the rest. Nothing is written yet.
+1. Propose first, always with `propose_changes` and the `action` that fits: `set_fields` (the default) for record fields, `update_fields` for fields only the system has, `move_stage`, `add_note`, `add_task`, `update_task`, `log_activity` for a call or meeting that took place, `add_line_item`, `link_records` or `unlink_records`, one item per record. Nothing is written yet.
 2. Show the customer the before and after list from the answer, in full, and say so first when something would be sent to their own customers.
 3. Ask whether to go ahead. Only after a clear yes, call `apply_proposal` with the proposal id.
 4. When the answer says the customer must approve it themselves (larger or risky changes, such as more than 10 records, a status or stage, or anything that sends a message), give them the approve link and stop. Never try to work around it.