Token导航 LogoToken导航

Agent Skill · 研究检索

sales-groove(销售槽)

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

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

总安装 1,109周安装 51GitHub Stars 13下载 420核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

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

这个 Skill 是做什么的

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

sales-groove 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。适用于需要根据关键词或任务场景进行信息检索的场景,如市场调研或竞品分析。通过关键词、来源仓库或任务线索调用,结合原始 README 可进一步核验具体用法。

安装命令为 npx skills add https://github.com/sales-skills/sales --skill sales-groove。使用前需确认权限范围、维护状态,以及是否涉及联网、命令执行或文件读写操作。

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

sales-groove 怎么安装?

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

sales-groove 支持哪些 AI 工具?

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

sales-groove 需要什么权限?

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

sales-groove 是免费的吗?

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

sales-groove 用的人多吗?

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

sales-groove 安全吗?

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

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

值得选的地方

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

销售槽 · 本页

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

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

SKILL.md 原文

Groove.cm Platform Help

Help the user with Groove.cm platform questions — all-in-one business platform covering websites, funnels, email marketing, e-commerce, membership sites, affiliate programs, webinars, video hosting, and blogging.

Step 1 — Gather context

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

Ask the user:

  1. Which Groove module do you need help with?

- A) GroovePages — websites and landing pages - B) GrooveFunnels — sales funnels with upsells/downsells - C) GrooveSell — product sales, checkout, payments - D) GrooveMail — email marketing, automation, broadcasts - E) GrooveAffiliate — affiliate program management - F) GrooveMember — membership sites and courses - G) GrooveVideo — video hosting - H) GrooveWebinar — live and automated webinars - I) GrooveBlog — blogging - J) GrooveKart/Store — e-commerce - K) GrooveProof — social proof notifications - L) Integrations — Zapier, webhooks, third-party tools - M) Other — describe it

  1. What's your role?

- A) Solopreneur / creator - B) Course creator / coach - C) Agency running Groove for clients - D) E-commerce seller - E) Affiliate marketer - F) Other

  1. What are you trying to accomplish?

- A) Setting up from scratch - B) Migrating from another platform - C) Optimizing an existing setup - D) Troubleshooting a specific issue - E) Connecting Groove to other tools

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.

Step 2 — Route or answer directly

If the user's question is better served by a specialized skill, route them:

Question typeHand off
Funnel strategy, conversion optimization, funnel structure"This is a funnel strategy question — run: /sales-funnel {your question}"
Email marketing strategy, nurture sequences, broadcast planning"This is an email marketing strategy question — run: /sales-email-marketing {your question}"
Affiliate program design, commission structures, recruitment"This is a affiliate program question — run: /sales-affiliate-program {your question}"
Webinar selling strategy, presentation structure, follow-up"This is a webinar strategy question — run: /sales-webinar {your question}"
Membership/course design, pricing, retention"This is a membership strategy question — run: /sales-membership {your question}"
Checkout optimization, upsell strategy, pricing psychology"This is a checkout optimization question — run: /sales-checkout {your question}"
Connecting Groove to CRM, Zapier workflows, webhooks"This is a tool integration question — run: /sales-integration {your question}"

If the question is Groove-specific (how to configure a module, platform limitations, Groove-specific terminology), answer directly.

Step 3 — Groove.cm 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

When helping the user, follow this pattern:

  1. Identify the specific module and task — don't give generic advice when they need step-by-step clicks
  2. Reference the correct navigation path — e.g., "GrooveSell > Products > Add Product > Pricing tab"
  3. Warn about plan limitations — many features are gated by plan tier. Check what plan the user is on before recommending features.
  4. Cross-module workflows — Groove's power is in the native integrations. Always suggest connected workflows (e.g., "Set up the GrooveSell product first, then GrooveMember will auto-create the access level, and GrooveMail can trigger a welcome sequence on purchase").
  5. Verify the setup — suggest testing steps (test purchase, test email, test funnel flow)

Gotchas

*Best-effort from research — review these, especially items about plan-gated features and integration gotchas that may be outdated.*
  • Pricing is extremely volatile. Groove.cm runs aggressive limited-time promotions ($1/year, lifetime deals) that change frequently. Never state current pricing as fact — always add "as of {date} — verify current pricing at groove.cm/pricing." Users may be on wildly different pricing depending on when they signed up.
  • No public API. Claude may be tempted to suggest API integrations, but Groove.cm has no comprehensive public REST API. The only programmatic options are GrooveSell webhooks (4 events) and Zapier. Don't invent API endpoints.
  • Free plan has real limitations. The free tier limits contacts (500), email sends (1,000–15,000/mo), pages (25), and domains (1). Don't recommend workflows that exceed free plan limits without checking the user's plan.
  • GrooveMail is opt-in email marketing, not cold outbound. Don't confuse GrooveMail with cold email tools like Mailshake or Lemlist. GrooveMail is for emailing subscribers who opted in. Using it for cold outbound will tank deliverability and violate terms.
  • Module names changed over time. Groove.cm was originally "GrooveFunnels" and module names have shifted (GrooveKart → GrooveStore, etc.). Users may reference old names. Map them to current names.
  • Self-improving: If you discover something not covered here, append it to references/learnings.md with today's date.

Step 5 — Related skills

  • /sales-funnel — Funnel strategy, structure, and optimization (tool-agnostic)
  • /sales-email-marketing — Email marketing strategy for opt-in lists (tool-agnostic)
  • /sales-affiliate-program — Affiliate program design and management (tool-agnostic)
  • /sales-webinar — Webinar-based selling strategy (tool-agnostic)
  • /sales-membership — Membership site and course delivery strategy (tool-agnostic)
  • /sales-checkout — Checkout optimization, upsells, and order bumps (tool-agnostic)
  • /sales-integration — Connect Groove to CRM and other tools via Zapier/webhooks
  • /sales-do — Not sure which skill to use? The router matches any sales objective to the right skill.

Examples

Example 1: Set up a course with payment

User says: "I want to sell an online course in Groove. How do I set it up?" Skill does:

  1. Walks through GrooveSell product creation (digital product, pricing)
  2. Connects to GrooveMember for course content delivery
  3. Sets up GrooveMail welcome sequence triggered on purchase
  4. Configures GrooveAffiliate so affiliates can promote the course
  5. Suggests testing with a $1 test purchase Result: Complete course sales pipeline with payment, delivery, email follow-up, and affiliate tracking

Example 2: Migrate from ClickFunnels

User says: "I'm moving from ClickFunnels to Groove. What's the process?" Skill does:

  1. Maps ClickFunnels concepts to Groove equivalents (funnels → GrooveFunnels, email → GrooveMail, membership → GrooveMember)
  2. Outlines migration order: pages first, then products, then email lists, then automations
  3. Warns about what doesn't transfer (automation rules, email history)
  4. Suggests running both platforms in parallel during transition Result: Step-by-step migration plan with risk mitigation

Example 3: Set up GrooveSell webhooks for external CRM

User says: "I need to send Groove sales data to my HubSpot CRM" Skill does:

  1. Notes no native Groove→HubSpot integration
  2. Recommends Zapier: GrooveSell "New Sale" trigger → HubSpot "Create Contact" + "Create Deal" actions
  3. Provides field mapping guidance
  4. Also mentions GrooveSell webhook option for custom integration
  5. Routes to /sales-integration for advanced webhook setup Result: Zapier workflow connecting Groove sales to HubSpot with field mapping

Troubleshooting

GrooveMail emails going to spam

Symptom: Subscribers report not receiving emails or finding them in spam Cause: Domain not authenticated, sending too fast on a new account, or content triggering spam filters Solution: Verify custom sending domain with SPF/DKIM/DMARC. Start with small sends and gradually increase volume. Use Groove's built-in spam checker before sending. Avoid spam trigger words in subject lines. Check sender reputation at mail-tester.com.

GrooveSell checkout not processing payments

Symptom: Customers see errors on checkout or payments don't go through Cause: Payment processor not connected, SSL issue on custom domain, or product pricing misconfigured Solution: Verify payment processor connection in GrooveSell > Settings > Payment Integrations. Test with a small purchase. Check that custom domain has SSL enabled. Verify product pricing and currency settings match the payment processor's configuration.

GrooveMember content not unlocking after purchase

Symptom: Customer purchases a course but can't access the content in GrooveMember Cause: Product not linked to membership access level, or automation delay Solution: Check GrooveSell product settings > Fulfillment tab — ensure it's linked to the correct GrooveMember product and access level. Verify the customer's email matches in both GrooveSell and GrooveMember. Check for automation delays (enrollment may take a few minutes).

平台分布

Codex

40.22%
按下载量换算169

Claude

27.34%
按下载量换算115

Cursor

18.59%
按下载量换算78

Gemini CLI

9.81%
按下载量换算41

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

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

安装前确认

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

继续浏览同类 Skills