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

outbound-sequences出站序列

Agent Skill

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

总安装

1,056

周安装

44

GitHub Stars

37

下载量

352
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/majesticlabs-dev/majestic-marketplace --skill outbound-sequences

简介

outbound-sequences 用于查找、检索和筛选相关信息。

  • 适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词快速定位候选结果。
  • 通过 npx skills add 命令从指定仓库安装,需结合 README 确认具体用法。
  • 安装前建议核实权限范围、维护状态及是否涉及联网或文件操作。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Outbound Sequences

Design high-response cold outreach sequences for email, phone, and LinkedIn.

Input Context

Expect structured context from orchestrator:

current_metrics:
  open_rate: percent
  reply_rate: percent
  meeting_rate: percent
diagnosed_problem: subject_lines | copy | targeting | CTA
target_persona:
  title: string
  industry: string
  company_size: string
channels: [email, phone, linkedin]
value_prop: string
social_proof: string
current_best: string  # sample copy
tool: Apollo | Outreach | Lemlist | etc.

Sequence Architecture

Multi-Channel Sequence (7 touches)

Day 1:  Email #1 (Initial) ──→ Day 3: LinkedIn Connect
Day 4:  Email #2 (Value-add) ──→ Day 6: LinkedIn Message
Day 7:  Phone Call ──→ Day 8: Email #3 (Insight)
Day 10: LinkedIn Engage ──→ Day 12: Email #4 (Case Study)
Day 15: Email #5 (Breakup)

RESPONSE BRANCHES:
Positive → Discovery call booking sequence
Objection → Objection handler sequence
"Not Now" → Nurture sequence (30-day follow-up)

Channel Templates

Response Handling

Positive Response

{{first_name}}, great to hear from you!

I have {{day}} at {{time}} or {{day}} at {{time}} available.

Here's my calendar if easier: {{link}}

Looking forward to it.

{{sender_name}}

Objection Response

{{first_name}}, appreciate the candid response.

Totally understand {{their_objection}}.

Quick question: {{question_uncovering_real_concern}}

Either way, happy to {{lower_commitment_offer}}.

{{sender_name}}

"Not Now" Response

{{first_name}}, completely understand - timing is everything.

When would be a better time to revisit this?

Happy to reach back out in {{timeframe}} if that works.

{{sender_name}}

"Send More Info" Response

{{first_name}}, happy to share more.

Here's {{one_specific_asset}}: {{link}}

Quick question: What specifically prompted the interest?

That'll help me tailor what I send next.

{{sender_name}}

Personalization Framework

TierTime/ProspectWhat to Include
Tier 1 (Basic)30 secName, company, industry
Tier 2 (Researched)2-3 minNews, LinkedIn content, job postings
Tier 3 (Deep)10-15 minPodcast quotes, custom video, mutual connections

Research Sources

  • LinkedIn posts and activity
  • Company news/press releases
  • Job postings (indicate priorities)
  • Podcast appearances
  • Conference presentations
  • Mutual connections

Timing Optimization

Sequence Spacing

  • Email to email: 3-4 days
  • Email to LinkedIn: 1-2 days
  • LinkedIn to phone: 1 day
  • After no response: wait 3 days
  • Breakup email: day 14-15

Output Format

# OUTBOUND SEQUENCE: {{Company Name}}

## Target Persona
{{title}}, {{industry}}, {{company_size}}

## Sequence Architecture
[Visual flow diagram]

## Email Sequence
### Email 1: Initial (Day 1)
**Subject:** [3 options]
**Preview:** [preview text]
**Copy:** [full email]
**Personalization:** [variables used]

### Email 2: Follow-up (Day 4)
...

## LinkedIn Sequence
### Touch 1: Connection (Day 3)
...

## Cold Call Script
[Opening + structure + objection handling]

## Response Playbook
[Templates for each response type]

## A/B Test Variants
[Specific tests for diagnosed problem area]

Anti-Patterns

MistakeWhy It FailsFix
Generic opener"Hope you're well" ignoredSpecific observation
Feature dumpThey don't care yetLead with their pain
Multiple CTAsConfusion, lower responseSingle clear ask
Long emailsWon't be read on mobileUnder 75 words
Same angle each emailNo reason to replyNew value per touch
No personalizationFeels like spamAdd {{variables}}

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

37.34%
按下载量换算131

Claude

30.22%
按下载量换算106

Cursor

18.38%
按下载量换算65

Gemini CLI

8.46%
按下载量换算30

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

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

来源信息

继续浏览同类 Skills