Agent skill · data analytics · jeremylongshore
salesloft-common-errors
Classify Salesloft API failures from status, documented error envelopes, auth context, visibility, and rate metadata without exposing customer data. Use when an integration returns 401, 403, 404, 422, 429, or 5xx. Trigger with "Salesloft error", "Salesloft request failed", or "debug Salesloft API".
Why this skill is useful
Provides specific troubleshooting steps and code snippets for handling common SalesLoft API errors that the AI wouldn't reliably generate on its own.
What it needs
Requires curl, jq 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 Error Triage Overview This skill identifies the failing contract before changing code, scopes, or credentials. It retains structured error meaning while excluding Bearer values and sales-record payloads. Prerequisites Method, path template, status, timestamp, and team alias Redacted request shape and response content type Auth flow, granted scopes, and acting-user role Rate headers and attempt count when present Tool Discipline Use Read, Glob, and Grep to trace request construction and response handling. Use WebFetch only for the exact official Salesloft contract. Use Write or Edit after the failure class is supported by evidence. Current Contract Success data is under data; list metadata is under metadata. Salesloft documents a singular error for 403 and 404 responses. A 422 response uses a field-keyed errors object and can report multiple validation failures. A 429 should be evaluated with x-ratelimit-endpoint-cost and x-ratelimit-remaining-minute plus any retry guidance actually returned. Authentication Record only auth type, expiry state, scope names, and acting-user identity. Never capture an access token, refresh token, client secret, API key, or authorization code. Instructions 1. Reproduce once with secrets and record values redacted before persistence. 2. Confirm base URL, method, path, content type, query encoding, and timeout. 3. Classify authentication, permission/visibility, missing resource, validation, rate, transport, or provider failure. 4. Compare the exact endpoint's required scope and allowed parameters with the request. 5. Apply the smallest correction and rerun a read-only or fixture proof first. 6. For writes, require payload approval and read-after-write verification. Approval Boundaries Do not rotate credentials, broaden scopes, change production data, or retry an uncertain write merely to test a theory. Escalate when the failure cannot be reproduced safely. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/salesloft-common-errors