Salesloft cadences skill

Builds and optimizes Salesloft cadences: Rhythm, Conversations, multi-channel orchestration, and analytics.

by LeadMagic·MIT license·★ 62 Stars on the repo·GitHub ↗

Use now

Inside this skill

SKILL.md · the author's own words
# Salesloft Cadences

## Overview
Salesloft is the market leader in sales engagement. Cadences here manage Rhythm
(multi-channel cadences), Conversations (reply management), and Deals (pipeline
integration). This skill covers setup, optimization, and team workflows.

## Authoritative Foundations
- **Salesloft Help Center — Cadences and Rhythm** — Configure cadence steps and let Rhythm prioritize tasks from buyer signals so reps work…
- **Google and Yahoo — Bulk sender requirements (2024)** — Authenticate with SPF, DKIM, and DMARC, keep spam complaints below 0.3%, and res…
- **The Bridge Group — SDR metrics research** — Benchmark activity and conversion per rep against published SDR data before judging cadence…

## When to Use
- "Set up Salesloft cadences"
- "Build Salesloft Rhythm"
- "Salesloft optimization"

Word-for-word excerpt, not a result. Read the full SKILL.md ↓

Files of Salesloft cadences

LeadMagic/main1 file shown
SKILL.md
Show the full text147 lines

Salesloft Cadences

Overview

Salesloft is the market leader in sales engagement. Cadences here manage Rhythm (multi-channel cadences), Conversations (reply management), and Deals (pipeline integration). This skill covers setup, optimization, and team workflows.

Authoritative Foundations

  • Salesloft Help Center — Cadences and Rhythm — Configure cadence steps and let Rhythm prioritize tasks from buyer signals so reps work the highest-value action first.
  • Google and Yahoo — Bulk sender requirements (2024) — Authenticate with SPF, DKIM, and DMARC, keep spam complaints below 0.3%, and respect per-mailbox volume.
  • The Bridge Group — SDR metrics research — Benchmark activity and conversion per rep against published SDR data before judging cadence performance.

When to Use

  • "Set up Salesloft cadences"
  • "Build Salesloft Rhythm"
  • "Salesloft optimization"
  • "Salesloft team setup"

Step-by-Step Process

Phase 1: Cadence Architecture

Design by motion type:

  • Prospecting Cadence: 6-8 touches over 14 days, email + call + LinkedIn
  • Inbound Cadence: 4 touches over 7 days, fast follow-up (speed-to-lead)
  • Re-engagement Cadence: 3 touches over 10 days, "still relevant?" angle
  • Event Follow-up Cadence: 2 touches over 5 days, reference the event
  • AE Cadence: 3 touches over 7 days, discovery-focused, less volume
Phase 2: Step Types
  • Email step: Template with merge fields, plain text, from individual sender
  • Call step: Auto-logged, call script + talk track linked, voicemail drop
  • Social step: LinkedIn view, connection, or DM (manual task with template)
  • Custom step: Slack message, direct mail, gift send
  • Wait step: 2-5 business days between touches, skip weekends
Phase 3: Team Configuration
  • Persona-based cadences: Different cadences for C-suite vs Director vs Manager
  • Industry variants: Different opener templates by industry
  • Rep assignment rules: Round-robin, territory-based, or account-owner
  • Manager approval gates: Require approval before high-touch sequences
Phase 4: Conversation Intelligence
  • Auto-categorize replies: positive, negative, OOO, referral, unsubscribe
  • Route positive replies to AE for immediate follow-up
  • Auto-pause cadence on OOO, resume when they're back
  • Flag negative replies for sequence refinement
Phase 5: Analytics
  • Cadence performance: meetings booked per 100 enrollments
  • Step performance: which step type/timing drives most replies
  • Rep leaderboard: meetings, reply rates, cadence completion
  • A/B testing: subject lines, openers, send times

Output Format

Salesloft setup guide with: cadence library, step configuration, team routing rules, analytics dashboard, and A/B test plan.

Quality Check

Before delivering, verify:

  • All required sections are complete
  • Output matches the user's stated need
  • Named frameworks are cited for key recommendations
  • No vague claims — every recommendation has a specific action
  • Deliverable is ready for operational use, not just conceptual

Common Pitfalls

  1. Skipping research. Building output without understanding the specific context. Fix: always gather required inputs before producing deliverables.
  2. Generic output. "Improve your process" without concrete steps. Fix: every recommendation must include a specific action, timeline, and owner.
  3. Missing framework citations. Advice without named authorities. Fix: ground every recommendation in a cited framework from a recognized authority.

Execution Artifacts

  • references/framework-notes.md — Rhythm cadences, CRM verify gate, enterprise governance
  • templates/output-template.md — CRM fields + cadence + enrollment gate deliverable
  • scripts/check-output.py — local checklist validator This skill includes lightweight artifacts the agent can load on demand:
  • references/enrichment-enrollment-gate.md — CRM lm_email_status before cadence enroll
  • references/pat-spielmann-outbound-copy.md — verify-before-enroll (Pat Spielmann)
  • references/gtm-table-blueprints.md — clay-toolkit CRM field patterns
  • the clay-loops-toolkit skill — clay-loops-toolkit signal cadences
  • references/gtm-experts-outbound-index.md — expert router Use the artifacts when the user asks for an implementation-ready deliverable, a repeatable workflow, or a quality check rather than generic advice.

Implementation Depth

Use this section when the user asks for a finished asset, not a high-level explanation.

Diagnostic Questions
  1. What is the primary motion: founder-led, sales-led, product-led, partner-led, or lifecycle-led?
  2. Which ICP tier is the output for: small business, mid-market, enterprise, or mixed?
  3. What proof is available today: customer stories, usage data, third-party validation, screenshots, or none?
  4. What system will execute the work: CRM, sequencer, warehouse, support desk, product analytics, or manual workflow?
  5. What decision will the user make from this output: launch, prioritize, route, rewrite, score, coach, or measure?
Framework Application

Map the recommendation explicitly to the named frameworks in this skill:

  • Salesloft Modern Selling Framework: apply only the part that directly improves the requested deliverable.
  • ColdIQ Cadence Design: apply only the part that directly improves the requested deliverable.
  • Outreach — Sales Engagement Cadence Design: apply only the part that directly improves the requested deliverable.
Deliverable Standard

A strong output from this skill includes:

  • A crisp diagnosis of the current situation
  • A recommended path with tradeoffs, not a generic list
  • A concrete artifact the user can use immediately: table, script, checklist, scorecard, sequence, dashboard spec, or implementation plan
  • A measurement plan with leading and lagging indicators
  • Risks and edge cases called out before execution
Adaptation Rules
  • For small business: reduce complexity, shorten time-to-value, and prioritize owner/operator clarity.
  • For mid-market: include workflow ownership, handoffs, integrations, and enablement assets.
  • For enterprise: include governance, risk, procurement, stakeholder mapping, and proof requirements.
  • cold-email-strategy, cold-calling, reply-handling, pipeline-management, multi-channel-outreach
1---
2name: salesloft-cadences
3description: >-
4 Builds and optimizes Salesloft cadences: Rhythm, Conversations, multi-channel
5 orchestration, and analytics. Use when the user is setting up or improving
6 cadences in Salesloft. Triggers on: "Salesloft", "Salesloft cadence",
7 "Rhythm", "Salesloft automation".
8license: MIT
9compatibility: Claude Code, Codex, GitHub Copilot, Cursor, Gemini CLI, OpenCode, Goose, Hermes, Windsurf, Zed
10metadata:
11 version: "1.0.0"
12 author: LeadMagic
13 category: tools
14 tags: [salesloft, cadence, rhythm, sales-engagement, outbound]
15 frameworks:
16 - "Salesloft Help Center — Cadences and Rhythm"
17 - "Google and Yahoo — Bulk sender requirements (2024)"
18 - "The Bridge Group — SDR metrics research"
19---
20 
21# Salesloft Cadences
22 
23## Overview
24Salesloft is the market leader in sales engagement. Cadences here manage Rhythm
25(multi-channel cadences), Conversations (reply management), and Deals (pipeline
26integration). This skill covers setup, optimization, and team workflows.
27 
28## Authoritative Foundations
29- **Salesloft Help Center — Cadences and Rhythm** — Configure cadence steps and let Rhythm prioritize tasks from buyer signals so reps work the highest-value action first.
30- **Google and Yahoo — Bulk sender requirements (2024)** — Authenticate with SPF, DKIM, and DMARC, keep spam complaints below 0.3%, and respect per-mailbox volume.
31- **The Bridge Group — SDR metrics research** — Benchmark activity and conversion per rep against published SDR data before judging cadence performance.
32 
33## When to Use
34- "Set up Salesloft cadences"
35- "Build Salesloft Rhythm"
36- "Salesloft optimization"
37- "Salesloft team setup"
38 
39## Step-by-Step Process
40 
41### Phase 1: Cadence Architecture
42Design by motion type:
43- **Prospecting Cadence:** 6-8 touches over 14 days, email + call + LinkedIn
44- **Inbound Cadence:** 4 touches over 7 days, fast follow-up (speed-to-lead)
45- **Re-engagement Cadence:** 3 touches over 10 days, "still relevant?" angle
46- **Event Follow-up Cadence:** 2 touches over 5 days, reference the event
47- **AE Cadence:** 3 touches over 7 days, discovery-focused, less volume
48 
49### Phase 2: Step Types
50- **Email step:** Template with merge fields, plain text, from individual sender
51- **Call step:** Auto-logged, call script + talk track linked, voicemail drop
52- **Social step:** LinkedIn view, connection, or DM (manual task with template)
53- **Custom step:** Slack message, direct mail, gift send
54- **Wait step:** 2-5 business days between touches, skip weekends
55 
56### Phase 3: Team Configuration
57- **Persona-based cadences:** Different cadences for C-suite vs Director vs Manager
58- **Industry variants:** Different opener templates by industry
59- **Rep assignment rules:** Round-robin, territory-based, or account-owner
60- **Manager approval gates:** Require approval before high-touch sequences
61 
62### Phase 4: Conversation Intelligence
63- Auto-categorize replies: positive, negative, OOO, referral, unsubscribe
64- Route positive replies to AE for immediate follow-up
65- Auto-pause cadence on OOO, resume when they're back
66- Flag negative replies for sequence refinement
67 
68### Phase 5: Analytics
69- Cadence performance: meetings booked per 100 enrollments
70- Step performance: which step type/timing drives most replies
71- Rep leaderboard: meetings, reply rates, cadence completion
72- A/B testing: subject lines, openers, send times
73 
74## Output Format
75Salesloft setup guide with: cadence library, step configuration, team routing rules,
76analytics dashboard, and A/B test plan.
77 
78 
79 
80## Quality Check
81 
82Before delivering, verify:
83- [ ] All required sections are complete
84- [ ] Output matches the user's stated need
85- [ ] Named frameworks are cited for key recommendations
86- [ ] No vague claims — every recommendation has a specific action
87- [ ] Deliverable is ready for operational use, not just conceptual
88 
89## Common Pitfalls
90 
911. **Skipping research.** Building output without understanding the specific context. Fix: always gather required inputs before producing deliverables.
922. **Generic output.** "Improve your process" without concrete steps. Fix: every recommendation must include a specific action, timeline, and owner.
933. **Missing framework citations.** Advice without named authorities. Fix: ground every recommendation in a cited framework from a recognized authority.
94 
95## Execution Artifacts
96 
97- `references/framework-notes.md` — Rhythm cadences, CRM verify gate, enterprise governance
98- `templates/output-template.md` — CRM fields + cadence + enrollment gate deliverable
99- `scripts/check-output.py` — local checklist validator
100This skill includes lightweight artifacts the agent can load on demand:
101- `references/enrichment-enrollment-gate.md` — CRM lm_email_status before cadence enroll
102- `references/pat-spielmann-outbound-copy.md` — verify-before-enroll (Pat Spielmann)
103- `references/gtm-table-blueprints.md` — clay-toolkit CRM field patterns
104- the `clay-loops-toolkit` skill — clay-loops-toolkit signal cadences
105- `references/gtm-experts-outbound-index.md` — expert router
106Use the artifacts when the user asks for an implementation-ready deliverable, a repeatable workflow, or a quality check rather than generic advice.
107 
108## Implementation Depth
109 
110Use this section when the user asks for a finished asset, not a high-level explanation.
111 
112### Diagnostic Questions
113 
1141. What is the primary motion: founder-led, sales-led, product-led, partner-led, or lifecycle-led?
1152. Which ICP tier is the output for: small business, mid-market, enterprise, or mixed?
1163. What proof is available today: customer stories, usage data, third-party validation, screenshots, or none?
1174. What system will execute the work: CRM, sequencer, warehouse, support desk, product analytics, or manual workflow?
1185. What decision will the user make from this output: launch, prioritize, route, rewrite, score, coach, or measure?
119 
120### Framework Application
121 
122Map the recommendation explicitly to the named frameworks in this skill:
123 
124- Salesloft Modern Selling Framework: apply only the part that directly improves the requested deliverable.
125- ColdIQ Cadence Design: apply only the part that directly improves the requested deliverable.
126- Outreach — Sales Engagement Cadence Design: apply only the part that directly improves the requested deliverable.
127 
128### Deliverable Standard
129 
130A strong output from this skill includes:
131 
132- A crisp diagnosis of the current situation
133- A recommended path with tradeoffs, not a generic list
134- A concrete artifact the user can use immediately: table, script, checklist, scorecard, sequence, dashboard spec, or implementation plan
135- A measurement plan with leading and lagging indicators
136- Risks and edge cases called out before execution
137 
138### Adaptation Rules
139 
140- For small business: reduce complexity, shorten time-to-value, and prioritize owner/operator clarity.
141- For mid-market: include workflow ownership, handoffs, integrations, and enablement assets.
142- For enterprise: include governance, risk, procurement, stakeholder mapping, and proof requirements.
143 
144 
145## Related Skills
146- cold-email-strategy, cold-calling, reply-handling, pipeline-management, multi-channel-outreach
147 

Discussion