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

outreach-and-prospecting外展和勘探

Agent Skill

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

总安装

824

周安装

34

GitHub Stars

7

下载量

269
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/jk-0001/skills --skill outreach-and-prospecting

简介

outreach-and-prospecting 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词快速定位候选结果。

  • 适用于客户拓展、合作伙伴发现和潜在客户挖掘等场景。
  • 支持基于任务线索进行定向信息聚合与筛选。
  • 安装前建议确认权限范围、维护状态及是否触发联网或文件读写。
  • 可结合原始 README 和仓库路径进一步验证具体功能和使用方法。

SKILL.md

Outreach and Prospecting

Overview

Outbound outreach is one of the most powerful but most abused channels. Done well, it surfaces high-value opportunities that inbound alone will never find. Done poorly, it damages your reputation. This playbook gives you a repeatable system: who to target, how to find them, what to say, and how to follow up — all tuned for a solopreneur doing this alongside everything else.


Step 1: Define Your Ideal Customer Profile (ICP)

Before reaching out to anyone, know exactly who you're looking for. A vague ICP = wasted outreach on the wrong people.

ICP template:

COMPANY / PERSON PROFILE:
  Industry:           [specific — not "tech"]
  Company size:       [e.g., 10-50 employees] (if B2B)
  Job title / role:   [the person who feels the pain AND has budget authority]
  Location:           [if relevant]
  Revenue range:      [if B2B — indicates budget capacity]

PAIN SIGNALS (how to know they need you):
  - [Observable behavior that indicates they have the problem]
  - [Tool they currently use that you can improve upon]
  - [Content they publish or engage with that reveals the pain]
  - [Life event or business event that triggers the need]

DISQUALIFIERS (do not reach out if):
  - [Signal that means they're not a good fit — saves time]
  - [Signal that means they can't afford you]
  - [Signal that means they already have a perfect solution]

Step 2: Find and Qualify Leads

Lead sources (ranked by quality for solopreneurs):

  1. Warm introductions — Someone you know introduces you to someone who needs you. Highest conversion. Ask your network regularly: "Do you know anyone dealing with [specific problem]?"
  2. LinkedIn Sales Navigator or free search — Filter by job title, industry, company size. Check their profile for pain signals.
  3. Job postings — Companies hiring for roles related to your problem space often have the pain you solve. The job posting itself is your conversation starter.
  4. Content engagement — People who comment on or share content about your problem. They're signaling the pain publicly.
  5. Tool review sites — People leaving negative reviews on competitor tools are actively frustrated and open to alternatives.
  6. Reddit / forum posts — People asking questions related to your problem. If the thread is old, they may have solved it — if recent, they haven't.
  7. Newly funded companies — Crunchbase alerts for funding in your industry. Funded companies have budget and growth pressure.
  8. Newly registered domains / new companies — Tools like Instantly or Apollo can surface these. New businesses need everything.

Qualification checklist — only outreach leads that pass ALL of these:

  • They have the specific pain you solve (evidence, not assumption)
  • They have budget (company size, funding, or individual income indicates ability to pay)
  • They are reachable (you can find a way to contact them)
  • They are the right person (decision-maker or influencer, not someone with no authority)

Step 3: Write Cold Emails That Get Replies

Most cold emails fail because they're about the sender. Flip it: make every sentence about the recipient.

The anatomy of a cold email that works:

SUBJECT LINE: Specific, curious, not salesy.
              Avoid: "Quick question", "Synergy opportunity", "Intro"
              Good: "[Specific observation about them]", "Saw your [thing] — thought of something"

LINE 1 (the hook):
  Show you did research. Reference something specific about THEM.
  "I noticed you just hired 3 new sales reps at [Company]."
  "Your blog post on [topic] mentioned [specific challenge]."
  This proves you're not mass-blasting.

LINES 2-3 (the bridge):
  Connect their specific situation to a problem you solve.
  "That usually means [specific pain that comes with their situation]."
  One sentence. Don't over-explain.

LINE 4 (the value):
  State what you do in terms of THEIR outcome. Not your features.
  "I help [company type] [achieve specific result] in [timeframe]."
  One sentence.

LINE 5 (the ask):
  Make it tiny. Low commitment. Easy to say yes to.
  NOT: "Can we hop on a 30-min call this week?"
  YES: "Would it be worth a quick 10-min chat if this is relevant?"
  YES: "Want me to send over a quick example of how I did this for [similar company]?"

SIGN-OFF:
  First name only. No title. No company logo. Keep it human.

Subject line formulas that work:

  • [Specific observation about their business]
  • [Their competitor] is doing [X] — are you?
  • Question about [specific thing on their site/profile]
  • [Mutual connection] suggested I reach out

Length rule: Under 100 words in the body. If you can't make your case in 5 sentences, you haven't distilled it enough.


Step 4: LinkedIn Outreach (Same Principles, Different Format)

LinkedIn messages get higher open rates than email but have stricter formatting constraints.

Connection request message (if not already connected):

  • 1-2 sentences max. Specific. Not "I'd love to connect."
  • "Saw your comment on [post] about [topic] — had a relevant thought. Mind connecting?"

After connection is accepted — the message:

  • Same structure as cold email but even shorter (3-4 sentences max).
  • Reference WHY you connected (the specific thing that triggered it).
  • End with a low-commitment ask.

LinkedIn outreach mistakes:

  • Sending a pitch immediately after connection. Wait. Send a value-first message first (share something useful, no ask).
  • Writing long paragraphs. LinkedIn messages get skimmed. Short wins.
  • Using templates so obviously that they feel automated. Personalization is the entire point.

Step 5: Build a Multi-Touch Sequence

One message rarely converts. Build a sequence of 3-5 touchpoints across different channels over 2-3 weeks.

Example sequence:

Day 1:   LinkedIn connection request (with personalized note)
Day 3:   LinkedIn message (value-first, no ask)
Day 5:   Cold email (the main pitch — references the LinkedIn interaction)
Day 10:  LinkedIn comment on one of their posts (genuine, helpful comment)
Day 14:  Follow-up email ("Just wanted to bump this — still relevant?")
Day 21:  Final email ("Last note from me — if the timing isn't right,
          totally understand. Happy to reconnect later.")

Rules:

  • Never more than one touchpoint per channel per week.
  • Each touchpoint adds something new — a different angle, a new piece of value, a different case study. Don't just repeat the same message.
  • The final touchpoint gives them a clean exit. No guilt, no pressure. This protects your reputation.

Step 6: Track and Manage Your Pipeline

Outreach without tracking is guesswork. Use a simple system (spreadsheet or CRM):

COLUMNS:
  Lead Name | Company | Source | Date First Contacted |
  Last Touchpoint | Stage | Notes | Next Action | Next Action Date

STAGES:
  Identified → Contacted → Replied → In Conversation → Proposal Sent →
  Closed Won → Closed Lost → Not Now (re-nurture later)

Pipeline hygiene rules:

  • Review your pipeline weekly (10 min). Move leads between stages. Delete dead ones (no response after full sequence = done).
  • "Not Now" is not "No forever." Flag these for re-contact in 3-6 months. Timing matters — a lead that said no in January might say yes in June.
  • Track your conversion rates at each stage. If "Contacted → Replied" is very low, your messaging needs work. If "In Conversation → Proposal Sent" is low, your discovery process needs work.

Step 7: Outreach Volume and Time Management

As a solopreneur, you can't prospect full-time. Time-box it.

Recommended cadence:

  • Daily (20 min): Research and qualify 3-5 new leads. Add to pipeline.
  • Daily (15 min): Send or follow up on 3-5 touchpoints.
  • Weekly (30 min): Pipeline review. Update stages. Plan next week's outreach.

Volume targets:

  • 3-5 new leads entering the pipeline per day
  • 15-25 active leads in your pipeline at any time
  • 1-3 discovery calls per week (depending on your capacity)

If outreach is taking more than 45 min/day, you're spending too much time on research. Use better tools or tighter ICP criteria to reduce the search time.


Outreach Mistakes to Avoid

  • Blasting the same template to 500 people. Personalization is not optional — it is the entire strategy.
  • Giving up after one message. Most replies come on touchpoints 3-5, not 1.
  • Pitching immediately. Lead with value or curiosity. Earn the right to pitch.
  • Ignoring "not now" responses. These are warm leads for the future. nurture them.
  • Not following up on replies fast enough. If someone replies, respond within the same day. Speed signals professionalism and interest.

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

36.33%
按下载量换算98

Claude

29.02%
按下载量换算78

Cursor

18.98%
按下载量换算51

Gemini CLI

8.85%
按下载量换算24

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

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

安装前确认

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

来源信息

继续浏览同类 Skills