Update to Salesforce

{
  "description": "Run Agentforce Sales MCP workflows beyond ordinary record reads. Use when the user asks to create or get account plans, assign a Contact or Lead to Agentforce Lead Nurturing, summarize a call transcript, query calendar events, or find active Agentforce sales agents.",
  "included_files": [],
  "name": "salesforce-automation",
  "skill_md_contents": "---\nname: salesforce-automation\ndescription: Run Agentforce Sales MCP workflows beyond ordinary record reads. Use when the user asks to create or get account plans, assign a Contact or Lead to Agentforce Lead Nurturing, summarize a call transcript, query calendar events, or find active Agentforce sales agents.\nallowed-tools:\n  - get_record_id_by_name\n  - get_record_details\n  - soql_query\n  - query_calendar_events_v2\n  - create_account_plan\n  - get_account_plan_v2\n  - query_agent_type\n  - assign_target_to_sdr\n  - summarize_conversation_transcript\n  - describe_global\n  - describe_sobject\n  - get_user_info_v2\n---\n\n# Salesforce Automation\n\nUse this workflow for Agentforce Sales MCP actions that are more specialized than ordinary record reads. Read `../../references/provider-api-rules.md` before creating account plans, assigning targets, summarizing calls, or relying on calendar context.\n\n## Preconditions\n\n- Use ordinary Salesforce reads first when the task can be completed without a specialized action.\n- Treat `create_account_plan` and `assign_target_to_sdr` as consequential writes. Restate the target and expected change before calling when there is any ambiguity.\n- Do not invent tools or custom Salesforce automation surfaces that are not listed in this skill.\n- Resolve record IDs before calling specialized tools.\n\n## Workflow\n\n1. For account plans, resolve the account and use `get_account_plan_v2` before creating a duplicate plan.\n2. For Agentforce Lead Nurturing assignment, call `query_agent_type`, present available agents, and ask which agent to use before `assign_target_to_sdr`.\n3. For call transcript summaries, query VoiceCall and VideoCall separately when the call id is unknown, then ask the user to choose a specific call before `summarize_conversation_transcript`.\n4. For calendar requests, use `query_calendar_events_v2` with a bounded date or owner scope. Call `get_user_info_v2` first to determine the user's timezone for correct ISO-8601 offset.\n5. Verify mutating results with returned fields, `get_record_details`, `get_account_plan_v2`, or a narrow SOQL read when the response does not prove the outcome.\n\n## Output\n\nWhen `query_calendar_events_v2` fulfills a standalone show or view request in a widget-capable conversation, rely on the rendered UI as the complete response. Do not add commentary, confirmation, summary, analysis, or repeat the rendered events.\n\nFor an explicit calendar summary or analysis request, a composite workflow such as an account brief or pipeline review, or a Codex, non-widget, or background workflow, use the returned event data to produce the requested textual or structured result. Include only relevant evidence rather than repeating the complete event list unless requested.\n\nFor other Agentforce workflows, summarize the target records, response status or payload, and verification performed. Say plainly when a requested action is unavailable on the installed MCP surface.\n"
}