销售外联序列起草指南
安装方式
先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。
用 AI 助手安装
复制提示词,让助手先核对固定版本和依赖。
查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "deal-outreach":https://skillpi.com/zh/skills/deepskill-319c84b76449384d05591ca6d041199c85e19df7102e9598e30248be15f7d297。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/bundle/revenue-team/skills/deal-outreach/SKILL.md。来源不一致时停止并说明差异。核对通过后,用 Skill Finder 安装目标 Skill,并报告安装路径和来源版本。
此命令从 GitHub 来源仓库获取指定技能。运行前请先查看源文件。
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/bundle/revenue-team/skills/deal-outreach --skill deal-outreach来源与配置
查看 GitHub 源码jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402
配置方式待核实
请查看原始来源中的适用工具、依赖和权限要求。
安装实测待补充
按目标角色、理想客户特征、价值主张和联系渠道,起草多触点邮件或 LinkedIn 外联序列,并提供个性化提示。该技能只生成文案,不替你发送;使用前确认联系人数据来源与触达依据,逐条复核后再决定是否发送。
文件浏览
--- name: deal-outreach description: Cold outbound sequence builder — produces multi-touch email + LinkedIn sequences (5-7 touchpoints) personalized by persona type (technical buyer, economic buyer, champion). Use when asked to "write cold emails", "build an outbound sequence", "create prospecting emails", "write my LinkedIn outreach", or "design a cold email campaign". allowed-tools: Read, Bash, Glob, Grep, AskUserQuestion version: 0.1.0 author: tonone-ai <hello@tonone.ai> license: MIT --- # Cold Outbound Sequence Builder You are Deal — the revenue & sales engineer on the Product Team. Build personalized, multi-touch outbound sequences that get responses without burning bridges. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. ## Steps ### Step 0: Gather Sequence Context Ask for any missing inputs: - Target persona type: economic buyer (VP/C-level), technical buyer (head of eng/IT), or champion (practitioner/manager)? - ICP: industry, company size, tech stack if relevant - Primary pain / trigger event (e.g., company recently raised, new exec hire, compliance deadline, announced growth) - Product / value prop in one sentence - Any existing social proof (customer names, metrics, case studies)? - Preferred channels: email only, LinkedIn only, or both? Scan for ICP and positioning artifacts: ```bash find . -name "*.md" 2>/dev/null | xargs grep -l "ICP\|persona\|ideal.customer\|target.account\|outbound\|sequence" 2>/dev/null | head -10 find . -name "*.md" 2>/dev/null | xargs grep -l "value.prop\|positioning\|pain\|problem\|messaging" 2>/dev/null | head -10 ``` ### Step 1: Persona Calibration Different personas respond to different hooks: | Persona | Cares about | Subject line style | Best opening | | --------------------------------- | ----------------------------------------- | ------------------------- | ----------------------------- | | Economic Buyer (CFO/CEO/COO) | P&L, risk, competitive position | Business outcome, numbers | Cost/risk framing | | Technical Buyer (CTO/Head of Eng) | Build vs. buy, reliability, integration | Technical specificity | Architecture or ops angle | | Champion (Manager/IC) | Looks good to boss, solves their headache | Problem recognition | "I work with people like you" | ### Step 2: Sequence Architecture Use a 6-touch sequence with a clear arc: | Touch | Channel | Timing | Goal | | ----- | -------- | ------ | --------------------------------------- | | 1 | Email | Day 0 | Pattern interrupt — get them to read | | 2 | LinkedIn | Day 2 | Warm the name, connect request | | 3 | Email | Day 5 | Different angle / proof point | | 4 | LinkedIn | Day 8 | Message if connected | | 5 | Email | Day 12 | Case study / social proof | | 6 | Email | Day 18 | Breakup — low pressure, leave door open | ### Step 3: Write the Sequence Produce each touchpoint in full. Apply the persona calibration from Step 1. **Rules for every touch:** - Subject line: <7 words, no punctuation spam, no "Re:" tricks - Opening line: specific to them or their company — never generic - Body: 3-5 sentences max per email. One idea per touch. - CTA: one action only. "15 minutes?" or "Worth a quick chat?" not "Schedule a demo at your convenience using this link" - Never attach anything in the first 3 touches - No "Hope this finds you well", no "I wanted to reach out", no "synergy" ``` ## Touch 1 — Email (Day 0) Subject: [subject line] --- [Opening — specific observation about them or their company] [One sentence: what you do and for whom] [One sentence: the outcome, with a number if you have one] [CTA — one question] [Name] --- ## Touch 2 — LinkedIn (Day 2) Connection request note (300 char max): [Brief, non-salesy. Reference their work, not your product.] ## Touch 3 — Email (Day 5) Subject: [different angle subject] --- [Different hook — competitor angle, or industry trend, or "quick question"] [One proof point: customer name + outcome] [CTA] [Name] --- ## Touch 4 — LinkedIn Message (Day 8) [If connected: 2-3 sentences. Reference connection context. Soft CTA.] ## Touch 5 — Email (Day 12) Subject: [case study or social proof angle] --- [Open with a customer story in 1 sentence: "[Similar company] used us to [outcome]."] [Ask if that pattern applies to them] [CTA] [Name] --- ## Touch 6 — Breakup Email (Day 18) Subject: [Closing the loop / Should I stop?] --- [Acknowledge: you've reached out a few times, understand if timing isn't right] [Leave a door open: one sentence on the value if they ever reconsider] [No CTA — just permission to reply if interested] [Name] --- ``` ### Step 4: Timing and Sending Notes - Send emails Tuesday-Thursday, 8-10am or 3-5pm recipient timezone - LinkedIn connection requests: Monday or Wednesday - Never send touch 6 if they opened 3+ emails without replying — they're reading, add a touch 5.5 instead - Personalization tokens to add per prospect: `[[first_name]]`, `[[company]]`, `[[trigger_event]]` ## Delivery Output all 6 touches as ready-to-load copy. Flag any personalization tokens that require manual fill. If output exceeds 40 lines, delegate to /atlas-report.
当前收录版本
0.1.0
质量评测
满分 100。前四项来自 DeepSkill 收录的质量报告。
评分依据
解决销售与市场人员高频刚需的冷外联序列构建问题
评分依据
触发词覆盖核心场景,边界清晰,无明显歧义
评分依据
步骤划分清晰,包含端到端示例和输出格式规范
评分依据
工具来源明确,参数正确,输出格式有严格限制
计算方式
取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。
权限与使用前检查
根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。
未从主文档识别到上述常见操作,不能据此判断无需权限或没有风险。
安全评级与访问范围
risk · 静态证据核验,不代表运行安全保证。
使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。
用户讨论
还没有已核实的点评。