Token导航 LogoToken导航

Agent Skill · 开发

monetizing-innovation(将创新货币化)

monetizing-innovation 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

monetizing-innovation 是开发类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在开发类的 21,746 个 Skill 里排第 16,443。

总安装 499周安装 20GitHub Stars 111下载 162核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/getagentseal/founder-playbook --skill monetizing-innovation

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合围绕项目状态进行整理。适用于代码变更追踪、协作事项管理和仓库状态查询等开发场景。通过 npx skills add 命令从 GitHub 仓库安装,需确认权限与维护状态。使用前建议核实是否会触发联网、命令执行或文件读写操作。

可结合原始 README 和仓库路径进一步了解具体用法与限制。

来源仓库内路径:skills/monetizing-innovation

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

monetizing-innovation 怎么安装?

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

monetizing-innovation 支持哪些 AI 工具?

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

monetizing-innovation 需要什么权限?

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

monetizing-innovation 是免费的吗?

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

monetizing-innovation 用的人多吗?

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

monetizing-innovation 安全吗?

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

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理开发类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
skill-vetter

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
monetizing-innovation

将创新货币化 · 本页

499111只读未明确通过

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

SKILL.md 原文

Note: This skill is independent analysis and commentary, not a reproduction of the original text. It synthesizes the book's core ideas with modern startup practice, surfaces where frameworks are outdated or incomplete, and integrates perspectives from adjacent disciplines. For the full argument and context, read the original book.

Monetizing Innovation

"Design the product around the price." - Ramanujam & Tacke

Core Insight

72% of new products fail (Simon-Kucher 2014, n=1,615). Root cause: pricing is decided LAST instead of designing the product around it. This figure comes from Simon-Kucher's own client survey data and has not been independently verified. The authors are principals at Simon-Kucher, a pricing consultancy - the stat motivates hiring firms like theirs. Treat it as directionally correct but not independently validated.

Old paradigmNew paradigm
design → build → market → pricemarket & price → design → build

Only ~5% of business cases include real WTP (willingness-to-pay) data. Most companies wait until weeks before launch to set price.


The 4 Failure Types (Diagnose Before Fixing)

FailureDefinitionCultural CauseTell-Tale Signs
Feature ShockCram too many features → confusing, overpricedEngineering-drivenCan't articulate value; price slashed post-launch
MinivationRight product, priced too lowRisk-averseSales easily hits target; sellouts; channel maxes margin
Hidden GemGreat idea never properly launchedCoddles core businessMid-level execs kill it; sold as deal sweetener; rival ships first
UndeadWrong answer (or no question asked)Top-down, no dissentSales avoid raising it; pet project of senior management

Real examples: Amazon Fire Phone (Feature Shock, $170M write-down), Audi Q7 (Minivation, missed €210M/yr), Kodak digital camera 1974 (Hidden Gem), Segway/Google Glass (Undead).

Full case file: see cases.md.


The 5 Pricing Myths (Counter These)

  1. "Build it and they will come" - hides 95% of failures
  2. "Innovation needs isolated artists" - customer input informs, doesn't pollute
  3. "High failure rates are normal" - failure is preventable
  4. "Customers must experience product to price it" - false, they react to concepts
  5. "You can't price what you haven't built" - cost-plus thinking; price is set by VALUE

The 9 Rules (Summary)

#RuleHeadline
1WTP Talk Early80% of companies skip this. Have it before design freezes.
2Needs-Based SegmentationDemographic segmentation is broken. Segment by needs/value/WTP.
3Configuration & BundlingUse Leaders/Fillers/Killers + Good/Better/Best with FENCES.
4How You Charge > What You ChargeChoose the right monetization model (5 options).
5Pricing StrategyMaximization / Penetration / Skimming. Apply the BECAUSE test.
6Living Business CaseLink Price-Value-Volume-Cost. Update at every milestone.
7Value CommunicationSell benefits, not features. Use MOCA matrix.
8Behavioral Pricing6 tactics: compromise, anchoring, signals, razor-blade, pennies-a-day, thresholds.
9Maintain Price IntegrityDon't cut after launch. Use 3 nonprice actions first.

Full framework details with sub-frameworks, methods, and checklists: see frameworks.md.


Critical Frameworks (At-a-Glance)

Leaders / Fillers / Killers

TypeDefinitionAction
LeaderDrives buying, high WTPAlways include
FillerNice-to-haveUse to fill gaps
KillerBlows the deal if forced to payEliminate or sell à la carte

Killer test: valued by <20% of customers AND not valued at all by >20%. Killers are segment-dependent (heated seats: leader in cold, killer in tropical).

Good/Better/Best Distribution

DistributionDiagnosis
≤25% Good, ~70% Better+Best, ≥10% BestHealthy
>50% GoodTrip-wire: cut features from Good
Best <10%Premium tier underpowered

Fences are mandatory. Every tier needs visible, defensible differences. Without fences G/B/B cannibalizes itself. Fence test: in 10 seconds can a customer see what's missing from Good?

The 5 Monetization Models

ModelWhen to UseExample
SubscriptionContinual usageNetflix, Adobe
Dynamic PricingVolatile demand or constrained supplyUber, airlines
AuctionsSeller's market, constrained inventoryGoogle AdWords ($35B/yr), eBay
Pay-As-You-Go / Alternative MetricUsage tracks valueMichelin (per-mile), GE engines
FreemiumNear-zero production AND fixed costLinkedIn, Dropbox

Freemium warning: fails for 90% of companies; software conversion typically <10%; games lose 75% of users in day 1.

Models are mix-and-matchable (Costco = subscription + per-product; OpenTable = subscription + transaction fee).

The 6 Behavioral Pricing Tactics

  1. Compromise effect - always have 3 tiers; people avoid extremes
  2. Anchoring - The Economist test: $59 vs $125 vs $125-print-only made bundle pick rate jump 32% → 84%
  3. Price signals quality - Ariely placebo: $2.50 pill 85% pain relief, $0.10 same pill 61%
  4. Razor / razor blades - low upfront preferred even if total cost identical
  5. Pennies-a-day - $9.99/mo converts very differently from $120/yr
  6. Psychological thresholds - $69.99 works, $71 doesn't (drops acceptance >20%)

Caveat: can't price purely on behavior. Combine with rational/value-based.


Decision Trees

"Is my product likely to fail?"

Can I clearly state the customer benefit (not features)?
├─ NO  → Likely Feature Shock
└─ YES → Has WTP been validated with real customers?
         ├─ NO  → Could be Undead or Minivation
         └─ YES → Did C-suite engage personally?
                  ├─ NO  → Likely Hidden Gem (won't get launched right)
                  └─ YES → On the right track

"Which monetization model?"

Is value tied to usage?
├─ YES → Alternative Metric (Michelin model)
└─ NO  → Demand volatile or supply constrained?
        ├─ YES → Dynamic Pricing
        └─ NO  → Production cost near zero?
                ├─ YES → Freemium (only if 90% of users still profitable)
                └─ NO  → Subscription or per-unit

"Should I cut the price?"

Sales below plan?
└─ YES → Identified ROOT CAUSE?
         ├─ NO  → Diagnose first (likely not price)
         └─ YES → Pricing-specific?
                  ├─ NO  → Fix actual problem
                  └─ YES → Tried 3 nonprice actions?
                           ├─ NO  → Try those (advertise; add value; upgrade)
                           └─ YES → War-game competitor reaction
                                    └─ Worse off after counter? → don't cut

Critical Numbers

NumberRule
72%New products fail
80%Companies wait until just before launch to set price
5%Business cases include real WTP data
3-4Ideal starting number of segments
<10%Killer features valued by less than this %
9 / 4Max benefits / products before psychological overload
≤25% / 70% / ≥10%G/B/B target (Good / Better+Best / Best)
50%Trip-wire: more than this picking Good = bleeding
20-30%Healthy deal escalation rate
30-40%Of ALL DEALS should have price changes upon escalation
3Nonprice actions required before any price cut
40%More likely to realize potential with defined pricing strategy
33%More profit when C-suite leads pricing (vs delegates) - also from Simon-Kucher client data; same provenance caveat as the 72% figure applies
25%Of customer interview questions should be "Why?"

The "BECAUSE" Test

Every pricing decision must end with a "because" traceable to customer data.

Bad: "We priced at $99 to be competitive." Good: "We priced at $99 BECAUSE 60% of segment B told us $100 was the threshold above which they'd reconsider, and our value advantage justifies the high end."

If you can't say "because customers told us X," you don't have a pricing strategy.


Quick Reference Checklist

Before designing a new product:

  • WTP conversations with real customers held
  • Segmented by needs/value/WTP (not demographics)
  • Leaders, fillers, killers identified
  • G/B/B configuration designed with FENCES
  • Monetization model picked (aligns with value)
  • Pricing strategy documented (max/penetration/skimming)
  • Living business case links Price/Value/Volume/Cost
  • Benefit-not-feature messaging tested
  • Behavioral tactics considered
  • Team prepared to maintain price integrity post-launch

The test: Ask anyone "Why this price?" If the answer is "cost-plus" or "competitor benchmark," failure is coming.


Critical Quotes

  • "Design the product around the price."
  • "How you charge trumps what you charge."
  • "Pricing too low is worse than pricing too high."
  • "Customers don't buy products. They buy benefits." - Drucker
  • "The single most important decision in evaluating a business is pricing power." - Buffett
  • "If I have 2,000 customers and 400 prices, I'm short 1,600 prices." - Crandall (American Airlines)

Supporting Files

  • frameworks.md - Full detail on all 9 rules, sub-frameworks, methods, and lists (10 WTP insights, 10 bundling insights, 6 post-launch tips, etc.)
  • cases.md - Detailed case studies (Porsche, Dodge Dart, LinkedIn, Dräger, Uber, Swarovski, Optimizely, Innovative Pharma) plus failure exemplars
  • examples.md - Worked examples: Pizza & Breadsticks bundling math, MOCA matrix, value-selling spreadsheet, 100-point goal allocation, BECAUSE test templates
  • integration.md - Implementation roadmap (4 phases), 9 pitfalls, startup/SaaS adaptation, WTP research limitations, conflict resolution with Mom Test/$100M Offers/SPIN

When This Doesn't Apply

  • Pure cost-plus regulated environments (utilities, some defense)
  • Pure commodities (sugar, copper)
  • Very early stage with no product (use Mom Test first)
  • B2C impulse buys under $50 (simpler approaches work)
  • Geographic markets with no purchasing power

Caveat on WTP Research

Stated WTP and revealed WTP differ. Customers predict their own behavior poorly in interviews. Treat WTP findings as a strong prior, not certainty. Validate with paid pilots, pre-orders, live A/B price tests, or money-back guarantees. See integration.md.

平台分布

Codex

33.59%
按下载量换算54

Claude

29.87%
按下载量换算48

Cursor

19.7%
按下载量换算32

Gemini CLI

10.15%
按下载量换算16

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills