Update to Nimble CRM

{
  "description": "Create or update individual deals in Nimble, including discovering writable field IDs, pipelines, and stages. Use for changes to deal values or relationships, not deal field or pipeline structure.",
  "included_files": [],
  "name": "manage-deals-in-nimble",
  "skill_md_contents": "---\nname: manage-deals-in-nimble\ndescription: Create or update individual deals in Nimble, including discovering writable field IDs, pipelines, and stages. Use for changes to deal values or relationships, not deal field or pipeline structure.\n---\n\n# Manage deals in Nimble\n\nUse the Nimble MCP connector as the source of truth.\n\n1. Use `search_deals` to find an existing deal and `get_deal` to inspect its full card and `is_editable` before an update.\n   Use `get_deal_search_field_metadata` only to build search queries.\n2. Call `get_deal_field_metadata` for field IDs, types, and value `read_only` flags, and `list_deal_pipelines` for current\n   pipeline and stage IDs. Use fields with `read_only: false`; `available_actions` describes structural edits. Prefer\n   field IDs because custom field names can repeat across pipelines. Do not guess IDs.\n3. For `create_deal`, provide `fields_values` with a name entry and either a pipeline ID or a non-final stage ID.\n   Values are lists of `{ \"value\": \"text\" }` objects; send numbers and dates as strings in their field's expected\n   format. If the selected stage has no default probability, provide a probability field value.\n4. For `update_deal`, send only properties to change. Inside `fields_values`, an empty list clears that field; other\n   fields stay unchanged. `related_contacts`, `related_external_contacts`, and `tags` replace their complete lists,\n   so use `[]` only when clearing them. A stage change must stay within the current pipeline and cannot mark a deal won\n   or lost. Do not use `null` for `fields_values` or `stage_id`.\n5. Both write tools return the full saved deal. Check the returned `deal_id`, changed values, and `is_editable` before\n   reporting success. If a create response is ambiguous after a transport failure, search for its exact name and\n   pipeline, then inspect any match with `get_deal` before retrying. If the result remains ambiguous, ask the user\n   before another create to avoid a duplicate.\n\nThe REST API enforces visibility, edit permission, and account-specific field validation. Report permission or validation\nerrors; do not switch to another identity or write route.\n"
}