Agent skill · software engineering · jeremylongshore
salesloft-sdk-patterns
Analyze and design a typed Salesloft REST adapter with tenant-bound authentication, endpoint-specific schemas, pagination, errors, and rate metadata. Use when creating or refactoring an integration client. Trigger with "Salesloft SDK patterns", "Salesloft client wrapper", or "typed Salesloft API".
Why this skill is useful
Provides production-ready patterns and error handling for the SalesLoft API that the AI wouldn't reliably generate on its own.
What it needs
Requires axios, node-fetch installed locally. Requires salesloft account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Salesloft Typed REST Adapter Overview This skill builds a narrow client around the endpoints an application actually uses. It avoids invented universal schemas, implicit tenant state, and unbounded recursive retries. Prerequisites A repository with an identified HTTP boundary Endpoint, scope, request-format, and response-format inventory A tenant-to-credential resolver Fixture coverage for success and failure envelopes Tool Discipline Use Read, Glob, and Grep to inspect package versions, call sites, and generated types. Use WebFetch only for official endpoint contracts. Use Write or Edit after the adapter boundary is confirmed. Current Contract Use https://api.salesloft.com/v2 and documented resource paths; do not force .json onto every path. Preserve data, metadata, error, and field-keyed errors as separate typed shapes. Pagination and filters are endpoint-specific; page numbers begin at 1 and deep pages consume more rate cost. Capture x-ratelimit-endpoint-cost and x-ratelimit-remaining-minute from every response that provides them. Use the request content type documented by the endpoint rather than assuming all writes are JSON. Authentication Resolve one Bearer credential from the explicit tenant context for every call. Never store a mutable global token or retry with another tenant's credential. Instructions 1. Inventory exact methods, paths, scopes, query parameters, bodies, and consumed response fields. 2. Define typed success, list metadata, singular error, validation error, and rate-state models. 3. Centralize timeout, Bearer injection, content negotiation, and redacted error capture. 4. Implement an iterative page iterator that stops on metadata.paging.nextpage or an empty page. 5. Retry only safe operations or explicitly idempotent application workflows with a bounded attempt budget. 6. Add contract fixtures before migrating callers behind the adapter. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/salesloft-sdk-patterns--9ede04