Token导航 LogoToken导航

Agent Skill · 研究检索

sales-and-revenue-operations(销售和收入运营)

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

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

总安装 3,491周安装 144GitHub Stars 42下载 1,140核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/manojbajaj95/claude-gtm-plugin --skill sales-and-revenue-operations

这个 Skill 是做什么的

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

sales-and-revenue-operations 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。

安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。当前顶部介绍为空,原始 SKILL.md 摘录未提供。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/sales-and-revenue-operations

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

sales-and-revenue-operations 怎么安装?

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

sales-and-revenue-operations 支持哪些 AI 工具?

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

sales-and-revenue-operations 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

sales-and-revenue-operations 是免费的吗?

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

sales-and-revenue-operations 用的人多吗?

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

sales-and-revenue-operations 安全吗?

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

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

值得选的地方

  • 同时适配 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-and-revenue-operations

销售和收入运营 · 本页

3,49142只读未明确通过

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

SKILL.md 原文

Sales & Revenue Operations

Full-stack sales playbook: founder-led sales, team building, enterprise deals, RevOps, ICP definition, buyer personas, and compensation design.


Quick Start

  1. Assess stage — Founder-led, first reps, or scaling?
  2. Define motion — Inbound, outbound, PLG, or hybrid?
  3. Build ICP — Who are you selling to?
  4. Design process — Discovery → Demo → Close
  5. Instrument RevOps — Lead lifecycle, scoring, routing

ICP & Buyer Persona

ICP Stack (build bottom-up)

┌─────────────────────────────┐
│       BUYING CENTER          │ ← All decision stakeholders
├─────────────────────────────┤
│       USER PERSONA           │ ← Daily user
├─────────────────────────────┤
│       BUYER PERSONA          │ ← Signs the check
├─────────────────────────────┤
│       COMPANY PROFILE        │ ← Firmographics
└─────────────────────────────┘

Company Profile: industry/vertical, size (employees/revenue), stage, geography, tech stack

Buyer Persona: title/role, seniority, goals & KPIs, decision authority, what they care about

User Persona: daily workflow, pain points, tech savviness

Buying Center Roles: Champion, Economic Buyer, Technical Evaluator, End User, Blocker

ICP Scoring

FactorWeight
Problem severity25%
Budget available20%
Champion identified15%
Technical fit15%
Decision timeline15%
Expansion potential10%

The 50-Company Test

List 50 specific companies that fit. Find the buyer's name at 20 of them. Reach out to 10. If you can't do this, your ICP isn't specific enough.

For full persona canvases, buying center maps, interview questions, and fit scoring: see references/full-guide.md


Founder-Led Sales

Core principles:

  • The founder IS the product — your credibility closes deals early competitors can't
  • Your biggest competitor is indecision (40-60% of B2B purchases end in no decision)
  • Sell before you build — Figma mockups can secure first customers
  • Close the laptop — focus on diagnosis, not demos
  • Book next meeting on the current one to maintain momentum

When to hire: Wait until ~$1M ARR and a repeatable process. Hire in pairs — you need an A/B test.

Hiring framework:

StageWho to HireWhen
Founder-ledNobodyBefore $1M ARR
First AEs2 repsAfter proven repeatability
SDRs1-2When inbound overflows
VP Sales1When 2+ reps hitting quota

Enterprise Sales

Buying committee roles: Champion (internal advocate), Economic Buyer (signs), Technical Buyer (evaluates), End User (uses daily), Blocker (can say no)

JOLT method for indecision:

  1. Judge level of indecision
  2. Offer a firm recommendation
  3. Limit exploration by building trust
  4. Take risk off the table — de-risk the deal

Key tactics:

  • Identify and arm the champion — they sell internally for you
  • Address FOMU (Fear Of Making a Mistake), not just FOMO
  • Make procurement's job easy — prepare all documentation upfront

Sales Qualification

BANT: Budget · Authority · Need · Timeline

MEDDIC: Metrics · Economic Buyer · Decision Criteria · Decision Process · Identify Pain · Champion

Rule: Qualify ruthlessly. "No" is a successful outcome. Disqualify on the first call if fit isn't there.


Sales Enablement

Sales Deck (10-12 slides)

  1. Current World Problem, 2. Cost of the Problem, 3. The Shift Happening, 4. Your Approach, 5. Product Walkthrough (3-4 workflows), 6. Proof Points, 7. Case Study, 8. Implementation, 9. ROI/Value, 10. Pricing Overview, 11. Next Steps/CTA

Demo Structure

Opening (2 min) → Discovery Recap (3 min) → Solution Walkthrough (15-20 min) → Interaction → Close (5 min)

Objection Handling

CategoryResponse Approach
PriceROI angle, payment terms
TimingUrgency, cost of delay
CompetitionDifferentiation, unique value
AuthorityArm the champion
Status quoCost of inaction

Revenue Operations

Lead Lifecycle Stages

StageOwnerEntry Criteria
SubscriberMarketingOpts in to content
LeadMarketingBasic info provided
MQLMarketingFit + engagement threshold
SQLSalesAccepted, qualified via call
OpportunitySales AEBANT confirmed
CustomerCSClosed-won

MQL = Fit Score (who they are) + Engagement Score (what they do). Neither alone qualifies.

MQL-to-SQL SLA: Contact within 4 hours; qualify or reject within 48 hours.

Lead Scoring

Explicit (fit): Company size, industry, title, tech stack

Implicit (engagement): Pricing page visits, demo requests, email clicks, product usage

Negative: Competitor domains, student emails, unsubscribes

Lead Routing Methods

MethodBest For
Round-robinEqual territories
Territory-basedRegional/vertical teams
Account-basedNamed accounts / ABM
Skill-basedComplex deals, multi-product

Speed-to-lead: Contact within 5 minutes = 21x more likely to qualify. After 30 minutes, conversion drops 10x.

For routing decision trees and automation playbooks: see references/routing-rules.md, references/automation-playbooks.md

Pipeline Stage Hygiene

  • Enforce required fields per stage to block advancement with bad data
  • Flag stale deals (2x average time in stage) automatically
  • Alert on stage skips (Qualified → Proposal without Discovery)
  • Require reason codes on close date pushes

RevOps Metrics

MetricTarget
Lead-to-MQL rate5-15%
MQL-to-SQL rate30-50%
SQL-to-Opportunity50-70%
Win rate20-30%
Speed-to-lead<5 minutes
LTV:CAC ratio3:1 to 5:1

For scoring models and lifecycle definitions: see references/scoring-models.md, references/lifecycle-definitions.md


Sales Compensation

Standard structure: 50% base / 50% variable (OTE). This is a starting point, not a law.

Modern comp plans align with customer outcomes, not just bookings. Reps who close churny deals should earn less than those who close sticky customers.

Ramp periods: 3-6 months for SMB, 6-12 months for enterprise. Provide guaranteed draw or reduced quotas during ramp.

Simplicity rule: If reps can't instantly calculate how an action affects their pay, the plan is too complex.

Common mistakes:

  • Incentivizing only bookings without customer quality
  • Over-complicated plans with too many variables
  • No ramp protection for new hires
  • Ignoring churn in comp design

For detailed comp frameworks: see references/guest-insights.md


Sales Metrics

MetricWhat It Tells You
Win rateSales effectiveness
Sales cycle lengthProcess efficiency
Pipeline coverageForecast reliability (target 3-4x quota)
Lead-to-OpportunityQualification quality
CACAcquisition efficiency
Quota attainmentRep performance

Related Skills

  • outbound-email-strategy — Cold outreach
  • pricing-strategy — Pricing decisions
  • go-to-market-strategy — Full launch planning

平台分布

Codex

33.68%
按下载量换算384

Claude

31.96%
按下载量换算364

Cursor

19.87%
按下载量换算227

Gemini CLI

8.79%
按下载量换算100

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

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

继续浏览同类 Skills