Token导航 LogoToken导航

Agent Skill · 研究检索

predictable-revenue(可预测的收入)

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

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

总安装 32,448周安装 1,293GitHub Stars 779下载 10,504核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/wondelai/skills --skill predictable-revenue

这个 Skill 是做什么的

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

predictable-revenue 用于查找、检索和筛选相关信息。适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词、任务场景或来源线索快速定位候选结果。通过 npx skills add 命令从指定 GitHub 仓库安装并使用。

安装前需确认权限范围和维护状态,注意可能触发联网、命令执行或文件读写操作。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/predictable-revenue

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

predictable-revenue 怎么安装?

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

predictable-revenue 支持哪些 AI 工具?

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

predictable-revenue 需要什么权限?

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

predictable-revenue 是免费的吗?

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

predictable-revenue 用的人多吗?

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

predictable-revenue 安全吗?

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

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

值得选的地方

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

可预测的收入 · 本页

32,448779只读未明确通过

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

SKILL.md 原文

Predictable Revenue Framework

A systematic approach to building a scalable, predictable B2B sales machine. Pioneered the outbound prospecting system that helped Salesforce add $100M in recurring revenue.

Core Principle

Predictable lead generation drives predictable revenue. The biggest mistake in sales is having the same people prospect AND close. Specialization creates a repeatable, scalable machine.

The foundation: Cold calling is dead. Cold Calling 2.0 — mass, personalized cold emails that generate referrals to the right person — is the new outbound. Combined with sales role specialization, this creates predictable, scalable revenue.

Scoring

Goal: 10/10. When evaluating or building a sales process, rate 0-10 based on predictability, specialization, and process maturity. A 10/10 means clear role separation, repeatable prospecting process, and predictable pipeline generation; lower scores indicate ad-hoc sales or reliance on heroics. Always provide current score and improvements to reach 10/10.

The Three Types of Leads

Not all leads are created equal. Treat them differently.

TypeSourceConversionCostExample
SeedsWord of mouth, referrals, organicHighest (best quality)Lowest (takes time)Customer referral, NPS-driven
NetsMarketing campaigns, inboundMediumMediumContent marketing, SEO, webinars
SpearsOutbound prospectingLower (but predictable)Higher (people-intensive)Cold Calling 2.0, targeted outreach

Key insight: Most companies over-invest in nets (marketing) and under-invest in spears (outbound). Seeds are the best but can't be manufactured quickly. A balanced mix of all three creates predictable revenue.

Revenue mix:

  • Seeds: Invest in customer success, NPS, referral programs
  • Nets: Invest in content, SEO, paid acquisition
  • Spears: Invest in SDR team, Cold Calling 2.0

See: references/lead-types.md for lead source strategy and investment allocation.

Sales Role Specialization

The #1 principle: Separate prospecting from closing.

Traditional (broken) model:

  • AEs prospect AND close
  • Result: AEs hate prospecting, pipeline is feast-or-famine

Predictable Revenue model:

RoleFocusMetrics
SDR (Sales Development Rep)Outbound prospecting → qualified opportunitiesQualified meetings/month
MDR (Market Development Rep)Inbound lead qualificationQualified leads/month
AE (Account Executive)Close dealsRevenue closed, win rate
CSM (Customer Success Manager)Retain and grow accountsRetention rate, expansion revenue

SDR (Sales Development Rep)

Mission: Generate qualified pipeline through outbound prospecting.

Focus:

  • Research target accounts
  • Write personalized Cold Calling 2.0 emails
  • Get referred to the right person
  • Qualify opportunities (ANUM)
  • Pass qualified opportunities to AEs

Not their job:

  • Close deals
  • Handle inbound leads
  • Manage existing customers

Metrics:

  • Qualified opportunities generated per month
  • Response rate to outbound emails
  • Meetings booked per week
  • Pipeline value generated

SDR capacity: One SDR typically generates 10-20 qualified opportunities per month.

AE (Account Executive)

Mission: Close deals from qualified pipeline.

Focus:

  • Run discovery calls
  • Demo and present solutions
  • Negotiate and close
  • Hand off to CSM

Not their job:

  • Prospect for new leads (this is SDR's job)
  • Qualify inbound leads (this is MDR's job)
  • Manage post-sale relationships (CSM's job)

Metrics:

  • Revenue closed
  • Win rate
  • Average deal size
  • Sales cycle length

CSM (Customer Success Manager)

Mission: Retain customers and grow accounts.

Focus:

  • Onboard new customers
  • Drive adoption and engagement
  • Identify expansion opportunities
  • Prevent churn

Metrics:

  • Net revenue retention
  • Churn rate
  • Expansion revenue
  • NPS / CSAT

The virtuous cycle:

SDR generates pipeline → AE closes → CSM retains/grows → Happy customer refers (Seeds)

See: references/roles.md for role definitions, career paths, and hiring profiles.

Cold Calling 2.0

The outbound prospecting methodology that replaces traditional cold calling.

Why traditional cold calling fails:

  • Gatekeepers block calls
  • Decision makers don't answer phones
  • 1-3% connection rate
  • Damages brand
  • Not scalable

Cold Calling 2.0 process:

1. Build list → 2. Send mass email → 3. Get referral → 4. Call the referral → 5. Qualify

Step 1: Build Target Account List

Ideal Customer Profile (ICP):

  • Company size (employees, revenue)
  • Industry
  • Technology stack
  • Geography
  • Pain points

Build list using:

  • LinkedIn Sales Navigator
  • ZoomInfo / Apollo / Clearbit
  • Company websites
  • Industry directories

Target: 200-500 accounts per SDR per quarter

Step 2: The Referral Email

The core innovation: Don't email the decision maker directly. Email above them and ask for a referral down.

Why it works:

  • Senior people are helpful (they forward emails)
  • Referrals have 3-5x higher response rate
  • Creates warm introduction from within the company

The email template:

Subject: Quick question

Body:

Hi [Name], I'm not sure if you're the right person to speak to about [specific topic] at [Company], but I was hoping you could point me to the right person. We help [companies like theirs] with [specific value prop]. Would you mind pointing me to the right person to talk to? Thanks, [Your name]

Key elements:

  • Short (< 100 words)
  • No pitch, no attachments, no links
  • Asks for referral, not a meeting
  • Specific about what you do
  • Easy to forward

Response rate: 9-15% (vs. 1-3% for traditional cold emails)

Step 3: Follow Up

Follow-up sequence:

DayAction
Day 1Send referral email
Day 3Follow up if no response
Day 7Second follow up (different angle)
Day 14Break-up email ("Should I close your file?")
Day 30Re-engage (new trigger event or content)

Break-up email example:

Hi [Name], I haven't heard back from you. I don't want to be a pest. Should I close your file, or would it make sense to chat? [Your name]

Why break-up emails work: People respond to the threat of losing access/opportunity (scarcity principle).

Step 4: Qualify with ANUM

ANUM qualification framework:

CriteriaQuestionStrong SignalWeak Signal
AuthorityCan this person decide?Decision maker or strong influencerNo buying power
NeedDo they have the problem you solve?Active pain, looking for solutions"Nice to have"
UrgencyWhen do they need to solve it?This quarter, budget allocated"Someday"
MoneyCan they afford it?Budget exists, within rangeNo budget, too expensive

Qualification call structure:

  1. Build rapport (2 min)
  2. Set agenda ("I want to understand your situation and see if there's a fit")
  3. Discovery questions (10-15 min)
  4. ANUM qualification (built into discovery)
  5. Next steps (if qualified → schedule AE demo)

Step 5: Hand Off to AE

The handoff must include:

  • Account background and ICP match
  • Contact details and role
  • Pain points discovered
  • ANUM qualification notes
  • Agreed next steps
  • Any competitive intel

Handoff meeting: SDR introduces AE on a brief 3-way call or email, then drops off.

See: references/cold-calling-2.md for email templates, sequences, and scripts.

Pipeline Math

The math of predictable revenue:

Revenue Goal ÷ Average Deal Size = Deals Needed
Deals Needed ÷ Win Rate = Opportunities Needed
Opportunities Needed ÷ SDR Conversion = Prospects Needed
Prospects Needed ÷ Response Rate = Emails Needed

Example:

  • Revenue goal: $1M ARR
  • Average deal: $20K ARR
  • Deals needed: 50
  • Win rate: 25%
  • Opportunities needed: 200
  • SDR conversion: 10% of responses become qualified
  • Response rate: 10% of emails get responses
  • Emails needed: 20,000
  • SDRs needed: ~2-3 (each sends 300-500 emails/month)

Capacity planning:

MetricBenchmarkYour Number
Emails per SDR per day50-100
Response rate9-15%
Qualified opportunities per SDR per month10-20
AE demo-to-close rate20-30%
Average sales cycle30-90 days

See: references/pipeline-math.md for revenue modeling templates.

Building the Sales Development Team

Hiring SDRs

Ideal SDR profile:

  • Coachable (most important trait)
  • Curious and intelligent
  • Strong writing skills
  • Resilient (handles rejection)
  • Organized and process-oriented
  • Not necessarily experienced

Where to hire:

  • Recent graduates
  • Career changers
  • Internal transfers
  • SDR-to-AE career path candidates

SDR career path:

SDR (6-18 months) → Senior SDR → AE or SDR Manager

SDR Ramp Time

PhaseTimelineExpectations
TrainingWeeks 1-2Product knowledge, tools, process
ShadowingWeeks 3-4Observe experienced SDRs, practice
RampingMonths 2-350% of full quota
Full quotaMonth 4+100% of quota

Full ramp: Expect 3-4 months to full productivity.

SDR Compensation

Structure: Base salary + variable (commission on qualified opportunities)

Typical split: 60/40 or 70/30 (base/variable)

Variable triggers:

  • Per qualified opportunity generated
  • Bonus for opportunities that close
  • Bonus for hitting/exceeding quota

See: references/team-building.md for hiring, onboarding, and compensation.

Metrics and Dashboards

Key metrics to track:

Leading Indicators (Predictive)

  • Emails sent per SDR per day
  • Response rate
  • Meetings booked per week
  • Qualified opportunities per month
  • Pipeline value generated

Lagging Indicators (Results)

  • Revenue closed
  • Win rate
  • Average deal size
  • Sales cycle length
  • Customer acquisition cost (CAC)

Efficiency Metrics

  • Cost per qualified opportunity
  • SDR:AE ratio (typically 2-3 SDRs per AE)
  • LTV:CAC ratio (target >3:1)
  • Payback period

Dashboard cadence:

  • Daily: Activity metrics (emails, calls, responses)
  • Weekly: Pipeline metrics (opportunities, meetings)
  • Monthly: Revenue metrics (closed, win rate, cycle)
  • Quarterly: Efficiency metrics (CAC, LTV, ratios)

See: references/metrics.md for dashboard templates.

Common Mistakes

MistakeWhy It FailsFix
AEs prospectingFeast-or-famine pipelineHire dedicated SDRs
Long, pitchy emailsLow response rateShort, referral-focused emails
No ICP definitionWasted effort on wrong accountsDefine ICP before hiring SDRs
Too few SDRsCan't generate enough pipelinePipeline math: work backward from revenue goal
No hand-off processLeads fall through cracksStandardize SDR→AE handoff
Measuring activity, not resultsBusy but not productiveTrack qualified opportunities, not just emails

Quick Diagnostic

Audit any B2B sales process:

QuestionIf NoAction
Are prospecting and closing separated?SDRs doing both = bottleneckCreate dedicated SDR role
Is there a defined outbound process?Ad-hoc prospectingImplement Cold Calling 2.0
Can you predict pipeline 3 months out?Revenue is unpredictableBuild pipeline math model
Do you know your lead type mix?Over-reliance on one sourceBalance seeds, nets, spears
Is SDR→AE handoff standardized?Leads lost in transitionCreate handoff checklist

Reference Files

Further Reading

This skill is based on Aaron Ross's Predictable Revenue methodology. For the complete system:

About the Author

Aaron Ross built the outbound sales process at Salesforce.com that added $100M+ in recurring revenue. His Cold Calling 2.0 methodology became the standard for B2B outbound prospecting and is used by thousands of companies worldwide. *Predictable Revenue* is known as "The Bible of Outbound Sales" and has influenced an entire generation of SaaS sales organizations. Ross is also co-founder of Predictable Revenue Inc., which helps companies build outbound sales machines.

平台分布

Codex

33.6%
按下载量换算3,529

Claude

31.12%
按下载量换算3,269

Cursor

20.42%
按下载量换算2,145

Gemini CLI

10.29%
按下载量换算1,081

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills