Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/salesloft-install-auth

@820dfc8
Run it yourself

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".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/salesloft-install-auth

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈73 tokens for metadata: the name and description. ≈934 when used: this file. ≈715 more on demand in 1 file.

Description uses 3.6% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈292 characters, or 3.6%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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. For authorization code, replace the access and refresh token together in one durable transaction.
  7. Prove access with a bounded read such as GET /v2/me; never print the response body in CI.

Approval Boundaries

Do not broaden scopes, enable client credentials, create or revoke credentials, or change production callback URIs without the integration owner and Salesloft admin. Never expose a token in a command, URL, patch, log, or example.

Output

Return the integration type, chosen flow, scope matrix, secret references, rotation behavior, read-only proof, and unresolved administrator actions.

Error Handling

Condition Response
invalid_grant Recheck redirect URI and one-time code, then restart authorization if needed.
401 Verify access-token injection and expiry; do not submit a refresh token to the API.
403 Compare granted scopes and acting-user permissions with the endpoint contract.
Concurrent refresh Serialize refresh and atomically persist the newly rotated token pair.

Examples

The example below shows the minimum redacted evidence expected from a successful invocation of this operator workflow.

integration=partner; flow=authorization-code; proof=GET /v2/me; writes=forbidden

Resources

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill provides secure and standard instructions for setting up SalesLoft API authentication. It follows best practices for secret management and uses official API endpoints and well-known dependencies.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 20 hours ago.

Activeupdated 2 months ago
What it can do
Reads files Network Edits files
Modelinherit
argument-hint
[repository-path] [integration-type]
version
1.6.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 6 allowed tools
ReadGlobGrepWebFetchWriteEdit
Other metadata
tags
[
  "saas",
  "salesloft",
  "authentication"
]
model
inherit
effort
medium
compatibility
Designed for Claude Code

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/salesloft-install-auth