Agent skill · marketing growth · jeremylongshore
salesloft-core-workflow-b
Reconcile Salesloft cadence membership state and engagement counts with an incremental, restartable read workflow. Use when building sales outcome reporting or downstream CRM synchronization. Trigger with "Salesloft cadence analytics", "Salesloft membership sync", or "Salesloft engagement reconciliation".
Why this skill is useful
Provides specific REST API commands and patterns for tracking and analyzing SalesLoft activities that the AI wouldn't reliably generate on its own.
What it needs
Requires axios 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 Cadence Outcome Reconciliation Overview This skill synchronizes cadence membership state and its documented engagement counts without relying on obsolete activity paths. It preserves mutable-record semantics and a restartable cursor. Prerequisites A named team and destination dataset cadences:read plus any endpoint-specific read scope A durable microsecond-precision updatedat cursor A documented merge key and data-retention policy Tool Discipline Use Read, Glob, and Grep to inspect schemas, sync checkpoints, and consumers. Use WebFetch only for current Salesloft endpoint and polling documentation. Use Write or Edit after confirming the destination contract. Current Contract GET /v2/cadencememberships supports updatedat filters, sortby=updatedat, direction, page, and perpage up to 100. A membership is mutable and reused when a person later returns to the same cadence. Current state includes processing, staged, active, scheduled, pending, completed, removed, reassigned, and archived outcomes. Documented counts include views, clicks, replies, calls, sent emails, and bounces. Authentication Use the explicit team credential with the minimum read scopes. Never mix cursors or destination partitions between teams. Instructions 1. Define the destination key, accepted fields, retention window, and team partition. 2. Start from a durable cursor with a deliberate overlap window for equal timestamps. 3. Fetch memberships ordered by updatedat ascending with a bounded page size. 4. Upsert by stable membership ID and treat state and counts as replaceable snapshots. 5. Advance the cursor only after the destination transaction succeeds. 6. Deduplicate overlap records and compare source, processed, and committed counts. 7. Reconcile periodic samples against Salesloft and alert on gaps or backward cursors. Approval Boundaries Keep this workflow read-only in Salesloft. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/salesloft-core-workflow-b