Agent skill · marketing growth · jeremylongshore
salesloft-core-workflow-a
Analyze and resolve a Salesloft person, then enroll that person in an approved cadence with duplicate, visibility, and consent safeguards. Use when automating controlled prospect enrollment. Trigger with "Salesloft cadence enrollment", "add person to Salesloft cadence", or "Salesloft person workflow".
Why this skill is useful
Adds executable scripts for managing SalesLoft people and cadences via REST API that are not publicly documented.
What it needs
Requires npm 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 Controlled Cadence Enrollment Overview This skill turns person resolution and cadence enrollment into one auditable workflow. It prevents demo writes, duplicate people, accidental owner changes, and enrollment into an unapproved cadence. Prerequisites Approved Salesloft team, cadence ID, acting user, and business purpose people:read, required person-write scope when creation is approved, and cadences:read or write scope as documented Consent and contact-restriction policy for the target person A durable application correlation key and rollback owner Tool Discipline Use Read, Glob, and Grep to find person resolution, cadence, and CRM ownership code. Use WebFetch only for current official endpoint documentation. Use Write or Edit after the mutation boundary is approved. Current Contract POST /v2/people requires either an email address or phone plus last name as a unique lookup basis. A person's donotcontact and contactrestrictions affect permitted communication and cadence steps. POST /v2/cadencememberships requires visible personid and cadenceid values. Acting for a teammate is constrained by team-cadence ownership or Personal Cadence Admin permission. Cadence membership records are mutable and can represent later re-enrollment, not immutable event history. Authentication Use a tenant-bound Bearer credential with only the scopes needed for the chosen read or write steps. Prove team and acting-user identity before mutation. Instructions 1. Confirm team, person lookup, approved cadence, acting user, consent state, and owned fields. 2. Search using only documented person filters and handle zero, one, or multiple candidates explicitly. 3. If no person exists, present the exact create payload and endpoint content type for approval. 4. Re-read the person and stop for donotcontact, incompatible restrictions, or identity ambiguity. 5. Inspect current and historical cadence membership before adding a new membership. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/salesloft-core-workflow-a