Agent skill · software engineering · jeremylongshore
salesforce-sdk-patterns
Build a version-negotiated Salesforce adapter around the customer-selected CLI or client library with typed boundaries and contract tests. Use when standardizing application access. Trigger with "design a Salesforce adapter".
Why this skill is useful
Provides specific TypeScript and Python patterns for Salesforce SDK usage that the AI wouldn't reliably generate on its own.
What it needs
Requires jsforce, simple-salesforce installed locally. 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 Typed Adapter and Client-Library Boundary Overview Contain library churn and org-specific schema behind a small adapter whose types, API version, permissions, retries, and evidence are explicit. Prerequisites Repository, runtime, supported environments, and selected Salesforce library or CLI Current dependency lock, org schema evidence, API support policy, and error samples 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 publishes versioned API contracts, while third-party client libraries have independent release and support policies. Object and field shapes remain customer-specific, so generated or handwritten types must be tied to dated metadata evidence. Authentication Accept an authenticated client or secret reference from the approved authorization layer. The adapter must not invent a password fallback, persist tokens, broaden scopes, or choose a production org implicitly. Instructions 1. Inventory direct Salesforce calls, library versions, API versions, objects, fields, mutations, retries, and error handling. 2. Define a narrow adapter interface for identity, metadata discovery, reads, bounded writes, async jobs, and limits. 3. Bind types to dated object metadata or a governed schema snapshot and label nullable, encrypted, formula, and inaccessible fields. 4. Centralize pagination, request IDs, timeouts, idempotency keys or external IDs, error normalization, and redaction. 5. Add contract fixtures for success, partial failure, token expiry, permission denial, schema drift, limits, and timeouts. 6. Test the adapter without a live org, then run approved read-only and sandbox mutation probes. 7. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/salesforce-sdk-patterns