salesforce

Classifies Salesforce CRM operations by risk and guides safe execution of record, quote, and automation changes.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/MetaFloor-AI/metafloor-scm-plugin-openai --skill salesforce-metafloor-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: salesforce
Source: https://github.com/MetaFloor-AI/metafloor-scm-plugin-openai/tree/main/skills/platforms/crm/salesforce
Command: npx skills add https://github.com/MetaFloor-AI/metafloor-scm-plugin-openai --skill salesforce-metafloor-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Salesforce writes can silently fire Flows, Apex triggers, and validation rules that email customers, create orders, or lock records, and destructive actions like merges and mass deletes cannot be undone. This Skill gives an AI agent the judgment to classify every Salesforce action as read, reversible write, committing write, or destructive before executing it. ## Core Features & Use Cases - Risk classification of operations: Maps Salesforce operation families (stage changes, lead conversion, order activation, merges, mass updates, OWD changes) to read/write/destructive gates with human-approval rules. - Object and state model guidance: Covers leads, accounts, contacts, opportunities, quotes/CPQ, orders, cases, price books, approval processes, and the sharing model (OWD, role hierarchy, profiles, permission sets, FLS). - Edge states and recovery playbooks: Documents 25 gotchas, edge cases like Person Accounts and multi-currency orgs, and recovery paths such as the 15-day Recycle Bin window and amendment orders. - Use Case: Before converting a lead or setting an opportunity to Closed Won, the agent checks wired automation, confirms the org (sandbox vs production), and pauses for human approval because the action fires committing downstream automation. ## Quick Start Ask the agent to update an opportunity stage in Salesforce and it will first read the record, check for wired automation, and classify the change before acting.

Frequently Asked Questions about salesforce

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely update an opportunity stage in Salesforce?

Read the record and its wired automation first, because a stage change moves the forecast and Closed Won can fire order creation or fulfillment. Treat it as a committing write that needs human approval, then re-read the record after saving to confirm what persisted.

What happens when you convert a lead in Salesforce?

Lead conversion creates an Account, Contact, and optionally an Opportunity, then marks the Lead read-only. It is one-way with no standard un-convert, so recovery means manually deleting the created records and the field mapping is lost.

Why did my Salesforce record update not save?

A validation rule or duplicate rule can silently reject the save, leaving the record unchanged. The record may also be locked by an approval process, lead conversion, or CPQ quote sync, so check the lock source before retrying.

Can deleted Salesforce records be recovered?

Deleted records stay in the Recycle Bin for 15 days and can be undeleted within that window. After the window, or after a Bulk API hardDelete or emptying the bin, recovery requires a backup rather than an undo.

When should a Salesforce change require human approval?

Committing actions like lead conversion, order activation, case closure, CPQ quote sync, and owner changes need approval because they fire automation reaching customers or fulfillment. Destructive actions like merges, mass deletes, and OWD changes need a named approver and a re-read of live state.