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

salessales 搜索

Agent Skill

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

总安装

235

周安装

10

GitHub Stars

167

下载量

82
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/whawkinsiv/claude-code-skills --skill sales

简介

sales 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。

  • 可结合来源仓库、安装命令和原始 README 继续核验具体用法。
  • 安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。
  • 当前顶部介绍为空,原始 SKILL.md 摘录未提供。
  • sales 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Founder-Led Sales & Outreach

Your first 100 customers won't come from inbound. You have to go get them. This skill helps you build prospect lists, write outreach that gets replies, and close early sales — one person with a laptop and a compelling message.

If ABOUT-ME.md and/or MY-ICP.md exist in the project root, read them before writing outreach. Lead with founder credibility from ABOUT-ME.md (Domain Expertise, Key Stories). Frame the message around ICP pain from MY-ICP.md (Their Pain, Their Language). If the founder has a strong network (ABOUT-ME.md Network & Distribution), prioritize warm channels over cold outreach.

Core Principles

  • Your first 100 customers won't come from inbound. You have to go get them.
  • Outreach that leads with "I built a thing" fails. Outreach that leads with "I noticed you have this problem" converts.
  • Volume matters, but relevance matters more. 10 personalized messages beat 100 generic ones.
  • Every reply — even a rejection — is data. Objections are product requirements in disguise.
  • Founder-led sales is temporary. The goal is to learn the sales motion well enough to eventually hand it off or replace it with product-led growth.
  • Consistency beats intensity. 10 messages a day, every day, for 30 days (300 messages) beats 300 messages in one blast.

Building a Prospect List

Where to Find Prospects

LinkedIn (best for B2B SaaS):

  • Search by job title + industry + company size matching your ICP.
  • Look at who follows your competitors.
  • Check who's posting about the problem you solve.
  • Groups related to your problem space.

Communities:

  • Reddit: Search subreddits where your ICP hangs out. Look at who's asking questions your product answers.
  • Indie Hackers, Hacker News: People building things often need tools.
  • Slack/Discord communities in your niche.
  • Facebook Groups (surprisingly active for many B2B niches).

Review sites:

  • G2, Capterra: Look at who's reviewing competitor products — especially negative reviewers.
  • Product Hunt: People who upvoted similar products.

Job boards:

  • Companies hiring for roles that your product makes easier are actively feeling the pain.
  • "Hiring a data analyst" = might need a better analytics tool.

Existing networks:

  • Your own LinkedIn connections who match the ICP.
  • Former colleagues, industry contacts.
  • Alumni networks.

Prospect List Structure

Build a spreadsheet:

| Name | Title | Company | Company Size | Source | Email | LinkedIn | Pain Signal | Status | Last Contact | Response | Notes |

Pain signal is the most important column. It's the specific reason you believe THIS person has the problem you solve:

  • "Posted on Reddit about struggling with X"
  • "Left 2-star review of [Competitor] complaining about Y"
  • "Hiring for a role that your product automates"
  • "Company just raised Series A (scaling pain incoming)"
  • "Commented on a LinkedIn post about the problem"

Finding Email Addresses

  • Hunter.io: Find emails by domain.
  • Apollo.io: Search + email + sequencing in one tool.
  • LinkedIn connection + direct message (no email needed).
  • Company website: Check /about, /team, or /contact pages.
  • Pattern guessing: Most companies use firstname@domain.com or first.last@domain.com. Verify with Hunter or NeverBounce.

Minimum viable list: 100 prospects before you start sending.

Writing Problem-First Messages

The Structure

[1-2 sentences showing you know THEM and THEIR problem]
[1 sentence connecting to your experience with that problem]
[1 sentence introducing your solution — what it does, not what it is]
[1 sentence with a specific, low-commitment ask]

Template

Subject: [Specific to their situation — NOT your product name]

Hi [First name],

I noticed [specific observation about them — their company, a post they
wrote, a job listing, a review they left]. [One sentence about why that
caught your attention, connecting it to a problem you understand.]

I ran into the same issue when I was [your relevant experience]. That's
why I built [Product] — it [one sentence on the specific outcome, not
features].

[Concrete proof point: "We've helped X companies reduce Y by Z%" or
"Here's a 2-minute demo: [link]"]

Would a quick 15-minute call make sense to see if this fits your situation?

[Your name]
[Product — one-line description]

Message Examples by Channel

Cold email:

Subject: re: your [specific pain signal]

Hi Sarah,

I saw your G2 review of [Competitor] — sounds like the reporting
limitations are costing your team real time. I heard the same thing
from 3 other marketing ops leads this month.

I built [Product] specifically to solve that gap — it [specific
outcome]. [Company X] cut their reporting time from 4 hours to 20
minutes.

Worth a 15-minute look? I can show you exactly how it'd work for
your setup.

— [Name]

LinkedIn DM:

Hi [Name] — I noticed you're leading [function] at [Company].
Curious: are you still using [current tool/process] for [task]?
I've been building something specifically for teams your size
and would love your take. No pitch — genuinely looking for feedback
from people doing this work daily.

Community reply (Reddit, HN, Discord):

I dealt with exactly this. [Share your genuine experience with the
problem — 2-3 sentences of value.] I actually ended up building a
tool to fix it for myself: [link]. Happy to answer questions if
you're exploring options.

What NOT to Do

  • Don't lead with your product name, features, or company story.
  • Don't send the same message to 500 people. Personalize at least the first two sentences.
  • Don't use fake urgency ("Limited spots!") — you're a solo founder, not a used car lot.
  • Don't write more than 150 words. Respect their time.
  • Don't ask for a 30-minute call. Ask for 15. (You can always go longer if it's going well.)
  • Don't follow up more than 3 times. Sequence: Initial → +3 days → +5 days → stop.

Tracking & Follow-Up System

Daily Routine

Morning (30-45 minutes):
  1. Send 10 new outreach messages (personalized).
  2. Send follow-ups to previous messages (per sequence rules).
  3. Reply to any responses from yesterday.
  4. Log everything in your spreadsheet.

End of week (15 minutes):
  1. Review response rate: Target 10-20% reply rate.
  2. Review objections: What are people saying?
  3. Refine message based on what's working.

Follow-Up Sequence

Day 0:  Initial message (the full problem-first message)
Day 3:  Follow-up #1 — Short, add new value
        "Hi [Name], following up on my note about [problem].
         I just published [relevant resource] that might be useful
         regardless — [link]. Still happy to chat if it makes sense."
Day 8:  Follow-up #2 — Even shorter, different angle
        "Hi [Name], one more thought — [different proof point or
         angle]. If the timing isn't right, no worries at all."
Day 15: Follow-up #3 (final) — Breakup email
        "Hi [Name], I'll assume this isn't a fit right now.
         If [problem] comes back up, I'm at [email]. Good luck
         with [something specific about their work]."

Response Handling

Positive reply ("Sure, let's chat"):

  • Respond within 2 hours. Send a Calendly link or propose 2-3 specific times.
  • Before the call: Research their company, prepare 3 specific questions about their workflow.
  • On the call: Listen 70%, talk 30%. Ask about their current process, not about your product.

Objection reply:

  • Log the objection verbatim.
  • Respond with empathy, not defense.
  • "Totally fair — [acknowledge objection]. Out of curiosity, what are you using now for [task]?"
  • Every objection at 3+ frequency becomes a product or marketing priority.

No reply (most common):

  • Follow the sequence. Don't take it personally.
  • If reply rate < 5% after 50+ messages: your targeting or message is off. Fix before sending more.

Directory Submission as Outreach

Apply the same systematic approach:

| Directory | URL | Category | Submitted | Status | Backlink? | Traffic? |

Batch this work: dedicate 2-3 focused sessions to submit to 100+ directories. Write 3 variations of your product description (short, medium, long) and reuse across submissions.

Priority directories: Product Hunt, BetaList, DevHunt, Uneed, MicroLaunch, AlternativeTo, SaaSHub, GetApp, G2 (free listing), Capterra (free listing).

Metrics to Track

Weekly outreach metrics:
  Messages sent:        ___
  Reply rate:           ___%  (target: 10-20%)
  Positive reply rate:  ___%  (target: 3-8%)
  Calls booked:         ___
  Demos given:          ___
  Conversions:          ___

Objection frequency:
  [Objection 1]:  ___ times
  [Objection 2]:  ___ times
  [Objection 3]:  ___ times

Related Skills

  • niche-advantage — If you're selling to your own industry, use warm channels instead of cold outreach
  • validate — Validate demand before investing in outreach
  • customer-research — Understand your ICP before reaching out
  • email — Automated email sequences for nurturing leads
  • copywriting — Write stronger outreach messages
  • content — Build-in-public as an alternative to cold outreach

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

35.84%
按下载量换算29

Claude

27.66%
按下载量换算23

Cursor

17.45%
按下载量换算14

Gemini CLI

9.51%
按下载量换算8

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

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

安装前确认

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

来源信息

继续浏览同类 Skills