How to use the Salesforce Sales Workflow agent skill

What is an agent skill, and what does this one do?

An agent skill is a folder containing a SKILL.md file with instructions that an AI agent reads when a request matches the skill's description. This one comes from the MiMo Sales workflow and is named salesforce. Its description says it should be used when a focused sales task needs Salesforce-backed CRM reads, record links, drafts, notes, account plans, Agentforce assignments, or Salesforce connector and query guidance.

• Look up accounts, contacts, opportunities and activity history in Salesforce
• Build clickable record links when a trusted URL is available
• Draft account plans and summarize call transcripts
• Show a reviewed field-level draft before any change
• Write to Salesforce only after explicit approval, then verify the result

Install the Salesforce skill from the ZIP download

Download the ZIP for the skill from the item page, then unzip it. Put the resulting salesforce folder in one of two places depending on how you want to use it. A personal install in ~/.claude/skills/ is available to you across projects. A project install in a project's .claude/skills/ folder applies only to that project.

If you use the Claude apps instead of files on disk, you can upload the skill under Settings → Capabilities → Skills.

• Personal: ~/.claude/skills/salesforce/
• Project: <your-project>/.claude/skills/salesforce/
• Claude apps: Settings → Capabilities → Skills, then upload the skill

Know what you need before you start

The skill does not connect to Salesforce by itself. It relies on a Salesforce connector exposed through the Agentforce Sales surface. It also expects the parent MiMo Sales workflow and its index skill instructions, which live at plugins/sales/skills/index/SKILL.md, because the salesforce skill reads the cross-skill best practices from that file first.

If Salesforce is not reachable, the agent is supposed to say so and label its answer as not Salesforce-backed, or ask you to supply record ids, names or field values yourself.

• A Salesforce connector exposed through the Agentforce Sales surface
• The parent MiMo Sales workflow and plugins/sales/skills/index/SKILL.md

Ask for work in plain language

You do not need to name the skill. Describe the sales task and include the account, opportunity or contact name if you have it. The skill is built to resolve names to records, so an exact name or Salesforce id helps most. Say whether you want information only, a draft, or a change written to Salesforce, because the skill treats these differently.

When a name matches more than one record, the agent is designed to show you candidates and ask you to choose. It will not quietly pick one and continue.

• Tell it the task: summary, draft, or approved write
• Give the most exact name or id you have
• Mention the time window or activity type if history matters
• Answer the clarification question when it asks you to choose a record

Example requests and what to expect

Requests that fit the skill look like the examples below. The agent will first run discovery reads, then return labelled results with record links where available. For any proposed change, you should see a draft listing each field, its assumptions and any gaps, and the approval still needed before anything is written.

Approving a draft is a separate step. Replying with a clarification answer is not treated as write approval, so say clearly when you want the change saved.

• "Prepare a briefing on the Acme Corp account with open opportunities and recent activity."
• "Summarize the last VoiceCall for the Northwind renewal and list follow-up tasks."
• "Draft an account plan for Contoso based on its opportunities and notes."
• "Update the close date on the Fabrikam opportunity to next quarter. Show me the draft first."

Safety: what the skill will and will not do

The skill runs no scripts, according to its listing, but it does use the network because it talks to Salesforce through the connector. Its write rules are strict: it does not delete records, does not upsert by external id, does not call arbitrary automation, and does not write without explicit approval. It sends only changed fields on an update and checks the response, using a narrow read when the response alone does not prove the outcome.

It also does not support some surfaces. The instructions say to state the missing surface rather than attempt unsupported work, including SOSL, global text search, Bulk API, Composite API, Data 360, Tableau Analytics, Flow invocation and high-volume writes.

• Runs scripts: no
• Uses network: yes, to reach Salesforce through the connector
• No deletes, no upsert by external id, no writes without explicit approval
• Large data exports, analytics and high-volume record changes are out of scope

Tips for better results

The skill works best when you give it narrow, specific requests. Broad requests such as pulling every opportunity in the company are outside its design, and it will ask you to narrow the object, field or identifier. Give it the record id when you have one, and check any draft fields against your own records before approving.

• Start with one account or opportunity rather than a whole territory
• Supply Salesforce ids when you know them to avoid ambiguity
• Review drafts line by line; the source gaps section tells you what the agent could not confirm
• If validation fails, the agent will show the exact Salesforce message and ask for the missing value