Token导航 LogoToken导航

Agent Skill · 研究检索

sales-woodpecker(销售啄木鸟)

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

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

总安装 1,148周安装 46GitHub Stars 13下载 372核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/sales-skills/sales --skill sales-woodpecker

这个 Skill 是做什么的

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

sales-woodpecker 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。适用于销售啄木鸟相关的信息调研、线索筛选和目标客户分析等研究检索任务。

通过 npx skills add 命令从指定 GitHub 仓库安装,需结合原始 README 核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写操作。可结合来源仓库路径 skills/sales-woodpecker 继续核验功能细节和使用边界。

来源仓库内路径:skills/sales-woodpecker

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

sales-woodpecker 怎么安装?

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

sales-woodpecker 支持哪些 AI 工具?

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

sales-woodpecker 需要什么权限?

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

sales-woodpecker 是免费的吗?

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

sales-woodpecker 用的人多吗?

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

sales-woodpecker 安全吗?

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

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

值得选的地方

  • 同时适配 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-woodpecker

销售啄木鸟 · 本页

1,14813需要联网未明确通过

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

SKILL.md 原文

Woodpecker.co Platform Help

Help the user with Woodpecker.co platform questions — from cold email campaign setup and condition-based sequences through deliverability tools, warmup, inbox rotation, LinkedIn automation, Lead Finder, agency panel, API, and integrations.

Step 1 — Gather context

If references/learnings.md exists, read it first for accumulated knowledge.

Ask the user:

  1. What area of Woodpecker do you need help with?

- A) Campaigns — creating condition-based sequences, A/B testing, follow-ups - B) Deliverability — Bounce Shield, Adaptive Sending, ESP Matching, domain audit, spam checker - C) Warmup — built-in email warmup powered by Mailivery - D) Agency panel — multi-client management, per-client isolation - E) Integrations / API — connecting to CRMs, webhooks, API automation - F) Lead Finder — B2B lead database, data credits - G) Inbox — centralized inbox, reply management, auto-categorization - H) LinkedIn automation — automated connection requests, messages, multichannel sequences - I) Something else — describe it

  1. What's your role?

- A) Admin / account owner - B) Sales rep / BDR / AE - C) Agency owner / account manager - D) Other

  1. What are you trying to accomplish? (describe your specific goal or question)

If the user's request already provides most of this context, skip directly to the relevant step. Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end — don't gate your response behind gathering complete context.

Note: If the user needs a specialized skill, route them there with a brief explanation of why that skill is a better fit.

Step 2 — Route or answer directly

If the request maps to a specialized skill, route:

  • Outbound cadence strategy / sequence design -> /sales-cadence
  • Cross-platform email deliverability -> /sales-deliverability
  • Email tracking strategy -> /sales-email-tracking
  • Building prospect lists -> /sales-prospect-list
  • Connecting Woodpecker to other tools via Zapier or middleware -> /sales-integration
  • Multi-client agency architecture (platform-agnostic) -> /sales-agency-outbound

Otherwise, answer directly from platform knowledge using the reference below.

Step 3 — Woodpecker platform reference

Read references/platform-guide.md for detailed module documentation, pricing, integrations, and data model.

*You no longer need the platform guide details — focus on the user's specific situation.*

Step 4 — Actionable guidance

Based on the user's specific question:

  1. Recommended setup order for new accounts:

1. Connect mailbox(es) (Gmail, Outlook, or SMTP) 2. Enable warmup on all connected mailboxes 3. Wait 2+ weeks for warmup to build reputation 4. Set up domain authentication (SPF, DKIM, DMARC) — use Woodpecker's domain audit to verify 5. Create your first campaign with condition-based steps 6. Add prospects (manually, CSV, Lead Finder, or API) 7. Run spam checker on your email copy 8. Launch campaign

  1. Configuration recommendations:

- Enable Bounce Shield on all campaigns — there is no reason to skip it - Enable Adaptive Sending to let Woodpecker auto-throttle based on engagement - Set daily per-mailbox limits conservatively (30-50 for cold outbound) - Use inbox rotation with 3+ mailboxes to distribute volume - A/B test subject lines first, then body copy — test one variable at a time

  1. For API questions: Always include a pointer — "For the full endpoint catalog, request/response schemas, and rate limits, see references/woodpecker-api-reference.md."

Gotchas

Best-effort from research — verify details against current Woodpecker documentation.
  1. API access is a paid add-on (EUR 20/mo) — not included in base plans. Many users expect API access by default, but you need the API & integrations add-on or an active trial to use the API at all.
  2. LinkedIn automation is a separate add-on (EUR 29/LinkedIn account) — not included in any plan tier. Each LinkedIn account you want to automate costs extra on top of your base plan.
  3. Woodpecker prices by "contacted prospects" not by user/seat — every new person added to a campaign counts against your monthly limit, even if they don't receive all steps. Recontacting the same prospect in a different campaign counts again.
  4. The agency panel is per active client (EUR 27/client/mo) — costs scale linearly with client count. Compare with Smartlead's flat agency pricing if managing many clients.
  5. Woodpecker's API has a strict 1-concurrent-request limit with a queue of only 6 — high-volume API integrations need careful throttling and retry logic. Requests beyond 6 queued return HTTP 429 immediately (15-second timeout per queued request).
  • Self-improving: If you discover something not covered here, append it to references/learnings.md with today's date.

Step 5 — Related skills

  • /sales-cadence — Design outbound cadence strategy (platform-agnostic, works with Woodpecker campaigns)
  • /sales-deliverability — Cross-platform email deliverability — SPF/DKIM/DMARC, warmup, inbox placement
  • /sales-email-tracking — Email tracking strategy — open/click tracking, engagement signals
  • /sales-prospect-list — Build prospect lists to import into Woodpecker
  • /sales-integration — Connect Woodpecker to other tools via webhooks, Zapier, or API
  • /sales-agency-outbound — Multi-client agency architecture — infrastructure, client isolation, onboarding
  • /sales-enrich — Enrich contacts with emails/phones before importing into Woodpecker
  • /sales-smartlead — Smartlead platform help (if evaluating alternatives to Woodpecker)
  • /sales-lemlist — Lemlist platform help (if evaluating alternatives to Woodpecker)
  • /sales-do — Not sure which skill to use? The router matches any sales objective to the right skill. Install with /install-skill sales-do if you don't have it.

Examples

Example 1: Basic campaign setup with A/B testing

User says: "How do I set up a cold email campaign in Woodpecker with A/B testing and follow-ups?" Skill does:

  1. Walks through creating a new campaign with condition-based steps
  2. Explains adding up to 16 steps with delays between them — initial email plus follow-ups
  3. Shows how to create A/B test variants (up to 5 per step) for subject lines and body copy
  4. Configures auto-stop on reply so prospects exit the sequence when they respond
  5. Recommends connecting 3+ mailboxes with inbox rotation for volume distribution Result: User has a multi-step campaign with A/B testing, follow-ups, and proper mailbox rotation configured

Example 2: Deliverability audit

User says: "My Woodpecker emails are going to spam. How do I fix deliverability?" Skill does:

  1. Runs through Woodpecker's domain audit — checks SPF, DKIM, DMARC with fix suggestions
  2. Verifies warmup status on all connected mailboxes — must be running 2+ weeks with healthy reputation
  3. Enables Bounce Shield and Adaptive Sending if not already active
  4. Uses spam checker to audit email copy for spammy words, broken links, and authentication issues
  5. Recommends deliverability monitor for ongoing inbox placement tracking Result: User has a complete deliverability diagnosis with specific fixes and ongoing monitoring

Example 3: Agency panel configuration

User says: "I run an agency and need to manage 10 clients in Woodpecker" Skill does:

  1. Explains the agency panel add-on pricing (EUR 27/active client/mo = EUR 270/mo for 10 clients)
  2. Walks through setting up per-client isolation — separate campaigns, prospects, and mailboxes
  3. Shows the Agency API authentication pattern: HQ key + x-company-id header
  4. Configures per-company API keys for any clients needing their own API access
  5. Sets up a single-dashboard workflow for monitoring all 10 clients Result: User has 10 isolated client workspaces with API access and centralized management

Troubleshooting

Emails going to spam

Symptom: Prospects report finding emails in spam, or reply rates are near zero despite high send volume Cause: Missing or misconfigured domain authentication (SPF/DKIM/DMARC), insufficient warmup, spammy content, or sender reputation damage Solution: Run Woodpecker's domain audit to check SPF/DKIM/DMARC — fix any issues flagged. Verify warmup has been running 2+ weeks on all mailboxes. Use the spam checker to audit email copy. Enable Bounce Shield and Adaptive Sending. If reputation is damaged, pause campaigns, run warmup-only for 2-3 weeks, then relaunch with lower volume. See /sales-deliverability for a comprehensive diagnosis framework.

Low open rates

Symptom: Campaign open rates below 30% Cause: Poor subject lines, bad send times, inbox placement issues, or stale prospect data Solution: A/B test subject lines (use all 5 variant slots). Check deliverability — low opens often mean emails are landing in spam, not that prospects are ignoring them. Verify prospect emails with Woodpecker's built-in verification to remove invalid addresses. Test different send times and days. Use Adaptive Sending to let Woodpecker optimize send timing. If open rates are low across all variants, the issue is likely deliverability, not content.

API 429 errors

Symptom: Frequent HTTP 429 (Too Many Requests) responses from the Woodpecker API Cause: Exceeding the 1-concurrent-request limit or overflowing the 6-request queue Solution: Woodpecker allows only 1 request at a time with a queue of 6 (15-second timeout per queued request). Implement strict request serialization — never send concurrent requests. Add retry logic with exponential backoff starting at 15 seconds. For bulk operations, batch where possible and process sequentially. If you need higher throughput, contact developers@woodpecker.co about rate limit increases. See references/woodpecker-api-reference.md for full rate limit details.

平台分布

Codex

39.99%
按下载量换算149

Claude

27.36%
按下载量换算102

Cursor

17.73%
按下载量换算66

Gemini CLI

10.19%
按下载量换算38

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

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

安装前确认

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

继续浏览同类 Skills