Agent skill · software engineering · jeremylongshore
salesloft-install-auth
Select and implement the correct Salesloft authentication flow with least-privilege scopes and safe token rotation. Use when onboarding a customer, partner, or private server integration. Trigger with "Salesloft auth", "Salesloft OAuth", or "Salesloft API key setup".
Why this skill is useful
Provides specific implementation details for integrating with the SalesLoft API using OAuth 2.0 and API key authentication that the AI wouldn't reliably generate on its own.
What it needs
Requires node, python 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 Authentication Decision Overview This skill chooses an authentication boundary before code is written. It distinguishes partner authorization, customer API keys, and admin-enabled private client credentials instead of treating them as interchangeable. Prerequisites A named repository, Salesloft team, and integration owner The integration type: partner, customer-owned, or private backend Approved callback URIs and minimum endpoint scopes A secret store that supports atomic token replacement Tool Discipline Use Read, Glob, and Grep to inspect existing auth code, environment schemas, and secret names. Use WebFetch only for current official Salesloft documentation. Use Write or Edit only after confirming the repository and auth design. Current Contract API requests use Authorization: Bearer <credential> against https://api.salesloft.com/v2. Partners use OAuth; Salesloft does not approve partner applications that rely on API keys. Customer API keys act as the issuing user and must remain server-side. Client credentials are admin-enabled, private-use only, cannot be allowlisted, inherit the creating admin's permissions, expire after 7,200 seconds, and have no refresh token. Authorization-code refresh returns a new refresh token and revokes the old one, so replacement must be atomic. Authentication Use authorization code for user-authorized partner applications, client credentials only for an approved private server process, or a scoped API key for a customer-owned integration. Request only scopes required by the current endpoint reference. Instructions 1. Inventory every Salesloft endpoint, caller, team boundary, and required scope. 2. Select one supported flow and document why it fits the integration type. 3. Register exact callback URIs or private-app settings in Salesloft Account. 4. Store client secrets, API keys, access tokens, and refresh tokens outside source and logs. 5. Implement Bearer injection plus expiry-aware refresh or reacquisition. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/salesloft-install-auth