Update to Salesforce

{
  "description": "Build Salesforce Agentforce Sales account intelligence, meeting prep, opportunity deep dives, contact maps, activity context, account plan context, and recent activity briefs. Use when the user asks for an account or opportunity summary, customer meeting prep, buying committee context, account risks, next-best actions, or a consolidated brief from Salesforce account, opportunity, contact, task, event, account plan, and call records.",
  "included_files": [],
  "name": "salesforce-account-brief",
  "skill_md_contents": "---\nname: salesforce-account-brief\ndescription: Build Salesforce Agentforce Sales account intelligence, meeting prep, opportunity deep dives, contact maps, activity context, account plan context, and recent activity briefs. Use when the user asks for an account or opportunity summary, customer meeting prep, buying committee context, account risks, next-best actions, or a consolidated brief from Salesforce account, opportunity, contact, task, event, account plan, and call records.\nallowed-tools:\n  - get_record_id_by_name\n  - get_activity_history_v2\n  - get_record_details\n  - soql_query\n  - query_calendar_events_v2\n  - get_account_plan_v2\n  - summarize_conversation_transcript\n  - get_user_info_v2\n  - describe_global\n  - describe_sobject\n---\n\n# Salesforce Account Brief\n\nUse this workflow for read-only Agentforce Sales briefs that combine account, opportunity, contact, task, event, activity history, account plan, and call context. Read `../../references/provider-api-rules.md` when relationship names, record-type-sensitive fields, UI/display context, or call summaries matter.\n\n## Workflow\n\n1. Resolve the target account or opportunity first. Prefer exact Salesforce IDs or URLs; otherwise use `get_record_id_by_name` or narrow `soql_query` calls to find candidates.\n2. Confirm the needed object and field API names with `describe_sobject` when the fields are non-obvious or custom.\n3. Read only the fields needed for the brief. Include `Id`, names, owners, stage/status, dates, amounts, priority, and last activity fields when relevant.\n4. Pull adjacent context selectively:\n   - account profile and owner fields;\n   - open opportunities and current stage/amount/close date;\n   - contacts or buying committee records;\n   - recent tasks, calendar events, or activity history;\n   - account plan details when the user asks for plan, strategy, strengths, gaps, or relationship context.\n5. Use `get_record_details` when presentation-ready layout or optional fields are useful. Always include both `Compact` and `Full` layout types unless the user asks for a narrower read.\n6. Use `summarize_conversation_transcript` only after resolving a specific VoiceCall or VideoCall id. If needed, query VoiceCall and VideoCall separately and ask which call to summarize.\n7. For relationship-heavy briefs, confirm relationship names with metadata before using nested SOQL. Do not guess child relationship names.\n8. If fields are missing from a UI/layout-oriented response, retry with explicit fields before concluding Salesforce does not expose them.\n\n## Output\n\nReturn a compact business-facing brief with:\n\n- resolved Salesforce record links;\n- current state and important risks;\n- recent activity or evidence used;\n- gaps or fields that should be verified live;\n- suggested next actions, clearly separated from facts.\n\nDo not write back to Salesforce from this skill. Route explicit changes through `salesforce-writeback`.\n"
}