Token导航 LogoToken导航

Agent Skill · 研究检索

outbound-sequencer(出站排序器)

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

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

总安装 2,109周安装 87GitHub Stars 85下载 689核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/guia-matthieu/clawfu-skills --skill outbound-sequencer

这个 Skill 是做什么的

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

outbound-sequencer 用于查找、检索和筛选相关信息。适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词快速定位候选结果。通过 npx skills add 命令从指定仓库安装,需结合 README 确认具体用法。安装前建议核实权限范围、维护状态及是否涉及联网或文件操作。

适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/outbound-sequencer

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

outbound-sequencer 怎么安装?

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

outbound-sequencer 支持哪些 AI 工具?

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

outbound-sequencer 需要什么权限?

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

outbound-sequencer 是免费的吗?

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

outbound-sequencer 用的人多吗?

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

outbound-sequencer 安全吗?

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

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

值得选的地方

  • 同时适配 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调用外部服务未明确有提醒
outbound-sequencer

出站排序器 · 本页

2,10985需要联网未明确有提醒

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

SKILL.md 原文

Outbound Sequencer

Create high-converting outbound sequences with strategic touchpoint timing, channel orchestration, and message progression.

When to Use This Skill

  • Designing new outbound campaigns
  • Optimizing existing sequences
  • Creating segment-specific cadences
  • Testing sequence variations
  • Training SDRs on best practices

Methodology Foundation

Based on Outreach.io Sequence Science and SalesLoft Cadence Research, combining:

  • Optimal touchpoint timing
  • Multi-channel orchestration
  • Message progression strategy
  • Personalization at scale

What Claude Does vs What You Decide

Claude DoesYou Decide
Designs sequence structureMessage copy
Suggests optimal timingBrand voice
Recommends channel mixTool selection
Creates progression logicA/B test priorities
Identifies optimization areasResource allocation

Instructions

Step 1: Define Sequence Parameters

Key Variables:

ParameterOptions
Touches8-14 typical
Duration14-30 days
ChannelsEmail, Phone, LinkedIn, Video
GoalMeeting, Response, Qualification

Step 2: Design Channel Mix

Recommended Mix:

ChannelPercentagePurpose
Email50-60%Scale, persistence
LinkedIn20-25%Personal touch
Phone15-20%Direct connection
Video5-10%Differentiation

Step 3: Structure Touchpoints

Framework: 4-Phase Sequence

PhaseDaysPurposeIntensity
Opening1-3Hook, establishHigh
Building4-10Value, credibilityMedium
Urgency11-18Social proof, FOMOHigh
Breakup19-25Final push, close loopLow

Step 4: Message Progression

Progression Pattern:

  1. Touch 1: Hook with insight/trigger
  2. Touch 2-3: Value proposition, social proof
  3. Touch 4-6: Different angles, persistence
  4. Touch 7-9: Urgency, scarcity
  5. Touch 10+: Breakup, future timing

Examples

Example 1: Enterprise Outbound Sequence

Output:

## Enterprise Outbound Sequence (14 touches, 21 days)

### Sequence Overview
- **Target**: VP+ at enterprise companies
- **Goal**: Booked meeting
- **Duration**: 21 days
- **Touches**: 14 total

### Channel Mix
| Channel | Touches | % |
|---------|---------|---|
| Email | 7 | 50% |
| LinkedIn | 4 | 29% |
| Phone | 2 | 14% |
| Video | 1 | 7% |

---

### Full Sequence

#### Phase 1: Opening (Days 1-3)

**Day 1 - Email #1 (Trigger-based)**

Subject: [Trigger] + [Company]

Hi [FirstName],

[Trigger observation - funding, hire, news].

I work with [similar companies] who face [challenge]. Curious if that's on your radar?

[One line value prop]

Worth a quick call?

[Name]

**Day 1 - LinkedIn Connection**
- Send connection request
- Note: "Hi [Name], [brief reason for connecting]"

**Day 2 - Phone Call #1**
- Goal: Live conversation
- If VM: "Hi [Name], [Name] from [Company]. Quick call about [trigger]. Will follow up via email."

**Day 3 - LinkedIn Voice Note**
- 30-second personalized message
- Reference trigger + offer value

---

#### Phase 2: Building (Days 4-10)

**Day 4 - Email #2 (Value)**

Subject: Re: [Previous subject]

[FirstName],

Wanted to share what [Similar Customer] achieved:

  • [Metric 1]
  • [Metric 2]

They were in a similar situation when we first connected.

Worth comparing notes?

[Name]

**Day 6 - LinkedIn Engagement**
- Engage with their content (like, comment)
- OR share relevant content, tag them

**Day 8 - Email #3 (Different Angle)**

Subject: Quick question about [specific challenge]

[FirstName],

Most [Titles] I talk to say [specific challenge] is their #1 priority this quarter.

Quick question: Is that true for you too, or is something else taking priority?

Genuinely curious—helps me understand what matters most to leaders like you.

[Name]

**Day 10 - Phone Call #2**
- Morning attempt
- Different VM: "Hi [Name], following up on my emails. Would love 15 minutes to discuss [value]. [Your number]."

---

#### Phase 3: Urgency (Days 11-18)

**Day 11 - Email #4 (Social Proof)**

Subject: How [Competitor's Customer] solved [problem]

[FirstName],

[Competitor's Customer] was dealing with [same problem].

After [implementing solution], they saw: • [Result 1] • [Result 2]

Happy to walk through their approach if useful.

[Name]

**Day 13 - LinkedIn Direct Message**

Hi [Name],

I've reached out a few times—wanted to try a different channel.

Not trying to sell you anything. Genuinely think [insight] could help [Company].

Open to a quick chat?

**Day 15 - Email #5 (Video)**

Subject: Recorded this for you, [FirstName]

[FirstName],

Put together a 60-second video on why I think [Company] would benefit from [approach].

[Video thumbnail/link]

If this resonates, let's talk. If not, no worries—I'll stop reaching out.

[Name]

**Day 18 - Email #6 (Urgency)**

Subject: [Event/timing trigger]

[FirstName],

With [event/quarter end/budget cycle] coming up, a lot of [Titles] are locking in [decisions].

Last chance to get this on your calendar before [deadline].

Quick call this week?

[Name]

---

#### Phase 4: Breakup (Days 19-21)

**Day 19 - LinkedIn Final**
- Send article or resource relevant to them
- No ask, just value

**Day 21 - Email #7 (Breakup)**

Subject: Should I close your file?

[FirstName],

I've reached out several times and haven't heard back. Totally understand—you're busy.

Just want to check: should I close out your file, or is this something worth revisiting in the future?

If timing isn't right, let me know and I'll circle back in [timeframe].

Either way, wishing you a great [quarter/year].

[Name]

---

### Sequence Metrics (Benchmarks)

| Metric | Target | Excellent |
|--------|--------|-----------|
| Open Rate | >40% | >55% |
| Reply Rate | >8% | >15% |
| Meeting Rate | >3% | >6% |
| Positive Reply | >60% of replies | >75% |

Example 2: High-Velocity SMB Sequence

Output:

## SMB Quick-Hit Sequence (8 touches, 14 days)

### Sequence Overview
- **Target**: Manager/Director at SMB
- **Goal**: Demo or trial signup
- **Duration**: 14 days
- **Touches**: 8 total

### Channel Mix
| Channel | Touches | % |
|---------|---------|---|
| Email | 5 | 63% |
| LinkedIn | 2 | 25% |
| Phone | 1 | 12% |

---

### Rapid Sequence

**Day 1 - Email #1 (Direct)**

Subject: Quick question, [FirstName]

Hi [FirstName],

Do you handle [function] at [Company]?

If so, I have an idea that could help you [specific outcome] in [timeframe].

Interested?

[Name]

**Day 1 - LinkedIn Connect**
- Simple connection request

**Day 3 - Email #2 (Value)**

Subject: Re: Quick question

[FirstName],

[One stat or proof point from similar company]

That's what [Customer] did with us.

Worth 10 minutes to see if we can do the same for [Company]?

[Name]

P.S. Here's a 2-min video showing how: [link]

**Day 5 - Phone Call**
- Quick call attempt
- VM: Keep to 20 seconds

**Day 7 - LinkedIn Message**

Hey [Name] - saw you opened my email but haven't had a chance to connect. Totally get it. Is [problem] even a priority for you right now?

**Day 9 - Email #3 (Different Hook)**

Subject: [Competitor name] alternative?

[FirstName],

A lot of [Company size] companies tell us they're frustrated with [competitor/status quo].

We're simpler + faster. Most customers are up and running in [timeframe].

Worth a look?

[Name]

**Day 11 - Email #4 (Offer)**

Subject: Try us free?

[FirstName],

Want to just show you instead of tell you?

Here's a free [trial/assessment/audit]: [link]

No commitment, no call required.

[Name]

**Day 14 - Email #5 (Breakup)**

Subject: Last one from me

[FirstName],

Haven't heard back, so this will be my last email.

If [problem] becomes a priority, I'm here: [calendar link]

Good luck with everything!

[Name]

Skill Boundaries

What This Skill Does Well

  • Structuring sequence flow
  • Optimizing touchpoint timing
  • Balancing channel mix
  • Creating progression logic

What This Skill Cannot Do

  • Write final copy for you
  • Know your specific personas
  • Access sequence tools
  • Test variations automatically

References

  • Outreach.io Sequence Science
  • SalesLoft Cadence Research
  • Gong Outbound Best Practices
  • TOPO SDR Benchmark Report

Related Skills

  • icp-matching - Target the right accounts
  • signal-monitoring - Trigger-based outreach
  • lead-qualification-bant - Qualify responses

Skill Metadata

  • Domain: SDR Automation
  • Complexity: Intermediate
  • Mode: cyborg
  • Time to Value: 1-2 hours per sequence
  • Prerequisites: ICP, messaging framework

平台分布

Codex

34.12%
按下载量换算235

Claude

32.32%
按下载量换算223

Cursor

19.86%
按下载量换算137

Gemini CLI

10.83%
按下载量换算75

安全审计

Gen Agent Trust Hub

可疑

Socket

通过

Snyk

通过

权限和风险

需要联网

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

安装前确认

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

继续浏览同类 Skills