Agent skill · marketing growth · jeremylongshore
salesforce-known-pitfalls
Review a Salesforce integration for fixed API versions, unsafe auth, N-plus-one queries, shared-limit blindness, stale metadata, blind retries, event gaps, and missing reconciliation. Use when preparing a release. Trigger with "audit Salesforce pitfalls".
Why this skill is useful
Provides domain-specific knowledge on Salesforce anti-patterns and best practices that the AI wouldn't reliably generate on its own.
What it needs
About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Salesforce Integration Pitfall Audit Overview Find evidence of recurring failure patterns in code and operations, rank their real blast radius, and convert each confirmed issue into a bounded fix and regression test. Prerequisites Repository, architecture, org topology, API and event contracts, deployment history, incidents, and current owners Current Salesforce API EOL, OAuth, limits, metadata, security, Bulk, Composite, CDC or Pub/Sub documentation Representative fixtures, non-production org, policy gates, reconciliation queries, and change process 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 Common Salesforce defects cross application and org boundaries: unsupported versions, legacy auth, inefficient queries, shared capacity, object or field drift, automation side effects, partial writes, event gaps, and permission differences. Their exact behavior must be proven in context. Authentication Audit secret references and authorization boundaries without resolving live secrets. Use the real integration principal only in a protected authorized test lane, never an administrator session as proof. Instructions 1. Inventory hard-coded API versions, login hosts, app types, OAuth flows, secrets, org aliases, direct calls, queries, writes, retries, and event state. 2. Detect N-plus-one and unbounded queries, broad field selection, missing pagination, stale metadata, wrong API mode, and unmeasured automation. 3. Check shared limits, concurrency, hard-quota behavior, timeout classification, partial results, uncertain-write reconciliation, and batch idempotency. 4. Review CRUD and field access, sharing, SOQL construction, logs, exports, support bundles, production data in fixtures, and privileged bypasses. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/salesforce-known-pitfalls