{"id":30467,"plugin_id":"plugin_asdk_app_697d413990c88191a2bf4799604f8f6c","kind":"skill","collection_source":"skill_api","comparison_source":"skill_api","observed_at":"2026-10-09T06:04:06.437Z","digest":"5ab6b5c8e5de947379023c16ac6961b8113aafc14a9b85b24afb2a80c2cbfc3c","against":29333,"payload":{"description":"Review Salesforce Agentforce Sales pipeline, forecast, stale opportunities, hygiene gaps, close-date risk, stage movement, owner rollups, segment rollups, and quarter summaries. Use when the user asks for open pipeline analysis, commit/upside risk review, deals needing manager review, missing next steps, stale activity, calendar context, or opportunities that changed stage, amount, close date, or forecast category.","included_files":[],"name":"salesforce-pipeline-review","skill_md_contents":"---\nname: salesforce-pipeline-review\ndescription: Review Salesforce Agentforce Sales pipeline, forecast, stale opportunities, hygiene gaps, close-date risk, stage movement, owner rollups, segment rollups, and quarter summaries. Use when the user asks for open pipeline analysis, commit/upside risk review, deals needing manager review, missing next steps, stale activity, calendar context, or opportunities that changed stage, amount, close date, or forecast category.\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_user_info_v2\n  - describe_global\n  - describe_sobject\n---\n\n# Salesforce Pipeline Review\n\nUse this workflow for read-only opportunity and forecast analysis. Read `../../references/provider-api-rules.md` when using custom fields, relationship fields, UI reads, or high-volume result sets.\n\n## Workflow\n\n1. Resolve the review scope: quarter or date range, owners, segments, accounts, opportunity type, and forecast categories. For \"my\" or \"me\", use `get_user_info_v2`.\n2. Inspect `Opportunity` metadata before using custom fields such as segment, forecast, next step, product, or stale-activity signals.\n3. Query in narrow passes:\n   - bounded ordinary opportunity rows with `Id`, stage, owner, amount, close\n     date, forecast category, and other fields needed for local summaries;\n   - detail rows for the largest, riskiest, or stale opportunities;\n   - activity, task, calendar, or account plan context only for records that need explanation.\n     Do not use aggregate or grouped SOQL such as `COUNT()` or `GROUP BY`; this connector expects clickable record rows and aggregate rows can fail output validation.\n4. Flag hygiene gaps such as missing next steps, past close dates, no recent activity, stage/amount/close-date changes, and obvious owner or account mismatches.\n5. Use `get_activity_history_v2` for Account, Contact, Lead, or Opportunity activity summaries when recency explains pipeline risk.\n6. If the requested review would require a very large export or bulk processing, state that Bulk API and query continuation are not exposed by this MCP app and narrow to a synchronous slice such as owner, date window, stage, or top-risk records.\n\n## Output\n\nLead with the review scope and run timestamp. Then return a concise table or grouped list of opportunities with Salesforce links, owner, stage, amount, close date, risk signal, and recommended action.\n\nKeep recommendations evidence-backed. Do not change forecast category, stage, amount, or close date from this skill; route explicit updates through `salesforce-writeback`.\n"},"changes":[{"path":"/skill_md_contents","type":"changed","before":"---\nname: salesforce-pipeline-review\ndescription: Review Salesforce Agentforce Sales pipeline, forecast, stale opportunities, hygiene gaps, close-date risk, stage movement, owner rollups, segment rollups, and quarter summaries. Use when the user asks for open pipeline analysis, commit/upside risk review, deals needing manager review, missing next steps, stale activity, calendar context, or opportunities that changed stage, amount, close date, or forecast category.\nallowed-tools:\n  - get_record_id_by_name\n  - get_activity_history_v2\n  - get_record_v2\n  - get_records_v2\n  - soql_query\n  - query_calendar_events_v2\n  - get_user_info_v2\n  - describe_global\n  - describe_sobject\n---\n\n# Salesforce Pipeline Review\n\nUse this workflow for read-only opportunity and forecast analysis. Read `../../references/provider-api-rules.md` when using custom fields, relationship fields, UI reads, or high-volume result sets.\n\n## Workflow\n\n1. Resolve the review scope: quarter or date range, owners, segments, accounts, opportunity type, and forecast categories. For \"my\" or \"me\", use `get_user_info_v2`.\n2. Inspect `Opportunity` metadata before using custom fields such as segment, forecast, next step, product, or stale-activity signals.\n3. Query in narrow passes:\n   - For an interactive set of opportunities, use `get_records_v2` (`inputs: [{objectApiName: \"Opportunity\", fieldNames, filterCriteria?, sortBy?, recordLimit?}]`) after confirming filterable/sortable fields with `describe_sobject`. Do not use it to retrieve one named deal.\n   - For one deal's detail view, resolve its Id and use `get_record_v2` (`inputs: [{recordId, objectApiName: \"Opportunity\", fieldNames}]`). Either tool's rendered widget supplies the record or table presentation; do not repeat its rows in prose.\n   - Use `soql_query` for bounded rows that feed local rollups, comparisons, or hygiene checks the table view does not compute. Do not use aggregate or grouped SOQL such as `COUNT()` or `GROUP BY`; this connector expects clickable record rows and aggregate rows can fail output validation.\n   - Pull activity, task, calendar, or account plan context only for records that need explanation.\n4. Flag hygiene gaps such as missing next steps, past close dates, no recent activity, stage/amount/close-date changes, and obvious owner or account mismatches.\n5. Use `get_activity_history_v2` for Account, Contact, Lead, or Opportunity activity summaries when recency explains pipeline risk.\n6. If the requested review would require a very large export or bulk processing, state that Bulk API and query continuation are not exposed by this MCP app and narrow to a synchronous slice such as owner, date window, stage, or top-risk records.\n\n## Output\n\nLead with the review scope and run timestamp. Then return a concise table or grouped list of opportunities with Salesforce links, owner, stage, amount, close date, risk signal, and recommended action.\n\nKeep recommendations evidence-backed. Do not change forecast category, stage, amount, or close date from this skill; route explicit updates through `salesforce-writeback`.\n","after":"---\nname: salesforce-pipeline-review\ndescription: Review Salesforce Agentforce Sales pipeline, forecast, stale opportunities, hygiene gaps, close-date risk, stage movement, owner rollups, segment rollups, and quarter summaries. Use when the user asks for open pipeline analysis, commit/upside risk review, deals needing manager review, missing next steps, stale activity, calendar context, or opportunities that changed stage, amount, close date, or forecast category.\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_user_info_v2\n  - describe_global\n  - describe_sobject\n---\n\n# Salesforce Pipeline Review\n\nUse this workflow for read-only opportunity and forecast analysis. Read `../../references/provider-api-rules.md` when using custom fields, relationship fields, UI reads, or high-volume result sets.\n\n## Workflow\n\n1. Resolve the review scope: quarter or date range, owners, segments, accounts, opportunity type, and forecast categories. For \"my\" or \"me\", use `get_user_info_v2`.\n2. Inspect `Opportunity` metadata before using custom fields such as segment, forecast, next step, product, or stale-activity signals.\n3. Query in narrow passes:\n   - bounded ordinary opportunity rows with `Id`, stage, owner, amount, close\n     date, forecast category, and other fields needed for local summaries;\n   - detail rows for the largest, riskiest, or stale opportunities;\n   - activity, task, calendar, or account plan context only for records that need explanation.\n     Do not use aggregate or grouped SOQL such as `COUNT()` or `GROUP BY`; this connector expects clickable record rows and aggregate rows can fail output validation.\n4. Flag hygiene gaps such as missing next steps, past close dates, no recent activity, stage/amount/close-date changes, and obvious owner or account mismatches.\n5. Use `get_activity_history_v2` for Account, Contact, Lead, or Opportunity activity summaries when recency explains pipeline risk.\n6. If the requested review would require a very large export or bulk processing, state that Bulk API and query continuation are not exposed by this MCP app and narrow to a synchronous slice such as owner, date window, stage, or top-risk records.\n\n## Output\n\nLead with the review scope and run timestamp. Then return a concise table or grouped list of opportunities with Salesforce links, owner, stage, amount, close date, risk signal, and recommended action.\n\nKeep recommendations evidence-backed. Do not change forecast category, stage, amount, or close date from this skill; route explicit updates through `salesforce-writeback`.\n"}],"summary":"Fields changed: 1. /skill_md_contents.","summary_kind":"deterministic","summary_metadata":{}}