Token导航 LogoToken导航

Agent Skill · 研究检索

lean-canvas(精益画布)

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

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

总安装 2,136周安装 89GitHub Stars 85下载 712核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/guia-matthieu/clawfu-skills --skill lean-canvas

这个 Skill 是做什么的

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

精益画布技能用于查找、检索和筛选相关信息。适用于需要基于关键词或业务场景快速获取结构化洞察的场景。集成于 Codex、Claude、Cursor、Gemini CLI 等宿主环境,支持智能辅助决策。使用前应核实其是否具备网络访问或文件操作能力,防止误触生产系统。

lean-canvas 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/lean-canvas

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

lean-canvas 怎么安装?

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

lean-canvas 支持哪些 AI 工具?

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

lean-canvas 需要什么权限?

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

lean-canvas 是免费的吗?

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

lean-canvas 用的人多吗?

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

lean-canvas 安全吗?

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

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

值得选的地方

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

精益画布 · 本页

2,13685需要联网未明确通过

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

SKILL.md 原文

Lean Canvas

Document your business model on one page and systematically de-risk it. Master Ash Maurya's adaptation of Business Model Canvas optimized for startups and uncertainty.

When to Use This Skill

  • Starting a new venture to articulate and test your business model
  • Preparing for customer discovery to document hypotheses to validate
  • Pivoting decisions to compare alternative business models
  • Investor conversations to communicate your model concisely
  • Team alignment to get everyone on the same page
  • Comparing opportunities to evaluate multiple ideas systematically

Methodology Foundation

AspectDetails
SourceAsh Maurya - "Running Lean" (2012), adapted from Osterwalder's Business Model Canvas
Core Principle"Document your Plan A, identify the riskiest parts, and systematically test them."
Why This MattersA business plan is a 60-page guess. A Lean Canvas is a 1-page hypothesis you can test in weeks, not months. It replaces planning with learning.

What Claude Does vs What You Decide

Claude DoesYou Decide
Structures production workflowFinal creative direction
Suggests technical approachesEquipment and tool choices
Creates templates and checklistsQuality standards
Identifies best practicesBrand/voice decisions
Generates script outlinesFinal script approval

What This Skill Does

  1. Creates one-page business models - 9 boxes that capture your entire model
  2. Identifies riskiest assumptions - Highlights what could kill your business
  3. Prioritizes validation experiments - Focuses on highest-risk unknowns first
  4. Enables rapid pivots - Easy to update as you learn
  5. Facilitates communication - Share your model in 5 minutes
  6. Tracks evolution - Version control your business model thinking

How to Use

Create a Lean Canvas for a New Idea

Create a Lean Canvas for this business idea: [description]
Fill out all 9 boxes and identify the top 3 riskiest assumptions.

Compare Two Business Models

I'm deciding between two approaches:
Option A: [description]
Option B: [description]

Create Lean Canvases for both and compare them on risk and potential.

Identify What to Validate First

Here's my Lean Canvas: [paste canvas]
What are the riskiest assumptions? Design experiments to test them.

Instructions

When creating or analyzing Lean Canvases, follow this systematic approach:

Step 1: Understand the 9 Boxes

## Lean Canvas Structure

┌──────────────────┬──────────────────┬──────────────────┐
│                  │                  │                  │
│  2. PROBLEM      │  4. SOLUTION     │ 3. UNIQUE VALUE  │
│  (Top 3)         │  (Top 3 features)│    PROPOSITION   │
│                  │                  │                  │
│                  │                  │ High-level       │
│                  ├──────────────────┤ concept          │
│                  │                  │                  │
│ Existing         │  8. KEY METRICS  │                  │
│ Alternatives     │  (Pirates:       │                  │
│                  │   AARRR)         │                  │
│                  │                  │                  │
├──────────────────┼──────────────────┼──────────────────┤
│                  │                  │                  │
│  9. UNFAIR       │  5. CHANNELS     │ 1. CUSTOMER      │
│     ADVANTAGE    │  (Path to        │    SEGMENTS      │
│  (Can't be       │   customers)     │  (Target users)  │
│   copied)        │                  │                  │
│                  │                  │ Early Adopters   │
│                  │                  │                  │
├──────────────────┴──────────────────┴──────────────────┤
│  7. COST STRUCTURE           │  6. REVENUE STREAMS     │
│  (Fixed + Variable)          │  (Pricing model)        │
└──────────────────────────────┴─────────────────────────┘

Key Difference from Business Model Canvas:

  • Replaces Partners/Resources/Activities with Problem/Solution/Key Metrics
  • Adds Unfair Advantage
  • Focuses on RISK and LEARNING, not operational planning

Step 2: Fill Out Each Box (In Order)

Recommended Order: Customer Segments → Problem → Unique Value Proposition → Solution → Channels → Revenue → Cost → Key Metrics → Unfair Advantage

## Box-by-Box Guide

### 1. CUSTOMER SEGMENTS
**Question:** Who are you creating value for?

Target customers:
- [Primary segment]
- [Secondary segment if any]

Early Adopters (most important):
- [Specific description of first customers]
- Why they'll buy first: [reason]

Tips:
- Be specific (not "businesses" but "SaaS companies 10-50 employees")
- Identify early adopters who feel the pain most acutely
- If you can't describe them, you can't find them

---

### 2. PROBLEM
**Question:** What problems are you solving?

Top 3 Problems:
1. [Most critical problem]
2. [Second problem]
3. [Third problem]

Existing Alternatives (how they solve it today):
- [Alternative 1]
- [Alternative 2]

Tips:
- List problems from the CUSTOMER's perspective
- If existing alternatives work well, your problem isn't painful enough
- Every problem should be something you've validated (or will validate first)

---

### 3. UNIQUE VALUE PROPOSITION
**Question:** Why should customers choose you?

Single clear message:
"[We help] [customer segment] [achieve outcome] [unlike alternatives]
[because unique differentiator]."

High-level concept (analogy):
"X for Y" or "Like X but for Y"
Example: "Uber for dog walkers"

Tips:
- Focus on the END BENEFIT, not features
- Make it different, not just better
- Test: Can you say this in 10 seconds?

---

### 4. SOLUTION
**Question:** What are you building?

Top 3 Features (that solve top 3 problems):
1. [Feature → Problem 1]
2. [Feature → Problem 2]
3. [Feature → Problem 3]

Tips:
- Match each solution to a problem
- Keep it minimal - MVP thinking
- This box should be the LAST one you fill with certainty

---

### 5. CHANNELS
**Question:** How will you reach customers?

Path to Customers:
- Awareness: [How they learn about you]
- Acquisition: [How they start using]
- Retention: [How they keep using]

Specific channels:
- [Channel 1: e.g., Content marketing]
- [Channel 2: e.g., Direct sales]
- [Channel 3: e.g., Partnerships]

Tips:
- Start with channels that don't scale (do things that don't scale)
- Match channels to where early adopters spend time
- Free channels first, paid channels when you have product-market fit

---

### 6. REVENUE STREAMS
**Question:** How will you make money?

Pricing Model:
- [ ] One-time purchase
- [ ] Subscription
- [ ] Freemium
- [ ] Transaction fee
- [ ] Advertising
- [ ] Other: ___________

Price Point:
- [Price]: [Justification]

Revenue Formula:
- [Customers] × [Price] × [Frequency] = [Revenue]

Tips:
- Price on value, not cost
- Test pricing early (it's a feature)
- If you can't charge, you don't have a business

---

### 7. COST STRUCTURE
**Question:** What are your costs?

Fixed Costs (monthly):
- [Cost 1]: $___
- [Cost 2]: $___
- Total Fixed: $___

Variable Costs (per customer):
- [Cost per customer]: $___

Customer Acquisition Cost (target):
- CAC: $___

Break-even:
- Need ___ customers at $___ to break even

Tips:
- Keep fixed costs minimal early
- Know your unit economics before scaling
- CAC must be < LTV (lifetime value)

---

### 8. KEY METRICS
**Question:** How will you measure success?

Pirate Metrics (AARRR):
- Acquisition: [How many sign up?]
- Activation: [How many have "aha" moment?]
- Retention: [How many come back?]
- Revenue: [How many pay?]
- Referral: [How many refer others?]

One Metric That Matters (right now):
- [Single metric]: [Target]

Tips:
- Focus on ONE metric at a time
- Vanity metrics (signups, page views) lie
- Measure behavior, not opinions

---

### 9. UNFAIR ADVANTAGE
**Question:** What makes you defensible?

Can't be easily copied or bought:
- [ ] Insider information
- [ ] Dream team
- [ ] Personal authority/brand
- [ ] Network effects
- [ ] Community
- [ ] Existing customers
- [ ] Proprietary tech/data
- [ ] SEO ranking

Your unfair advantage:
- [What is it?]
- [Why can't competitors copy it?]

Tips:
- Most startups don't have one at first (that's OK)
- It often emerges over time
- "Passion" and "first mover" are NOT unfair advantages

Step 3: Identify Riskiest Assumptions

## Risk Assessment

### Stage 1 Risks (Product Risk)
"Do I have a problem worth solving?"

| Assumption | Type | Evidence | Risk Level |
|------------|------|----------|------------|
| Problem exists and is painful | PROBLEM | | High/Med/Low |
| Customers are identifiable | CUSTOMER | | High/Med/Low |
| Current alternatives inadequate | PROBLEM | | High/Med/Low |

### Stage 2 Risks (Market Risk)
"Have I built something people want?"

| Assumption | Type | Evidence | Risk Level |
|------------|------|----------|------------|
| Solution solves the problem | SOLUTION | | High/Med/Low |
| Customers will pay [price] | REVENUE | | High/Med/Low |
| CAC is sustainable | COST | | High/Med/Low |

### Stage 3 Risks (Scale Risk)
"Can I build a viable business?"

| Assumption | Type | Evidence | Risk Level |
|------------|------|----------|------------|
| Channels work at scale | CHANNEL | | High/Med/Low |
| Unit economics work | COST/REV | | High/Med/Low |
| Defensibility exists | ADVANTAGE | | High/Med/Low |

### TOP 3 RISKIEST ASSUMPTIONS
1. [Highest risk - validate first]
2. [Second highest]
3. [Third highest]

Step 4: Design Validation Experiments

## Validation Plan

### For each risky assumption:

**Assumption:** [Statement]
**Risk if wrong:** [Consequence]

**Experiment:**
- Type: [Interview / Landing page / Prototype / Concierge]
- Target: [Who/How many]
- Timeline: [Duration]

**Success Criteria:**
- Validated if: [Specific metric]
- Invalidated if: [Specific metric]

**Next Action:**
- [ ] [Specific next step]

Examples

Example 1: B2B SaaS - Sales Enablement Tool

Input:

"Create a Lean Canvas for a sales enablement tool that helps SDRs personalize outreach at scale."

Output:

## LEAN CANVAS: SalesAI - Personalized Outreach at Scale

┌─────────────────────────────────────────────────────────────────────┐
│                                                                      │
│  2. PROBLEM                      │  4. SOLUTION                     │
│  ────────────                    │  ────────────                    │
│  1. SDRs spend 40% of time       │  1. AI-generated personalized    │
│     researching prospects         │     intros based on LinkedIn +   │
│  2. Generic outreach gets        │     company data                  │
│     <2% response rates           │  2. One-click personalization    │
│  3. Good reps leave, burnout     │     for 100+ contacts/day        │
│     from repetitive work         │  3. Response rate dashboard      │
│                                  │     with A/B testing             │
│  Existing Alternatives:          │                                  │
│  - Manual research (slow)        ├─────────────────────────────────│
│  - Outreach.io (templates only)  │  8. KEY METRICS                  │
│  - ZoomInfo (data, no writing)   │  ────────────────                │
│                                  │  - # messages personalized/day   │
│                                  │  - Response rate improvement     │
│                                  │  - Time saved per SDR            │
│                                  │  - OMTM: Response rate lift %    │
│                                  │                                  │
├──────────────────────────────────┴──────────────────────────────────┤
│  3. UNIQUE VALUE PROPOSITION                                         │
│  ────────────────────────────                                        │
│  "Write 100 personalized emails in the time it takes to write 5."   │
│                                                                      │
│  High-level concept: "Jasper AI for sales outreach"                 │
│                                                                      │
├─────────────────────────────────────────────────────────────────────┤
│  9. UNFAIR ADVANTAGE            │  5. CHANNELS              │  1.  │
│  ────────────────────           │  ────────────             │ CUST │
│  - Training data from           │  - LinkedIn content       │ SEGS │
│    1M+ successful emails        │  - Sales podcasts ads     │ ──── │
│  - Network of SDR community     │  - Outbound (dogfooding)  │ B2B  │
│    (early adopters)             │  - Integrations:          │ SDRs │
│  - (Initially: None)            │    Outreach, Salesloft    │ at   │
│                                 │                           │ 50-  │
│                                 │                           │ 500  │
│                                 │                           │ emp  │
│                                 │                           │ SaaS │
│                                 │                           │      │
│                                 │                           │ EA:  │
│                                 │                           │ SDR  │
│                                 │                           │ mgrs │
│                                 │                           │ w/   │
│                                 │                           │ 5+   │
│                                 │                           │ reps │
├─────────────────────────────────┴───────────────────────────┴──────┤
│  7. COST STRUCTURE                  │  6. REVENUE STREAMS          │
│  ──────────────────                 │  ────────────────────        │
│  Fixed:                             │  Model: Per-seat SaaS        │
│  - Team (2 founders): $0 (sweat)    │  Price: $99/user/month       │
│  - Infrastructure: $500/mo          │  Tiers:                      │
│  - Tools: $200/mo                   │  - Starter: $99 (1-5 seats)  │
│                                     │  - Growth: $79 (6-20 seats)  │
│  Variable:                          │  - Enterprise: Custom        │
│  - AI costs: ~$0.10/user/day        │                              │
│  - CAC target: <$500                │  LTV target: $1,800 (18 mo)  │
│                                     │  LTV:CAC ratio: 3.6:1        │
│  Break-even: 50 paying users        │                              │
└─────────────────────────────────────┴──────────────────────────────┘

Riskiest Assumptions:

#AssumptionRisk LevelWhy
1AI can write emails that perform better than humansHIGHCore value prop depends on this
2SDRs/managers will trust AI with prospect communicationHIGHCultural barrier could block adoption
3$99/user is acceptable price pointMEDIUMDetermines if business is viable

Validation Plan:

  1. Week 1-2: Build prototype, A/B test AI vs. human emails (10 SDRs)
  2. Week 3-4: Interview 15 SDR managers on trust/adoption concerns
  3. Week 5: Pricing validation with early adopter interviews

Example 2: Consumer App - Fitness for Parents

Input:

"Here's my Lean Canvas for a fitness app for busy parents. What are the riskiest assumptions?"

User's Canvas:

Problem: No time to exercise, gym is inconvenient
Customer: Working parents 30-45 with young kids
Solution: 10-minute home workouts, kid-friendly
Revenue: $9.99/month subscription

Output:

Risk Analysis:

CRITICAL ISSUE: This canvas is incomplete and under-specified.

Problems I See:

  1. Customer segment too broad

- "Working parents 30-45" = millions of people - Who are the EARLY ADOPTERS who will pay first? - Missing: Income level, fitness history, tech savviness

  1. Problem not differentiated

- "No time to exercise" is the problem of EVERY fitness app - Existing alternatives: Peloton, Nike Training, YouTube, Apple Fitness+ - Why would someone SWITCH from these?

  1. Solution is a feature list, not a value prop

- "10-minute workouts" exists everywhere - "Kid-friendly" - what does this actually mean?

  1. Revenue assumptions untested

- $9.99/month - based on what? - Fitness apps have notoriously high churn - Most people don't pay for fitness apps

Riskiest Assumptions (in order):

#AssumptionRiskEvidence Needed
1Parents will PAY for yet another fitness appFATALOnly 2-5% of app downloaders pay. Need proof of WTP
2"Kid-friendly" is a differentiator people care aboutHIGHDoes this problem exist? Do they seek solutions?
310-minute workouts are effective enoughMEDIUMWill users see results and stay?
4$9.99 is the right priceMEDIUMCould be too high or too low

Recommendation:

Before building anything, validate:

  1. Do parents with kids SPECIFICALLY want kid-friendly fitness?

- Interview 15 parents who've TRIED fitness apps - Ask: What made you quit? What would make you stay?

  1. Is "kid-friendly" a real differentiator?

- What does this mean? Kids do it with them? Kids don't interrupt? - Test: Would they pay MORE for this feature?

  1. Willingness to pay?

- How many of your target users currently pay for any fitness solution? - If <30%, this market may not monetize

Revised Canvas Hypothesis:

## More Specific Lean Canvas

Customer Segment:
- Primary: Stay-at-home moms, ages 28-40, with kids 2-6
- Early Adopter: Former gym-goers who quit after having kids
  and have tried 2+ fitness apps in past year

Problem (validated):
- Can't workout because toddler interrupts/needs attention
- Guilt about "ignoring" kids to exercise
- Previous apps failed because required uninterrupted time

Unique Value Proposition:
"The only workout you can do WITH your toddler, not despite them."

Solution:
- Workouts designed for parent + kid together
- Toddler becomes part of the exercise (lifting, playing)
- 15-min max, no equipment, living room safe

This is more specific and testable.


Example 3: Pivot Comparison

Input:

"I'm considering pivoting. Compare these two Lean Canvases and recommend which to pursue."

Canvas A: B2B Analytics Dashboard

  • Customer: Marketing managers at e-commerce companies
  • Problem: Too many analytics tools, no unified view
  • Solution: All-in-one dashboard connecting GA, FB, Shopify
  • Revenue: $299/month
  • Unfair Advantage: None yet

Canvas B: Shopify App for Email Segmentation

  • Customer: Shopify store owners doing 100K-1M revenue
  • Problem: Mailchimp/Klaviyo segments are basic
  • Solution: AI-powered customer segmentation for Shopify
  • Revenue: $49/month
  • Unfair Advantage: Shopify partnership potential

Output:

Comparative Analysis:

DimensionCanvas A (Dashboard)Canvas B (Shopify App)
Market SizeLarge (all e-commerce)Smaller (Shopify only)
CompetitionHIGH (Databox, Klipfolio, Geckoboard, custom)MEDIUM (some apps exist)
DifferentiationLOW (everyone does "unified")MEDIUM (AI segmentation specific)
DistributionHard (enterprise sales)EASIER (Shopify App Store)
Price Point$299 (requires sales)$49 (self-serve possible)
Unfair AdvantageNoneShopify ecosystem
Time to RevenueLongerShorter

Risk Assessment:

Canvas A Risks:

RiskLevelNotes
Building a commodityHIGH"Unified dashboard" = red ocean
Long sales cyclesHIGH$299 needs demos, trials
Integration complexityHIGHMust support many platforms
No defensibilityHIGHEasy to copy

Canvas B Risks:

RiskLevelNotes
Platform dependencyHIGHShopify could change rules
Smaller marketMEDIUMLimited to Shopify stores
AI hype skepticismMEDIUMMust prove AI actually works better
Low price = high volume neededMEDIUMNeed ~200 customers to be meaningful

Recommendation: PURSUE CANVAS B

Reasoning:

  1. Faster validation: Shopify App Store = immediate distribution. You can test in weeks.
  2. Clearer differentiation: "AI segmentation" is specific vs. "unified dashboard" which is generic.
  3. Better path to defensibility:

- App Store reviews and ratings compound - Shopify partner program potential - Data from customers creates better AI

  1. Lower risk profile: $49 self-serve is easier to sell than $299 with demos.
  2. Pivot optionality: If it works on Shopify, you can expand to other platforms. If Canvas A fails, you have nothing.

BUT validate first:

  • Is "segmentation" really the pain point? Or is it "I don't know what emails to send"?
  • Do Shopify merchants actually buy apps? What's average spend?
  • What's the competitive landscape in Shopify App Store?

Checklists & Templates

Lean Canvas Template (Blank)

## LEAN CANVAS: [Product Name]

**Version:** 1.0
**Date:** ___________
**Author:** ___________

┌─────────────────────────────────────────────────────────────────────┐
│                                                                      │
│  2. PROBLEM                      │  4. SOLUTION                     │
│  ────────────                    │  ────────────                    │
│  1.                              │  1.                              │
│  2.                              │  2.                              │
│  3.                              │  3.                              │
│                                  │                                  │
│  Existing Alternatives:          ├─────────────────────────────────│
│  -                               │  8. KEY METRICS                  │
│  -                               │  ────────────────                │
│                                  │  A:                              │
│                                  │  A:                              │
│                                  │  R:                              │
│                                  │  R:                              │
│                                  │  R:                              │
│                                  │  OMTM:                           │
├──────────────────────────────────┴──────────────────────────────────┤
│  3. UNIQUE VALUE PROPOSITION                                         │
│  ────────────────────────────                                        │
│                                                                      │
│  High-level concept:                                                 │
├─────────────────────────────────────────────────────────────────────┤
│  9. UNFAIR ADVANTAGE            │  5. CHANNELS              │  1.  │
│  ────────────────────           │  ────────────             │ CUST │
│                                 │  -                        │ SEGS │
│                                 │  -                        │ ──── │
│                                 │  -                        │      │
│                                 │                           │      │
│                                 │                           │ EA:  │
│                                 │                           │      │
├─────────────────────────────────┴───────────────────────────┴──────┤
│  7. COST STRUCTURE                  │  6. REVENUE STREAMS          │
│  ──────────────────                 │  ────────────────────        │
│  Fixed:                             │  Model:                      │
│                                     │  Price:                      │
│  Variable:                          │                              │
│                                     │  LTV:                        │
│  CAC:                               │  LTV:CAC:                    │
│  Break-even:                        │                              │
└─────────────────────────────────────┴──────────────────────────────┘

Lean Canvas Review Checklist

## Lean Canvas Quality Check

### Completeness
- [ ] All 9 boxes filled
- [ ] Customer segment is specific (not generic)
- [ ] Early adopters identified
- [ ] Problems are customer problems (not your assumptions)
- [ ] Solution maps to problems
- [ ] UVP is clear in one sentence
- [ ] Metrics are measurable

### Quality
- [ ] Problems validated (or marked as hypothesis)
- [ ] Existing alternatives researched (not guessed)
- [ ] Revenue model makes mathematical sense
- [ ] Costs are realistic
- [ ] Unfair advantage is real (or honestly "none yet")

### Risks Identified
- [ ] Top 3 riskiest assumptions documented
- [ ] Validation experiments designed
- [ ] Go/no-go criteria defined

Lean Canvas Versioning Template

## Lean Canvas Evolution Log

### Version 1.0 - [Date]
Initial hypothesis
Key assumptions: [list]

### Version 1.1 - [Date]
**What changed:** [box(es) updated]
**Why:** [evidence/learning that caused change]
**Key assumptions now:** [updated list]

### Version 2.0 - [Date] (Major Pivot)
**What changed:** [customer/problem/solution pivot]
**Why:** [what invalidated previous version]
**New hypothesis:** [summary]

Skill Boundaries

What This Skill Does Well

  • Structuring audio production workflows
  • Providing technical guidance
  • Creating quality checklists
  • Suggesting creative approaches

What This Skill Cannot Do

  • Replace audio engineering expertise
  • Make subjective creative decisions
  • Access or edit audio files directly
  • Guarantee commercial success

References

  • Maurya, Ash. "Running Lean" (2012) - Original Lean Canvas methodology
  • Maurya, Ash. "Scaling Lean" (2016) - Traction roadmap
  • Osterwalder, Alex. "Business Model Generation" (2010) - Original BMC
  • Blank, Steve. "The Startup Owner's Manual" (2012) - Customer Development
  • Ries, Eric. "The Lean Startup" (2011) - Build-Measure-Learn context

Related Skills


Skill Metadata (Internal Use)

name: lean-canvas
category: validation
subcategory: business-model
version: 1.0
author: MKTG Skills
source_expert: Ash Maurya
source_work: Running Lean
difficulty: beginner
estimated_value: $2,000 startup strategy session
tags: [business-model, validation, startups, YC, lean-startup, canvas]
created: 2026-01-25
updated: 2026-01-25

平台分布

Codex

34.71%
按下载量换算247

Claude

28.83%
按下载量换算205

Cursor

20.85%
按下载量换算148

Gemini CLI

9.07%
按下载量换算65

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

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

安装前确认

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

继续浏览同类 Skills