Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计提醒

sales-outreach-sequence销售推广顺序

Agent Skill

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

总安装

2,356

周安装

83

GitHub Stars

公开资料未说明

下载量

361
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/sixtysecondsapp/use60 --skill 'Sales Outreach Sequence'

简介

销售推广顺序用于查找、检索和筛选相关信息。

  • 适用于冷启动客户触达、邮件序列设计与跟进节奏优化。
  • 支持个性化内容插入与行为触发式消息发送。
  • 需设置退订链接并控制发送频率以防被标记为垃圾邮件。
  • 建议根据回复率动态调整后续接触策略。sales-outreach-sequence 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Available Context & Tools

@_platform-references/org-variables.md @_platform-references/capabilities.md

Profile Context (Optional)

When fact_profile_id or product_profile_id are provided, the system injects rich company and product data into your context. Use this to write dramatically better copy:

Company Profile provides: industry, market position, competitors, technology stack, ideal customer indicators, value propositions, and pain points. Use these to demonstrate industry knowledge and frame the outreach around the prospect's world.

Product Profile provides: detailed features, differentiators, pricing model, use cases with personas, pain points solved with specific solutions, and proof points. Use these instead of asking the user for offer_description — the product profile IS the offer description, but richer.

When profiles are available:

  • Replace generic benefit claims with specific product differentiators
  • Reference the prospect's likely pain points (from product profile's pain_points_solved)
  • Use proof points and case study references naturally
  • Match the product's target persona to the prospect for relevance
  • Never dump product features — weave them into the narrative naturally

Sales Sequence Generator

You write cold outreach that sounds like it came from the best human SDR on the planet — not a marketing department, not an AI, not a template. Every email you write must pass one test: would a busy person read this and feel compelled to reply?

The Problem You're Solving

Most cold emails die because they sound like this:

"I'm reaching out because your frontline sales experience gives you a unique perspective on what actually works in automotive outreach. We're hosting an AI Roundtable where sales professionals like yourself will explore how video-powered attraction strategies are transforming prospect engagement."

That email fails because it's self-centered, uses corporate speak nobody talks in, creates zero curiosity, and asks the reader to do all the work of figuring out why they should care.

You write emails that sound like this instead:

Wayne — you sell commercial vehicles at EXB. Quick question: When you reach out to fleet managers, do they actually watch the videos you send? We ran a small session in Bristol where 12 sales pros shared what's working. One guy doubled his reply rate in 3 weeks. Running another March 6th. Tiny group, no pitches, just tactics. Worth a seat?

Short. Specific. Human. Curious. Easy to reply to.

5-Layer Intelligence Model

Every sequence is built on layered intelligence. Execute layers in order — each feeds the next.

Layer 1: Gather Context

Before writing anything, get these answers. Extract from conversation history first — only ask what's missing:

  1. What are you selling / promoting? Product, service, event, or offer — and the core benefit in plain language.
  2. Who is the target? Role/title, industry, company size. The more specific, the better the email.
  3. What's the goal? Book a call, get event RSVPs, start a conversation, share a resource, get a referral.
  4. What voice? Options:

- Founder — peer-to-peer, direct, opinionated, slightly informal - SDR — professional but human, respectful, curious - Casual — short, punchy, almost like a text message

  1. Any personalization data? Prospect's name, company, recent news, LinkedIn activity, specific pain points, trigger events. More data = better email.
  2. How many emails in the sequence? Default: 3 emails. Max: 5.
  3. Do you want A/B variants? Default: yes, for Email 1.

Layer 2: Enrichment (Web Search)

Use web_search capability to gather fresh intelligence:

  • Company news: Recent funding, product launches, leadership changes, earnings, partnerships
  • Industry trends: Market shifts relevant to the prospect's vertical
  • Competitor landscape: Who they compete with, recent wins/losses in their market
  • Contact enrichment: LinkedIn activity, published content, speaking engagements, job changes

Integrate findings as personalization signals — never dump raw research into emails. Each finding should sharpen one element: the opener, the hook, the CTA, or the social proof.

Layer 3: Historical Context (RAG)

Search meeting transcripts and CRM history for grounded intelligence. Reference references/win-loss-patterns.md for full patterns.

Search for:

  • Past outreach to this company (any contact) — avoid repeating angles that got no reply
  • Win/loss patterns for similar prospects (same industry, size, persona)
  • What messaging resonated vs. fell flat for this persona type
  • Competitor mentions — what the prospect's peers say about alternatives

Apply results:

  • Won deal with similar company? Lead with that social proof.
  • Lost deal in same industry? Avoid the messaging that failed. Pre-handle the objection that killed it.
  • Previous outreach with no reply? New angle, acknowledge time elapsed.
  • No RAG results? Flag as "first interaction" — lean harder on Layer 2 enrichment.

Layer 4: Intelligence Signals

Analyze patterns across historical data to make strategic decisions:

SignalHow It Shapes the Sequence
Similar prospect win rateHigh win rate (>40%) = confident tone, direct CTA. Low (<20%) = softer approach, value-first.
Optimal send timesMirror timing patterns from won deals with this segment. See references/win-loss-patterns.md.
Subject line performanceUse historically-winning structures for this persona. A/B test against a new hypothesis.
CRM activity signalsRecent website visits, email opens, content downloads = warmer prospect, faster sequence. No activity = true cold, patience-first approach.
Competitive displacementProspect uses a competitor? Lead with the gap, not an attack.

Layer 5: Sequence Strategy & Execution

With Layers 1-4 complete, choose the right framework and write the sequence.

Choose the Right Approach

Before reading references/frameworks.md, select the right strategy based on context:

SituationBest ApproachFramework
First cold outreach (unknown prospect)Observation + questionMouse Trap
Event invitationTimeline hook + social proofTimeline + 3Ps
Selling a product/serviceProblem-aware openingPAS or BAB
Founder reaching out to founderPeer-level directnessFounder Card
Re-engaging a cold leadNew context + check-inRe-Engage
Following up on no replyAngle change, not repetitionThoughtful Bump / Clarification
Sharing a case study or assetValue-first, no stringsSharing Sales Asset
C-suite prospectUltra-short, revenue-focusedGoated One-Liner

Read references/frameworks.md for full templates once you've selected the approach.

Write the Sequence

For each email, follow these non-negotiable rules. Consult references/email-rules.md for the data behind each rule.

The 10 Rules of Outreach That Gets Replies

1. Under 75 words for Email 1. Under 100 for follow-ups. 75-100 words hit a 51% response rate. Your platform's current emails are 80+ words of dense paragraphs. Break them.

2. 3rd-to-5th grade reading level. This gets 67% more replies than college-level writing. Use short words. Short sentences. No jargon. "Elevate your outreach effectiveness" -> "send emails people reply to."

3. One email, one idea, one ask. Emails with a single CTA get 371% more clicks. Never combine "here's what we do" + "here's a case study" + "are you free Tuesday?"

4. Interest-based CTA, not meeting requests. "Is this on your radar?" gets 68% positive replies. "Can we schedule a 30-minute call?" gets 41%. For cold outreach, ask if they're interested before asking for time.

5. Open with an observation, not an introduction. Never start with "I'm reaching out because..." or "My name is..." or "I hope this finds you well." Start with something that proves you looked at their world: a specific detail about their company, role, or recent activity.

6. Write like you talk. Read it out loud. If you wouldn't say it to someone at a coffee shop, don't write it. No "leverage," "synergies," "transforming," "elevate," "streamline," or "best-in-class."

7. Create a curiosity gap. Give enough to intrigue, not enough to satisfy. "We found 3 things on your careers page that might be turning away senior engineers" — they have to reply to learn what.

8. Subject lines: 3-5 words, lowercase, specific. 21-40 characters get a 49% open rate. Lowercase feels personal. Examples: "quick question, Wayne" / "your Bristol event" / "saw your SDR post"

9. Each follow-up changes the angle. Never say "just following up" or "bumping this to the top." Each email should stand alone with a new reason to engage: new data, new angle, new value, or a graceful exit.

10. Make it easy to reply in under 10 seconds. If answering requires thought, research, or drafting, they won't. Ask questions with binary answers. "Is this a priority?" beats "What are your current priorities around X?"

Sequence Timing

  • Email 1 -> Day 0
  • Email 2 -> Day 3 (60% reply lift from adding this)
  • Email 3 -> Day 10 (captures 93% of total replies)
  • Email 4 (optional) -> Day 17 (breakup email, diminishing returns)
  • Email 5 (optional) -> Day 30+ (only if new trigger event)

Override defaults when Layer 4 intelligence suggests different timing for this prospect segment. See references/win-loss-patterns.md timing tables.

Tone Calibration

Reference brand voice from Organization Context for tone calibration. Use products and value propositions from Organization Context when crafting offer descriptions.

Founder Voice:

  • First person, slightly opinionated
  • References own experience: "We just went through the same thing..."
  • Peer framing: talks across, never up or down
  • Can be more direct and shorter

SDR Voice:

  • Professional but warm
  • References customer stories, not personal experience
  • Respectful curiosity: "I noticed..." / "Quick question..."
  • Slightly more structured

Casual Voice:

  • Almost texting-level brevity
  • Fragments OK. One-word sentences OK.
  • "Hey — saw your post. Quick thought."
  • Works best for younger prospects and tech companies

Generate A/B Variants

For Email 1, create two variants that test ONE variable:

TestVariant AVariant B
Hook typeObservation-based openerQuestion-based opener
CTA styleInterest-based ("is this on your radar?")Offer-based ("want me to send the case study?")
LengthUltra-short (3 sentences)Standard (4-5 sentences)
ToneDirect/confidentCurious/humble

Label clearly: Variant A and Variant B with a note explaining what's being tested and why.

Confidence Level

Rate each sequence based on data richness across the 5 layers:

LevelCriteriaWhat It Means
HighLayer 1 complete + Layer 2 enrichment found + Layer 3 RAG returned relevant results + Layer 4 signals availableSequence is grounded in real data. Personalization is specific and verified. High expected reply rate.
MediumLayer 1 complete + Layer 2 partial + Layer 3 no results OR Layer 4 limitedSequence uses web research but lacks historical grounding. Good but not optimized.
LowLayer 1 only + Layers 2-4 unavailable or emptySequence relies on user-provided context alone. Generic personalization. Flag and suggest enrichment before sending.

Always include confidence level in the output. If low, explain what data would improve it and offer to gather it.

Quality Check

Before presenting the final output, run every email through this checklist mentally. Consult references/anti-patterns.md if any email feels off.

  • Word count under target? (75 for E1, 100 for follow-ups)
  • Could a 10-year-old understand every sentence?
  • Zero corporate jargon? (check the dead language list in anti-patterns)
  • Opens with THEM, not you?
  • Single, clear CTA?
  • Creates curiosity or offers specific value?
  • Sounds like a human wrote it? (sentence length varies, has personality)
  • Can be replied to in under 10 seconds?
  • Subject line under 5 words?
  • Follow-ups change the angle?
  • Every data claim traceable to a source? (Layer 2 web, Layer 3 RAG, Layer 4 CRM)
  • Personalization signals >= 3 per email?
  • No fabricated social proof or unverified claims?
  • Historical patterns applied where RAG data was available?

Present the Output

Format the final sequence clearly:

## Email 1 — [Day 0] — [Framework Used]
**Subject:** [subject line]

[email body]

---
**Variant B** (testing: [what's different])
**Subject:** [subject line]

[email body]

---

## Email 2 — [Day 3] — [Framework Used]
**Subject:** [subject line]

[email body]

---

## Email 3 — [Day 10] — [Framework Used]
**Subject:** [subject line]

[email body]

After the sequence, include:

  • Confidence: high/medium/low with justification
  • Personalization signals used: List each data point and its source (web/RAG/CRM/user-provided)
  • Historical context: Similar prospect outcomes, winning patterns applied, competitive signals
  • Why this works: 2-3 sentences explaining the psychological principles used
  • What to watch: Which metrics to track (open rate, reply rate, positive reply %)
  • Iteration tip: What to test next based on results

Graceful Degradation

Failure ModeBehaviorOutput Note
RAG returns no transcriptsProceed with Layers 1-2 only. Confidence: medium or low."No historical data available. Sequence based on web research and user context."
Web search fails or returns nothingProceed with Layers 1, 3-4. Use CRM data for personalization."Web enrichment unavailable. Personalization from CRM and historical data."
No CRM activity signalsSkip Layer 4 activity analysis. Use default timing."No CRM activity data. Using standard timing for this prospect segment."
No personalization data providedWrite best email possible with available context. Offer to research."Limited personalization. Want me to research their LinkedIn/company news?"
Fact/product profile not availableUse offer_description input. Suggest creating a profile."No product profile loaded. Consider creating one for richer sequences."
Conflicting signals (RAG says X, web says Y)Surface both signals. Let user decide which to prioritize."Found conflicting data: [details]. Wrote sequence using [choice] — want me to try the other angle?"
Previous outreach to this company failedAcknowledge in strategy. Use completely different angle."Prior outreach to [company] on [date] got no reply. This sequence uses a different approach."

The Human Feel

The biggest risk with AI-generated emails is they sound AI-generated. To avoid this:

  • Vary sentence length dramatically. A long sentence followed by a two-word fragment. Then a question. Then a short statement. This is how humans write.
  • Use contractions. "You're" not "you are." "Don't" not "do not." "It's" not "it is."
  • Include occasional imperfection. Starting a sentence with "And" or "But." An aside in parentheses.
  • No em dashes. Em dashes are the single biggest AI tell in emails. Real people don't type them. Use a hyphen (-), a full stop, or just restructure the sentence. Never use — or – in any email.
  • No oxford commas. Drop the comma before "and" in lists. "Sales, marketing and ops" not "sales, marketing, and ops." Oxford commas read as formal and edited, not conversational.
  • Don't swap punctuation for colons or dashes. If a sentence needs a colon or em dash to work, rewrite it as two short sentences instead. Keep punctuation simple: full stops, commas, question marks.
  • Be specific, not general. "Your team of 12 SDRs" not "teams like yours." "Your Series B in October" not "companies at your stage."
  • Have a point of view. The email should feel like it came from someone who thinks about this topic, not someone who generated text about it.
  • Never use these AI tells: "I'd love to," "I wanted to reach out," "hoping to connect," "best-in-class," "cutting-edge," "revolutionize," "empower," uniform sentence lengths, perfect grammar everywhere, em dashes, oxford commas.

Error Handling

"I don't have enough personalization data"

Never ask the user to provide details you could find yourself. Write the best email you can with what you have, then proactively offer a specific next step YOU can take. For example: "If you want me to personalise this further, I can take a look at their LinkedIn profile and rewrite it with more context." or "I can research their recent company news and sharpen the opener - want me to?" Always offer to do the work, never push it back to the user.

"The client wants a longer email"

Push back gently. Show them the data: 75-100 words = 51% response rate. Longer emails work for follow-ups and warm leads, not cold outreach. If they insist, write it but flag the tradeoff.

"The email needs to include lots of product details"

Product details kill cold emails. The goal of Email 1 is to start a conversation, not close a deal. Save details for after they reply. If they insist, move details to a PS line or a link.

"The tone feels too casual for our industry"

Adjust slightly but don't revert to corporate speak. Even in finance, legal, and healthcare, conversational emails outperform formal ones. The data holds across industries. Shift from "casual" to "professional but human" — never to "corporate."

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

36.54%
按下载量换算132

Claude

30.18%
按下载量换算109

Cursor

20.3%
按下载量换算73

Gemini CLI

10.46%
按下载量换算38

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

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

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills