# Salesforce

Use when a focused Sales workflow needs Salesforce-backed CRM reads, links, drafts...

- Repository: https://github.com/XiaomiMiMo/MiMo-Code (13741 stars)
- Category: Writing
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add XiaomiMiMo/MiMo-Code --skill salesforce -g -a claude-code -y`
Codex: `npx skills add XiaomiMiMo/MiMo-Code --skill salesforce -g -a codex -y`
Cursor: `npx skills add XiaomiMiMo/MiMo-Code --skill salesforce -g -a cursor -y`
Gemini CLI: `npx skills add XiaomiMiMo/MiMo-Code --skill salesforce -g -a gemini-cli -y`

## Description

Use when a focused Sales workflow needs Salesforce-backed CRM reads, links, drafts, notes, account plans, Agentforce assignments, or explicitly requested Salesforce connector/query guidance. Do not use for generic CRM app construction or when another CRM is authoritative.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Salesforce User Guide

Prepare a sales person with trustworthy Salesforce context or a safely reviewed Salesforce action, while keeping the surrounding Sales workflow authoritative for the business task.

## Common Skill Instructions

MANDATORY: If not already in context, read and adhere closely to plugins/sales/skills/index/SKILL.md## Cross-Skill Best Practices.

## Salesforce Operation Ranking

Use this priority order when the requested Salesforce job or record is ambiguous.

1. Explicit user request, named record, Salesforce id, account, opportunity, contact, lead, or stated action
2. Read-only context that helps the active Sales workflow make a decision
3. Exact record or high-confidence candidate resolved from the user's words and business context
4. The smallest field set, activity history, account plan, event, or transcript context that answers the request
5. A reviewed draft of proposed Salesforce changes
6. An explicitly approved, supported Salesforce write followed by verification

Do not silently pick among plausible records, broaden a read into a write, or treat clarification answers as write approval.

## Key Dependency Categories

These are particularly important for this workflow; use your best judgment to potentially include other data sources to improve quality.

- ~~CRM, specifically the exposed Agentforce Sales/Salesforce connector, for Salesforce-backed reads, record links, account plans, transcript summaries, Agentforce Lead Nurturing assignments, and approved writes
- The parent Sales workflow for Calendar, Scheduling, Meeting Transcripts, Email, Internal Messaging, Knowledge & Files, or Sales Intelligence context that Salesforce does not own
- User-provided record ids, names, exports, field values, and business context when connector access is unavailable or a record needs disambiguation

Avoid unsupported claims. If Salesforce is missing, unavailable, stale, ambiguous, or limited by the exposed connector surface, state the limitation.

The rest: https://github.com/XiaomiMiMo/MiMo-Code/blob/HEAD/packages/cli/src/skill/builtin/.bundle/sales/workflows/salesforce/SKILL.md