Token导航 LogoToken导航

Agent Skill · 研究检索

multithread-outreach(多线程外展)

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

multithread-outreach 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 65,896。

总安装 272周安装 11GitHub Stars 30下载 85核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/salesably/salesably-marketplace --skill multithread-outreach

这个 Skill 是做什么的

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

用于查找、检索和筛选相关信息,支持批量查询和多线程处理。适合在需要并行获取大量数据或联系记录时使用。可加快信息收集速度,但需注意来源可靠性和去重机制。

安装命令:npx skills add https://github.com/salesably/salesably-marketplace --skill multithread-outreach。应评估是否涉及第三方服务调用或自动化外联行为。

来源仓库内路径:skills/multithread-outreach

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

multithread-outreach 怎么安装?

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

multithread-outreach 支持哪些 AI 工具?

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

multithread-outreach 需要什么权限?

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

multithread-outreach 是免费的吗?

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

multithread-outreach 用的人多吗?

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

multithread-outreach 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

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

值得选的地方

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

多线程外展 · 本页

27230只读未明确通过

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

SKILL.md 原文

Multithread Outreach

This skill creates tailored outreach messages for different stakeholders within an account, enabling you to engage multiple decision-makers and influencers with role-specific messaging.

Objective

Generate personalized, role-appropriate messages for various stakeholders in a deal-ensuring each person receives communication relevant to their priorities while maintaining consistent core messaging.

Why Multithreading Matters

The Problem with Single-Threading

  • Deals stall when your champion leaves or goes dark
  • You miss perspectives from key decision-makers
  • No internal advocates beyond your main contact
  • Limited visibility into the buying process

Benefits of Multithreading

  • Resilience: Deal survives if one contact goes dark
  • Speed: Multiple parallel conversations accelerate decisions
  • Intelligence: Learn about different perspectives and priorities
  • Influence: Build coalition of supporters across the org

Stakeholder Categories

Executive Sponsors (C-Level, VP)

What They Care About:

  • Business outcomes and ROI
  • Strategic alignment
  • Risk mitigation
  • Competitive advantage
  • Resource allocation

Messaging Approach:

  • Lead with business impact
  • Keep it brief and high-level
  • Quantify value when possible
  • Focus on outcomes, not features
  • Respect their time

Operational Leaders (Directors, Managers)

What They Care About:

  • Team productivity and efficiency
  • Implementation feasibility
  • Day-to-day impact
  • Change management
  • Success metrics

Messaging Approach:

  • Balance strategic and tactical
  • Address implementation concerns
  • Show understanding of their challenges
  • Include relevant details
  • Offer to support their team

Technical Buyers (IT, Security, Architecture)

What They Care About:

  • Integration requirements
  • Security and compliance
  • Technical architecture
  • Maintenance overhead
  • Vendor reliability

Messaging Approach:

  • Lead with technical credibility
  • Address integration and security early
  • Provide technical resources
  • Offer to connect with your tech team
  • Respect their expertise

End Users

What They Care About:

  • Ease of use
  • Daily workflow impact
  • Training and adoption
  • Current pain points
  • Personal productivity

Messaging Approach:

  • Focus on user experience
  • Acknowledge their pain points
  • Highlight ease of adoption
  • Show empathy for their situation
  • Offer hands-on demonstrations

Economic Buyers (Finance, Procurement)

What They Care About:

  • Total cost of ownership
  • Pricing and terms
  • Contract flexibility
  • Budget timing
  • Vendor risk

Messaging Approach:

  • Lead with value and ROI
  • Be transparent about pricing
  • Address procurement concerns
  • Highlight financial flexibility
  • Provide case study ROI data

Message Structure by Scenario

Scenario 1: Initial Introduction (Never Met)

Someone your contact suggested you reach out to.

Subject: [Contact Name] suggested we connect

Hi [Name],

[Contact Name] mentioned you'd be a good person to include
in our conversation about [initiative].

We've been discussing [brief summary] with [their team/department],
and given your role in [their area], I thought you might find
[specific aspect] relevant.

[1-2 sentences on business impact specific to their role]

Would you be open to a brief conversation, or would you prefer
I keep you updated via email as things progress?

Best,
[Your name]

Scenario 2: Post-Call Briefing (Wasn't on the Call)

Someone who should know about a conversation they weren't part of.

Subject: Update: [Company] and [Your Company] Discussion

Hi [Name],

I wanted to share a quick update from my conversation with
[their colleague] earlier this [day/week].

Key discussion points:
- [Point relevant to their role]
- [Another relevant point]
- [Outcome or next step]

Given your focus on [their area], I thought [specific aspect]
might be particularly relevant to you.

Happy to give you a brief overview if helpful-or simply keep
you in the loop as we progress. What works best?

Best,
[Your name]

Scenario 3: Champion Enablement

Helping your champion sell internally.

Subject: Materials for your internal discussion

Hi [Name],

As promised, here are some resources for your conversation with
[other stakeholders]:

For [Stakeholder 1 - role]:
- [Relevant resource/talking point]

For [Stakeholder 2 - role]:
- [Relevant resource/talking point]

I've also attached [executive summary/one-pager] that you can
share or forward as needed.

Let me know if there's anything else I can prepare to help the
conversation go smoothly.

Best,
[Your name]

Scenario 4: Executive Air Cover

Reaching up to get executive support.

Subject: [Specific business outcome] at [Company]

Hi [Name],

[Their company] has been evaluating [your solution category]
to address [business challenge]. Your team has identified
[specific opportunity or risk].

Based on similar situations with [comparable company], we've
seen [quantified result] through [your approach].

I've been working with [their direct report] on the details-
happy to provide an executive briefing if helpful as this
moves toward a decision.

Would a brief call be worthwhile?

Best,
[Your name]

Messaging Guidelines

Consistency Across Stakeholders

  • Core value proposition stays the same
  • Key facts and claims are consistent
  • Pricing/timeline aligned
  • No conflicting information

Role-Specific Customization

  • Lead with what matters to them
  • Use appropriate level of detail
  • Match formality to their role
  • Reference relevant benefits

Coordination Rules

  • Don't contradict what you told others
  • Reference connections appropriately
  • Time outreach thoughtfully
  • Share relevant intel with your champion

What to Avoid

  • Exact same message to multiple people (they'll compare)
  • Going over your contact's head without warning
  • Inconsistent information across stakeholders
  • Pushy or aggressive outreach to executives

Email Length Guidelines

Stakeholder TypeTarget Length
Executives75-125 words
Operational Leaders150-250 words
Technical Buyers150-300 words
End Users100-175 words
Economic Buyers125-200 words

Output Format

When creating multithread messages, produce:

For Each Stakeholder:

  1. Name & Role: Who this is for
  2. Priority Level: How important to engage them
  3. Message Type: Which scenario applies
  4. Subject Line: Specific, relevant subject
  5. Full Message: Complete email in appropriate tone/length
  6. Timing Suggestion: When to send relative to other outreach
  7. Coordination Notes: What to tell your champion

Overall Strategy:

  • Outreach Sequence: Order of who to contact
  • Message Themes: How messaging varies by role
  • Risk Notes: Potential concerns with the approach

Cross-References

  • Use prospect-research for stakeholder intelligence
  • Apply company-intelligence for organization context
  • Reference call-analysis for conversation-specific follow-ups
  • Inform powerful-framework with new stakeholder insights
  • Coordinate with follow-up-emails for primary contact

平台分布

Codex

37.54%
按下载量换算32

Claude

27.17%
按下载量换算23

Cursor

17.04%
按下载量换算14

Gemini CLI

8.4%
按下载量换算7

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills