Agent skill · data analytics · jeremylongshore
salesforce-common-errors
Analyze Salesforce authorization, permission, schema, validation, locking, limit, async-job, and event-delivery failures from evidence. Use when triaging an integration. Trigger with "diagnose a Salesforce error".
Why this skill is useful
Provides specific solutions and code snippets for diagnosing and fixing common Salesforce API errors that the AI wouldn't reliably generate on its own.
What it needs
Requires salesforce account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Salesforce Integration Error Triage Overview Classify the failed layer, preserve request context, and test one evidence-backed hypothesis before proposing a bounded, reversible correction. Prerequisites Timestamp, environment, principal, operation, request or job ID, and redacted response Expected API version, object and field contract, permissions, limits, automation, and recent changes Incident, application, Salesforce platform, security, and data owners Tool Discipline Use Read, Glob, and Grep to inspect approved repository and evidence files, WebFetch to re-check current first-party Salesforce documentation, and Write or Edit only for secretless plans, fixtures, configuration, and redacted receipts. Current Contract Salesforce exposes documented HTTP and API errors, but the same symptom can originate from OAuth, permissions, sharing, schema, validation, automation, locks, limits, asynchronous processing, or event state. Diagnose the returned evidence in org context. Authentication Use read-only diagnostic access with the approved principal or a separately authorized support principal. Do not collect tokens, session IDs, passwords, private keys, raw personal data, or broad debug logs. Instructions 1. Freeze the first failure timestamp, environment, release, principal, API, request or job ID, payload shape, and retry history. 2. Confirm org status, identity, API support, resource entitlement, and whether other integrations are affected. 3. Classify the layer: transport, OAuth, scope, CRUD or field access, sharing, schema, validation, automation, locking, limit, async job, or event. 4. Correlate the minimum Salesforce response, application trace, limits snapshot, metadata, job result, and recent change evidence. 5. Reproduce with a synthetic or read-only request in the lowest-risk authorized org. 6. Propose one hypothesis-specific correction and define success, stop, rollback, and no-blind-retry rules. 7. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/salesforce-common-errors