Token导航 LogoToken导航

Agent Skill · 研究检索

sales(sales 搜索)

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

sales 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 68,166。

总安装 235周安装 10GitHub Stars 167下载 82核验 2026-05-01

安装说明

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

安装方式

通过对话安装

复制提示词发给支持本地命令或 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

这个 Skill 是做什么的

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

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

当前顶部介绍为空,原始 SKILL.md 摘录未提供。sales 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/sales

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

sales 怎么安装?

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

sales 支持哪些 AI 工具?

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

sales 需要什么权限?

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

sales 是免费的吗?

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

sales 用的人多吗?

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

sales 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

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

值得选的地方

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

sales 搜索 · 本页

235167需要联网未明确有提醒

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

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

平台分布

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 复核。

安装前确认

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

继续浏览同类 Skills