Token导航 LogoToken导航

Agent Skill · 研究检索

sales-cadence(销售节奏)

sales-cadence 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

sales-cadence 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描有提醒项,按安装量在研究检索类的 73,674 个 Skill 里排第 37,928。

总安装 1,646周安装 70GitHub Stars 13下载 577核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:sales-cadence(销售节奏)
来源仓库:https://github.com/sales-skills/sales
仓库路径:skills/sales-cadence
安装命令:
npx skills add https://github.com/sales-skills/sales --skill sales-cadence
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/sales-skills/sales --skill sales-cadence

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

sales-cadence 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。适用于销售研究、信息检索和线索筛选等需要精准匹配来源仓库的场景。

通过关键词或任务描述触发,返回符合条件的候选结果列表,支持进一步交互验证。安装命令为 npx skills add https://github.com/sales-skills/sales --skill sales-cadence,需确认权限范围和维护状态。

使用前请核实是否会触发联网、命令执行或文件读写操作,避免安全风险。

来源仓库内路径:skills/sales-cadence

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/sales-skills/sales --skill sales-cadence;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

sales-cadence 怎么安装?

在终端执行 npx skills add https://github.com/sales-skills/sales --skill sales-cadence。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

sales-cadence 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

sales-cadence 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

sales-cadence 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

sales-cadence 用的人多吗?

公开数据是累计安装 1,646 次,近一周安装 70 次,下载 577 次,GitHub 13 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

sales-cadence 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
sales-cadence

销售节奏 · 本页

1,64613需要联网未明确有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Design a Multi-Channel Outbound Cadence

Help the user design a complete outbound cadence for Salesloft, Mailshake, Smartlead, Lemlist, Yesware, or Hunter.io — from architecture and timing through full content for every step, A/B testing, and optimization benchmarks.

Step 1 — Gather context

If references/learnings.md exists, read it first for accumulated knowledge.

Ask the user:

  1. What's the campaign goal?

- A) Cold outbound — net-new prospects, no prior relationship - B) Inbound follow-up — responding to a lead that came in - C) Trigger-based — responding to a signal (job change, funding round, tech install, intent data) - D) Re-engagement — reviving a cold or stalled conversation - E) Expansion — reaching new contacts at existing customer accounts - F) Other — describe it

  1. Who is the target persona? (title, seniority, industry, company size)
  2. What channels are available?

- A) Email only - B) Email + phone - C) Email + phone + LinkedIn - D) Email + phone + LinkedIn + video - E) Other combination — describe

  1. What constraints should I know about?

- Total duration (e.g., 14 days, 21 days, 30 days) - Max touches per week - Existing messaging or value props to incorporate - Compliance requirements (GDPR, CAN-SPAM, industry-specific) - Any channels to avoid or emphasize

If the user's request already provides most of this context, skip directly to the relevant step. Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end — don't gate your response behind gathering complete context.

Step 2 — Cadence architecture

Design the cadence structure as a table:

DayStepChannelActionNotes
11EmailIntro email (A/B subject lines)Personalization Level 3+
12LinkedInProfile view + connection requestSame day as email
33PhoneCall attempt #1 + voicemailReference email
44EmailFollow-up email (value-add)Different angle from Step 1
...............

Design principles

  • Channel mixing: Never send 3+ touches in the same channel consecutively. Alternate between email, phone, and LinkedIn.
  • Spacing:

- Days 1-7: Higher intensity (touch every 1-2 days) — this is when engagement peaks - Days 8-14: Medium intensity (every 2-3 days) - Days 15+: Lower intensity (every 3-4 days) — don't burn the prospect

  • Touch count by persona (typical ranges — adjust based on persona, sales cycle, and industry norms):

- C-suite / VP: 8-12 touches over 21-28 days (less aggressive, more spaced) - Director / Manager: 12-16 touches over 21-30 days (standard) - Individual contributor / practitioner: 10-14 touches over 14-21 days (shorter cycle)

  • Phone placement: Always within 24 hours after an email so you can reference it ("I just sent you a note about...")
  • LinkedIn: Use early for connection + later for social proof or content sharing. Don't be repetitive with email.
  • Final touch: Always a "breakup" email — creates urgency without being pushy

Step 3 — Write content for every step

For each step in the cadence, write the actual content:

Email templates

For each email:

  • Subject line: Provide A/B variants (Variant A and Variant B)
  • Body: Full email text with personalization tokens in {{brackets}}
  • CTA: Specific ask (meeting, reply, resource)
  • Keep emails under 125 words for cold outbound, under 200 for warm follow-up

Call scripts

For each call step:

  • Opening (first 10 seconds — must earn the right to continue)
  • Reason for calling (one sentence connecting to their world)
  • Key questions (2-3 if they engage)
  • Ask (meeting request with specific time)
  • Voicemail script (under 30 seconds, always leave one)

LinkedIn messages

  • Connection request note: Under 300 characters, no selling
  • Follow-up InMail or message: Reference a specific post, mutual connection, or insight about their company
  • Keep LinkedIn casual and conversational — it's a social platform, not email

Video guidance (if applicable)

  • When to use: Steps 5+ when email hasn't gotten a response
  • Duration: 60-90 seconds max
  • Structure: Say their name, show you did research, one key insight, soft CTA

For platform-specific cadence implementation (Salesloft, Mailshake, Lemlist, Smartlead, Mixmax, Reply.io, Woodpecker, Hunter.io, Seamless.AI, Closum, Minelead, GetProspect, ZoomInfo, Snov.io, 6sense, Clay, BrandJet, AiSDR, Nooks, Orum, Amplemarket, Sendr, LeadIQ), see references/platforms.md.

Personalization framework

  • Level 1 (Minimum): First name, company name, title — the bare minimum
  • Level 2 (Standard): Industry reference, company-size-specific pain point
  • Level 3 (Strong): Something specific about their company (recent news, tech stack, job posting, quarterly results)
  • Level 4 (Elite): Personal insight (their LinkedIn post, podcast appearance, conference talk, published article)

Recommend Level 3+ for all touches in a cold outbound cadence. Level 2 is acceptable for re-engagement at scale.

For Level 3+ at scale (100+ prospects), consider AI personalization: Smartlead SmartAgents, Clay, or custom GPT workflows to research each prospect and generate personalized snippets for {{custom_field}} merge variables. This automates the research step that makes Level 3-4 feasible at volume.

Step 4 — A/B testing plan

Design an A/B testing strategy:

Test #What to testVariant AVariant BMetricMin sample size
1Subject line (Step 1)Pain-focusedCuriosity-basedOpen rate100 sends each
2CTA style (Step 1)Specific time askOpen-ended questionReply rate100 sends each
3Email length (Step 4)Short (75 words)Medium (125 words)Reply rate100 sends each

A/B testing rules

  • Test one variable at a time
  • Run each test for at least 100 sends per variant (200+ preferred) before drawing conclusions
  • Primary metric: positive reply rate (not just open rate)
  • Wait at least 5 business days before evaluating results
  • Roll the winner into the cadence and start the next test
  • Always be testing something — cadences decay over time as messaging gets stale

Step 5 — Metrics and optimization

Provide a benchmarks table:

MetricGoodGreatIf below "Good"...
Open rate40-50%50%+Fix subject lines, check deliverability, verify email addresses
Reply rate (total)8-12%15%+Improve personalization, test different angles, check targeting
Positive reply rate3-5%7%+Revisit value prop, check ICP fit, strengthen the ask
Meeting booked rate2-4%5%+Improve CTA clarity, offer more flexibility, add social proof
Bounce rate<3%<1%Clean your list, use email verification tools, check domain health
Unsubscribe rate<1%<0.5%Reduce frequency, improve relevance, check compliance
Call connect rate5-10%12%+Try different times of day, use local presence dialing, vary call days

Optimization cadence

  • Week 1-2: Let the cadence run, gather baseline data
  • Week 3-4: Analyze first A/B test results, implement winners
  • Monthly: Review full-funnel metrics, retire underperforming steps, test new angles
  • Quarterly: Major refresh — new messaging, updated case studies, seasonal angles

Before recommending a specific platform skill

This skill covers a strategy domain across many platforms. Before pointing the user to any specific platform skill (any /sales-{platform} listed in ## Related skills, e.g., /sales-mailshake, /sales-klaviyo, /sales-apollo), read that platform skill's actual SKILL.md first. The 1-line description in ## Related skills is enough to *identify* a candidate — it's not enough to *commit* to it or to write a prompt that invokes it well.

How to read it:

  • If ~/.claude/skills/{skill-name}/SKILL.md exists locally, Read it.
  • For sales-* skills, WebFetch directly from this repo: https://raw.githubusercontent.com/sales-skills/sales/main/skills/{skill-name}/SKILL.md — e.g., for sales-mailshake: https://raw.githubusercontent.com/sales-skills/sales/main/skills/sales-mailshake/SKILL.md.
  • For non-sales-* skills (third-party), look up {org}/{repo} in ~/.claude/skills/sales-do/references/skill-sources.md if installed and fetch the same skills/{skill-name}/SKILL.md path under that repo.

After reading, ground your recommendation in something concrete from the SKILL.md (its scope, a sub-flow, its argument-hint shape, or a "Do NOT use for..." negative trigger). Align any generated invocation with the platform skill's argument-hint. If the platform skill turns out not to fit the user's situation, swap to another or handle the question here directly rather than recommending a poor fit.

Related skills

  • /sales-salesloft — General Salesloft platform help (Rhythm, Analytics, Drift, admin)
  • /sales-deliverability — Email deliverability — SPF/DKIM/DMARC, warmup, inbox placement
  • /sales-mailshake — Mailshake platform help (campaigns, Lead Catcher, settings)
  • /sales-smartlead — Smartlead platform help (campaigns, SmartSenders, SmartAgents, API)
  • /sales-lemlist — Lemlist platform help (sequences, Lemwarm, LinkedIn automation, enrichment, API)
  • /sales-call-review — Review calls from your cadence to improve scripts
  • /sales-email-tracking — Email engagement tracking — open/click/attachment signals for follow-up timing
  • /sales-brandjet — BrandJet AI platform help — multi-channel outreach, brand intelligence, AI monitoring
  • /sales-revenue-io — Revenue.io platform help (Salesforce-native Guided Selling cadences, RingDNA dialer, Moments coaching)
  • /sales-nooks — Nooks platform help (AI parallel dialer, multi-channel sequencing, coaching, waterfall enrichment)
  • /sales-orum — Orum platform help (AI parallel dialer, coaching suite, virtual salesfloor)
  • /sales-outreach-io — Outreach platform help (sequences, Kaia CI, deal management, forecasting, coaching)
  • /sales-amplemarket — Amplemarket platform help (all-in-one: data + sequences + signals + deliverability + Duo AI)
  • /sales-sendr — Sendr platform help (lipsync video, dynamic pages, Lead Finder, campaign sequencing)
  • /sales-leadiq — LeadIQ platform help (Scribe AI outreach writer, Chrome extension prospecting, champion tracking)
  • /sales-do — Not sure which skill to use? The router matches any sales objective to the right skill

Gotchas

  • Don't make all touches email-only. Claude defaults to generating email-heavy cadences. A real cadence needs channel mixing — if the user has phone and LinkedIn available, use them from the start, not as afterthoughts.
  • Don't space touches too close together. Avoid scheduling touches less than 2 business days apart (except same-day email + LinkedIn on Day 1). Prospects need time to engage before you follow up.
  • Don't write generic "just checking in" follow-ups. Every touch must add new value or a new angle. If you catch yourself writing "I wanted to follow up on my last email," rewrite it with a new hook.
  • Don't ignore timezone for call steps. Phone calls placed outside business hours are wasted touches. If you know the prospect's timezone, note the best call windows (typically 8-10am and 4-6pm local time).
  • Don't generate a cadence without confirming channel availability first. If the user didn't specify channels, ask — don't assume they have LinkedIn Sales Navigator or a phone dialer.
  • Self-improving: If you discover something not covered here, append it to references/learnings.md with today's date.

Examples

Example 1: Cold outbound cadence

User says: "Build a 21-day cold outbound cadence for VP Engineering at Series B SaaS companies. We have email, phone, and LinkedIn." Skill does:

  1. Designs a 14-step cadence architecture table with channel mixing
  2. Writes full email copy with A/B subject lines, call scripts with voicemail, LinkedIn messages
  3. Provides an A/B testing plan and benchmark metrics Result: Complete cadence ready to import into Salesloft with content for every step

Example 2: Cadence optimization

User says: "My cadence has 35% open rate but only 2% reply rate. What's wrong?" Skill does:

  1. Diagnoses the gap (subject lines work, body/CTA needs fixing)
  2. Recommends specific changes to email body, personalization, and CTA
  3. Designs an A/B test plan to validate improvements Result: Prioritized optimization plan with testable hypotheses

Troubleshooting

Low open rates (<30%)

Cause: Subject lines aren't compelling, or deliverability issues Solution: Test pain-focused vs. curiosity-based subject lines. Check domain reputation, SPF/DKIM records, and bounce rate. If bounce rate >3%, clean your list first.

High open rate but low reply rate

Cause: Email body doesn't deliver on the subject line promise, CTA is weak or unclear, or personalization is too generic Solution: Ensure the first sentence connects to the prospect's world. Make the CTA specific ("15 minutes Thursday?") not vague ("let me know if interested"). Increase personalization to Level 3+.

Prospects engaging but not booking meetings

Cause: Too many touchpoints before the ask, or the ask is buried Solution: Include a clear meeting CTA by Step 3. Use the phone step within 24 hours of an email open. Offer a specific time, not an open question.

平台分布

Codex

38.08%
按下载量换算220

Claude

27.78%
按下载量换算160

Cursor

17.76%
按下载量换算102

Gemini CLI

9.25%
按下载量换算53

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills