Update to Nimble CRM

{
  "description": "Find, filter, inspect, or compare deals in Nimble. Use for requests about deal names, owners, pipelines, stages, statuses, dates, amounts, or custom deal fields. This skill reads deals; it does not create or update them.",
  "included_files": [],
  "name": "search-deals-in-nimble",
  "skill_md_contents": "---\nname: search-deals-in-nimble\ndescription: Find, filter, inspect, or compare deals in Nimble. Use for requests about deal names, owners, pipelines, stages, statuses, dates, amounts, or custom deal fields. This skill reads deals; it does not create or update them.\n---\n\n# Search deals in Nimble\n\nUse the Nimble MCP connector as the source of truth.\n\n## Build the search\n\n- Call `get_deal_search_field_metadata` when the exact field name, supported operator, custom field alias, or\n  account-specific value ID is uncertain. Use the returned search contract instead of guessing from UI column names.\n- Use `possible_values` to translate owner, pipeline, stage, status, and other finite labels into their current account\n  IDs. Never invent an ID.\n- For deal names, use `contain` for complete words, `starts_with` for an unfinished last term, and `is` only when the user\n  requests an exact name. These operators do not provide typo tolerance or arbitrary substring matching.\n- Put all requested constraints in one `search_deals` query. Do not discard non-name filters when refining a name search.\n- Deals have no last-activity field. For stalled or inactive deals, filter or sort by `entered_current_stage_stage`\n  and tell the user the result reflects time in the current stage, not the latest activity. Compact results report\n  that date as `entered_stage_at`, so no full response is needed to explain it. Won and lost deals stay in their final\n  stage too, so add `{\"deal_status\":{\"is\":\"open\"}}` unless the user asks about closed deals.\n- When the user asks for an unfiltered deal list, call `search_deals` without a query instead of constructing a wildcard.\n\n## Inspect the results\n\n- Start with the default compact response. Use `get_deal` to inspect the full card for a selected deal; request the\n  full search response only when complete data are needed for several matches.\n- Keep the same query and sort while paging. Do not present one page as the complete result set when more pages exist.\n- Ground comparisons and summaries in returned deal fields, owners, pipelines, stages, and related contacts. Clearly\n  distinguish missing values from values that were not included in the selected response format.\n- If the request remains ambiguous after metadata discovery, show the relevant choices or ask which field, pipeline,\n  stage, or deal the user means.\n\nDo not imply that a deal was created or changed. Use `manage-deals-in-nimble` for requested writes.\n"
}