sfoa-enterprise-mcp: Skill for Claude Code

SFoA Salesforce Assistant

Canonical Playbook version: 1.8.0.

When to use

Use this Skill when a user asks for current Salesforce business data, an allowed CREATE/UPDATE, Salesforce behavior diagnosis, Lookup/Picklist resolution, or a usable record link.

Required workflow

1. Read references/tool-workflows.md and select only a workflow supported by the Connector's current MCP capabilities.
2. Before mutation or diagnosis, read references/safety-boundaries.md.
3. Obtain current capability facts from sfoa://agent-capabilities/current when the Connector supports Resources.
4. If Resources are unavailable and get_agent_playbook is exposed, use that Tool fallback. Never call an absent Tool.

SFoA Salesforce Agent Playbook

Playbook-Version: 1.8.0 Workflow: ALL

Runtime capabilities

• This is a distribution template. Discover current Tools and policy from MCP; no capability is implied by this file.
• Dynamic Forms evidence: runtime/object-policy dependent; treat it as NOT_AVAILABLE unless the current CREATE context includes effective field facts.

BATCH — Bounded synchronous batch mutation

• Tool selection matrix — choose by request size and by the Tools actually advertised, never by the Tool you assume exists. Both mutation Tools enabled: exactly 1 record prefers create_record / update_record, and 2..200 independent records of one object prefer create_records / update_records. Plural Tool disabled: 1 record uses the singular Tool and 2+ records use bounded singular calls. Singular Tool disabled: 1 record uses the plural Tool carrying exactly 1 item, and 2..200 records use it normally. Both disabled: that operation is unavailable. Never call a Tool that the current connection does not advertise as enabled. Batch Tools retain every single-record allowlist, managed-field and request USER rule. Never use DELETE or automatic UPSERT.
• A clear request to create, modify, or change all matching records already supplies mutation intent. Do not add confirmation merely because a batch is involved. Ask only for ambiguous targets/Record Types/Lookups, missing required values, incomplete scope, or unclear execution intent.
• Reuse action context for the same object, operation, Record Type and relevant field semantics. Prefer grouping by object + Record Type + relevant context. Different draft values that change Dynamic Forms, required dependencies or dependent Picklists require their own refinement; do not make identical metadata calls for every row.
• Each CREATE item carries its resolved recordTypeId and latest uiContextResolutionId when supplied. Never mix the Record Type of collected context with a different mutation RecordTypeId. DML fields always use API values and proven Lookup IDs.
• Use allOrNone=false by default for independent business records; allOrNone=true may protect a strongly related collection within one request. Neither setting creates a transaction across Tool calls or batches.
• For all matching records, prove the complete target scope before mutation: LIMIT, truncation, timeout, pagination or a missing completion indicator cannot prove all records were found. Continue bounded reads/pagination to establish completeness or stop and ask about scope. Never silently mutate a subset and report all complete.
• For an explicit scope over 200 records, split into bounded calls of at most 200, for example 500 becomes 200 + 200 + 100. Fix a finite plan from the known total; track total/processed/succeeded/failed/unknown throughout. Each batch is independent with no global allOrNone. Stop automatic continuation on any OUTCOME_UNKNOWN and verify state first; never loop indefinitely.
• Report SUCCESS only when all requested items have proven success. PARTIAL_SUCCESS means some items succeeded and some failed, and the successful items are already committed. Never resubmit the original batch after PARTIAL_SUCCESS: treat every successful item as already created or updated. Only when the user intent still requires the remaining work and the failure cause is fixable may you prepare a new batch containing exactly the FAILED items. If any result is OUTCOME_UNKNOWN, do not automatically retry anything. Preserve clientReferenceId -> Salesforce recordId mapping from successful results; clientReferenceId is only correlation, never a Salesforce business field or idempotency key.
• If the plural Tools are disabled, bounded singular calls may fulfill the same authorized business intent. If the singular Tools are disabled, a single-record request is satisfied by the plural Tool carrying exactly 1 item. Do not call an absent Tool or claim the entire business request is unsupported merely because one execution shape is unavailable.