apex-execute

Execute Anonymous Apex

Execute Anonymous Apex code against a connected Salesforce org. This skill is user-invoked only — Claude constructs the Apex code based on what the user wants to accomplish, then executes it via the Salesforce CLI.

Prerequisites

You must be authenticated to a Salesforce org before executing Apex. If not authenticated, run the authentication script first.

Authentication

If the user is not authenticated or gets an auth error, run the authentication script:

node ${CLAUDE_PLUGIN_ROOT}/scripts/sf-auth.js --status

To authenticate interactively (opens browser):

node ${CLAUDE_PLUGIN_ROOT}/scripts/sf-auth.js --alias <alias>

To authenticate to a sandbox:

node ${CLAUDE_PLUGIN_ROOT}/scripts/sf-auth.js --alias <alias> --instance-url https://test.salesforce.com

CRITICAL: Safety Rules for DML Operations

Before executing ANY generated Apex code, you MUST analyze it for data-modifying operations.

DML Detection

Scan the generated code for these keywords (case-insensitive):

DML Statements: insert, update, delete, upsert, undelete, merge Database Methods: Database.insert, Database.update, Database.delete, Database.upsert, Database.undelete, Database.merge, Database.emptyRecycleBin, Database.convertLead Other Mutating Operations: System.enqueueJob, System.schedule, System.scheduleBatch, EventBus.publish, Messaging.sendEmail

If DML is Detected

1. WARN the user that the code will modify data
2. SHOW the complete Apex code that will be executed
3. DESCRIBE exactly what will happen (e.g., "This will update the Rating field to 'Cold' on up to 10 Account records where Rating is currently null")
4. ASK for explicit confirmation before executing
5. Only proceed if the user confirms

If Code is Read-Only

If the code only contains queries ([SELECT ...]), System.debug(), Schema.describe*, Limits.*, or other non-mutating operations — execute without extra confirmation.