Ceos Calendar
bradfeld/ceos
A skill your agent uses when managing the rolling market calendar - conferences, launches, fundraising milestones, partner events, and team constraints
Systematically validate your business hypotheses before building anything.
$ npx skills add guia-matthieu/clawfu-skills --skill customer-discovery -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install guia-matthieu/clawfu-skills customer-discovery --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/guia-matthieu/clawfu-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/validation/customer-discovery .claude/skills/customer-discovery && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "customer-discovery" agent skill from https://github.com/guia-matthieu/clawfu-skills/tree/main/skills/validation/customer-discovery into .claude/skills/customer-discovery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-discovery", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/guia-matthieu/clawfu-skills/tree/main/skills/validation/customer-discoveryType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add guia-matthieu/clawfu-skills --skill customer-discovery -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install guia-matthieu/clawfu-skills customer-discovery --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/guia-matthieu/clawfu-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/validation/customer-discovery .agents/skills/customer-discovery && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "customer-discovery" agent skill from https://github.com/guia-matthieu/clawfu-skills/tree/main/skills/validation/customer-discovery into .agents/skills/customer-discovery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-discovery", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add guia-matthieu/clawfu-skills --skill customer-discovery -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install guia-matthieu/clawfu-skills customer-discovery --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/guia-matthieu/clawfu-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/validation/customer-discovery .cursor/skills/customer-discovery && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "customer-discovery" agent skill from https://github.com/guia-matthieu/clawfu-skills/tree/main/skills/validation/customer-discovery into .cursor/skills/customer-discovery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-discovery", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/guia-matthieu/clawfu-skills.git --path skills/validation/customer-discovery--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add guia-matthieu/clawfu-skills --skill customer-discovery -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install guia-matthieu/clawfu-skills customer-discovery --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/guia-matthieu/clawfu-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/validation/customer-discovery .gemini/skills/customer-discovery && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "customer-discovery" agent skill from https://github.com/guia-matthieu/clawfu-skills/tree/main/skills/validation/customer-discovery into .gemini/skills/customer-discovery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-discovery", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install guia-matthieu/clawfu-skills customer-discoveryInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add guia-matthieu/clawfu-skills --skill customer-discovery -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/guia-matthieu/clawfu-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/validation/customer-discovery .github/skills/customer-discovery && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "customer-discovery" agent skill from https://github.com/guia-matthieu/clawfu-skills/tree/main/skills/validation/customer-discovery into .github/skills/customer-discovery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-discovery", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add guia-matthieu/clawfu-skills --skill customer-discovery -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install guia-matthieu/clawfu-skills customer-discovery --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/guia-matthieu/clawfu-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/validation/customer-discovery .opencode/skills/customer-discovery && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "customer-discovery" agent skill from https://github.com/guia-matthieu/clawfu-skills/tree/main/skills/validation/customer-discovery into .opencode/skills/customer-discovery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-discovery", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
customer-discoverySystematically validate your business hypotheses before building anything.
Customer Discovery is an agent skill from guia-matthieu/clawfu-skills. Systematically validate your business hypotheses before building anything. Master Steve Blank's Customer Development methodology that became the foundation of Lean Startup and YC's approach. Use when: Starting a new venture to avoid building something nobody wants; Before writing a line of code to validate problem-solution fit; Pivoting decisions to systematically test new directions; Early-stage fundraising to prove market validation; Product roadmap planning to prioritiz...
Its SKILL.md is about 5.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including scripts (for example `scripts/main.py`).
It sits in Business, Finance & HR, covering Fundraising and pitch decks and Product roadmapping. The repository describes itself as: 172 expert marketing skills for AI agents — ClawFu MCP Server. The licence is MIT.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 4108f5c. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Ships 2 files in scripts/ (Python), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Customer Discovery loads about 5.3k tokens when it runs. Until then it costs about 130 tokens; SKILL.md has 1,209 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
The full file from guia-matthieu/clawfu-skills at commit 4108f5c, republished under its MIT licence (© guia-matthieu). 1,209 words, ~5,316 tokens.
.claude/skills/customer-discovery/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.Systematically validate your business hypotheses before building anything. Master Steve Blank's Customer Development methodology that became the foundation of Lean Startup and YC's approach.
| Aspect | Details |
|---|---|
| Source | Steve Blank - "The Four Steps to the Epiphany" (2005) |
| Core Principle | "No business plan survives first contact with customers. Get out of the building." |
| Why This Matters | Startups fail because they build products nobody wants. Customer Discovery replaces guessing with systematic learning before you run out of money. |
| Claude Does | You Decide |
|---|---|
| Structures content frameworks | Final messaging |
| Suggests persuasion techniques | Brand voice |
| Creates draft variations | Version selection |
| Identifies optimization opportunities | Publication timing |
| Analyzes competitor approaches | Strategic direction |
I'm starting customer discovery for [business idea].
Help me document my hypotheses and design validation experiments.
Use Steve Blank's Customer Development methodology.Here's what I've learned from [X] customer interviews: [summary]
Evaluate my progress against Customer Discovery criteria.
Should I proceed, pivot, or go back to more interviews?I need to validate this hypothesis: [hypothesis]
Design a Customer Discovery experiment to test it.
What would prove it true? What would prove it false?When helping with Customer Discovery, follow Steve Blank's systematic approach:
## Business Model Canvas Hypotheses
Before talking to customers, document what you BELIEVE to be true.
These are GUESSES until validated.
### Customer Hypotheses
| # | Hypothesis | Confidence | Evidence |
|---|------------|------------|----------|
| C1 | Our target customer is [WHO] | Low/Med/High | [None yet] |
| C2 | They have this problem: [WHAT] | Low/Med/High | [None yet] |
| C3 | The problem is severe because [WHY] | Low/Med/High | [None yet] |
| C4 | They currently solve it by [HOW] | Low/Med/High | [None yet] |
### Value Proposition Hypotheses
| # | Hypothesis | Confidence | Evidence |
|---|------------|------------|----------|
| V1 | Our solution provides [BENEFIT] | Low/Med/High | [None yet] |
| V2 | Customers care about [FEATURE/OUTCOME] | Low/Med/High | [None yet] |
| V3 | We're differentiated by [UNIQUE VALUE] | Low/Med/High | [None yet] |
### Channel Hypotheses
| # | Hypothesis | Confidence | Evidence |
|---|------------|------------|----------|
| H1 | We can reach customers through [CHANNEL] | Low/Med/High | [None yet] |
| H2 | Customer acquisition will cost [ESTIMATE] | Low/Med/High | [None yet] |
### Revenue Hypotheses
| # | Hypothesis | Confidence | Evidence |
|---|------------|------------|----------|
| R1 | Customers will pay [PRICE] | Low/Med/High | [None yet] |
| R2 | Revenue model: [TYPE] | Low/Med/High | [None yet] |
| R3 | Lifetime value: [ESTIMATE] | Low/Med/High | [None yet] |Critical Rule: You don't have a business until these hypotheses are validated with real evidence from real customers.
## Hypothesis Prioritization Matrix
Prioritize by RISK and IMPACT:
| Hypothesis | If WRONG, Impact | Current Confidence | Priority |
|------------|------------------|-------------------|----------|
| [H1] | Fatal/Major/Minor | Low/Med/High | P1/P2/P3 |
| [H2] | Fatal/Major/Minor | Low/Med/High | P1/P2/P3 |
### Priority Rules:
- P1: Fatal if wrong + Low confidence → Validate FIRST
- P2: Major if wrong + Low/Med confidence → Validate SOON
- P3: Minor if wrong OR High confidence → Validate LATER
### Your P1 Hypotheses (Validate These First):
1. ________________________________
2. ________________________________
3. ________________________________
These are your "leap of faith" assumptions.## Experiment Design Template
### Hypothesis Being Tested:
"We believe [CUSTOMER SEGMENT] has [PROBLEM] and would [BEHAVIOR]."
### Experiment Type:
- [ ] Customer Interviews (Problem Discovery)
- [ ] Solution Interviews (Solution Validation)
- [ ] Landing Page Test (Demand Validation)
- [ ] Concierge MVP (Solution Validation)
- [ ] Smoke Test (Demand Validation)
### Success Criteria:
**Validated if:** [Specific, measurable outcome]
**Invalidated if:** [Specific, measurable outcome]
Example:
- Validated: 8+ of 10 customers describe this exact problem unprompted
- Invalidated: Fewer than 5 of 10 mention this problem
### Sample Size:
- Minimum: [Number] customers
- Target segment: [Description]
### Data to Collect:
1.
2.
3.
### Timeline:
- Start: [Date]
- End: [Date]
- Go/No-Go Decision: [Date]## Customer Discovery Interview Framework
### PHASE 1: Problem Discovery (First 5-10 interviews)
**Goal:** Understand the problem space, NOT pitch solutions
**Interview Structure:**
1. **Context** (5 min): Their role, background, day-to-day
2. **Problem Exploration** (15 min): Deep dive into the problem area
3. **Existing Solutions** (5 min): What they use today
4. **Impact** (5 min): How the problem affects them
5. **Wrap-up** (5 min): Referrals, next steps
**Key Questions:**
- "Tell me about your biggest challenge with [area]..."
- "Walk me through the last time you dealt with [problem]..."
- "What solutions have you tried? What worked/didn't work?"
- "How much time/money does this cost you?"
- "If this magically disappeared, what would change?"
**DO NOT:**
- Pitch your solution
- Ask leading questions
- Talk more than 30% of the time
- Ask "would you use/pay for..."
### PHASE 2: Solution Discovery (Next 5-10 interviews)
**Goal:** Test if your solution addresses validated problems
**Only proceed to Phase 2 if:**
- [ ] You've talked to 10+ potential customers
- [ ] Clear problem patterns emerged
- [ ] Problems are severe and frequent enough
- [ ] Customers are actively seeking solutions
**Solution Interview Structure:**
1. **Recap** (3 min): Confirm the problem you heard
2. **Solution Demo** (10 min): Show concept/prototype
3. **Reaction** (10 min): Their honest feedback
4. **Commitment** (5 min): Would they try/buy/refer?
**Key Questions:**
- "Does this solve the problem you described?"
- "What's missing?"
- "What would you pay for this?"
- "Would you be willing to pilot this?"
- "Who else should see this?"## Customer Discovery Scorecard
### Problem Validation
| Criteria | Threshold | Your Result | Pass? |
|----------|-----------|-------------|-------|
| # of interviews completed | 10+ | | Y/N |
| % who confirmed the problem unprompted | 70%+ | | Y/N |
| Problem severity (1-10 avg) | 7+ | | Y/N |
| Already spending money on solutions | 50%+ | | Y/N |
| Actively seeking alternatives | 30%+ | | Y/N |
**Problem Validated:** All Y → Proceed to Solution Validation
**Problem NOT Validated:** Any N → Pivot or dig deeper
### Solution Validation
| Criteria | Threshold | Your Result | Pass? |
|----------|-----------|-------------|-------|
| # of solution interviews | 10+ | | Y/N |
| Said "this solves my problem" | 70%+ | | Y/N |
| Willing to try/pilot | 50%+ | | Y/N |
| Willing to pay (some amount) | 30%+ | | Y/N |
| Gave commitment (deposit, LOI, intro) | 3+ people | | Y/N |
**Solution Validated:** All Y → Proceed to MVP
**Solution NOT Validated:** Any N → Iterate or pivot
### Decision Framework
IF Problem NOT Validated: → PIVOT: Different customer segment? → PIVOT: Different problem? → STOP: No market here?
IF Problem Validated BUT Solution NOT Validated: → ITERATE: Different solution to same problem → ITERATE: Different features/approach
IF Both Validated: → BUILD: Minimum Viable Product → SELL: Pre-sales before building
## Customer Discovery Learning Log
### Round [#] Summary
**Dates:** [Start] - [End]
**Interviews Conducted:** [#]
**Customer Segments Covered:** [List]
### Validated Hypotheses ✅
| Hypothesis | Evidence | Confidence Now |
|------------|----------|----------------|
| [H1] | [Quotes/Data] | High |
### Invalidated Hypotheses ❌
| Hypothesis | Evidence | Next Step |
|------------|----------|-----------|
| [H2] | [Quotes/Data] | Pivot to... |
### Surprises / New Insights 🔍
| Insight | Implication |
|---------|-------------|
| [Learning] | [What this means] |
### Updated Business Model
[What changed based on learnings]
### Next Validation Round
| Hypothesis to Test | Experiment | Timeline |
|--------------------|------------|----------|
| [H3] | [Method] | [Dates] |Context: Founder believes mid-size companies need better employee onboarding software.
Input:
"I want to build HR onboarding software for mid-size companies. Help me set up Customer Discovery."
Output:
Business Model Hypotheses:
| # | Hypothesis | Risk if Wrong | Priority |
|---|---|---|---|
| C1 | HR managers at 100-500 employee companies manage onboarding | Fatal | P1 |
| C2 | Current onboarding is manual, time-consuming (5+ hrs/new hire) | Fatal | P1 |
| C3 | Poor onboarding causes turnover they care about | Fatal | P1 |
| V1 | Automated workflows would save 3+ hours per new hire | Major | P2 |
| V2 | They'd pay $50-100/employee/month for this | Major | P2 |
| H1 | We can reach HR managers through LinkedIn | Minor | P3 |
P1 Validation Plan:
Experiment 1: Problem Discovery
Success Criteria:
Sample Interview Guide:
Opening: "I'm researching how mid-size companies handle employee onboarding.
Not selling anything - just learning. Mind if I ask some questions?"
Problem Exploration:
1. "When you hired your last employee, walk me through the onboarding process..."
2. "What took the most time?"
3. "Where do things typically go wrong?"
4. "Tell me about a time onboarding didn't go well..."
Current State:
5. "What tools or systems are you using for this?"
6. "What do you like about your current process?"
7. "What's frustrating about it?"
Impact:
8. "How does onboarding quality affect employee retention?"
9. "If you could wave a magic wand, what would change?"
Close:
10. "Who else should I talk to about this?"
11. "Can I follow up in a few weeks to share what I'm learning?"Context: Founder wants to build a fitness app for busy parents.
Input:
"I did 12 customer discovery interviews. Here's my summary. Evaluate my progress."
Interview Summary:
Output:
Customer Discovery Evaluation:
| Criteria | Threshold | Your Result | Pass? |
|---|---|---|---|
| Interviews completed | 10+ | 12 | ✅ |
| Problem confirmed unprompted | 70%+ | 83% (10/12) | ✅ |
| Problem severity | 7+ | Unknown | ⚠️ |
| Spending on solutions | 50%+ | 17% (2/12) | ❌ |
| Actively seeking alternatives | 30%+ | Unknown | ⚠️ |
Analysis:
Good Signs:
Warning Signs:
Missing Data:
Diagnosis: Problem validated, but MARKET not validated.
The problem is real (busy parents want to exercise). But evidence suggests:
Recommendation: Go Deeper Before Building
Next 5 interviews, focus on:
Decision: Do not build yet. Either find a more acute pain point within this segment, or find a segment that demonstrates stronger buying behavior.
Context: Founder validated problem but solution bombed.
Input:
"Problem validated: Small business owners hate bookkeeping. But when I showed my automated bookkeeping tool, response was lukewarm. 3 of 10 were excited. Should I pivot?"
Output:
Situation Analysis:
| Phase | Result |
|---|---|
| Problem Discovery | ✅ Validated |
| Solution Discovery | ❌ Failed (30% < 70% threshold) |
Questions Before Pivoting:
Who were the 3 excited customers?
Why were 7 NOT excited?
What specifically was lukewarm?
Pivot Decision Framework:
┌─────────────────────────────────────────────────────────┐
│ SOLUTION FAILED │
│ │
│ Is the problem still validated? │
│ └── YES → Solution Pivot (keep problem, change solution)│
│ │
│ Were some customers excited? │
│ └── YES → Segment Pivot (narrow to excited segment) │
│ │
│ Did feedback suggest different problem? │
│ └── YES → Problem Pivot (keep customer, find new problem)│
│ │
│ Is there any signal at all? │
│ └── NO → Consider stopping or major pivot │
└─────────────────────────────────────────────────────────┘Recommended Next Steps:
Interview the 3 excited customers deeply
Understand the 7 "no"s
Consider these pivots:
Before building anything:
## Before Starting Customer Discovery
### Preparation
- [ ] Business Model Canvas hypotheses documented
- [ ] P1 hypotheses identified (highest risk)
- [ ] Target customer segment defined
- [ ] Interview questions drafted
- [ ] 15+ potential interviews scheduled
### Mindset
- [ ] Committed to learning, not selling
- [ ] Ready to hear "your idea is wrong"
- [ ] Willing to pivot based on evidence
- [ ] No code written yet (or willing to throw away)
### Resources
- [ ] 2-4 weeks allocated for discovery
- [ ] Note-taking system ready
- [ ] Team aligned on validation criteria## Customer Discovery Interview Log
| # | Date | Name | Company | Segment | Problem Confirmed? | Solution Fit? | Commitment? | Key Quote |
|---|------|------|---------|---------|-------------------|---------------|-------------|-----------|
| 1 | | | | | Y/N | Y/N/NA | | |
| 2 | | | | | Y/N | Y/N/NA | | |
| 3 | | | | | Y/N | Y/N/NA | | |
### Running Totals
- Interviews completed: __/15
- Problem confirmed: __%
- Solution fit (if applicable): __%
- Commitments received: __## Customer Discovery Decision Point
**Date:** _______________
**Total Interviews:** _______________
**Hypothesis Being Tested:** _________________________________
### Evidence Summary
| Metric | Target | Actual | Pass? |
|--------|--------|--------|-------|
| Problem confirmation rate | 70%+ | | |
| Average severity score | 7+/10 | | |
| Currently paying for alternatives | 50%+ | | |
| Solution fit (if tested) | 70%+ | | |
| Concrete commitments | 3+ | | |
### Strongest Evidence FOR:
1.
2.
3.
### Strongest Evidence AGAINST:
1.
2.
3.
### Decision
- [ ] **PROCEED:** Build MVP / Start selling
- [ ] **ITERATE:** More interviews needed, adjust approach
- [ ] **PIVOT:** Change [customer/problem/solution]
- [ ] **STOP:** No viable market here
### If Proceeding, Next Steps:
1.
2.
3.
### If Pivoting, New Hypothesis:
name: customer-discovery
category: validation
subcategory: methodology
version: 1.0
author: MKTG Skills
source_expert: Steve Blank
source_work: The Four Steps to the Epiphany
difficulty: intermediate
estimated_value: $5,000 startup consulting engagement
tags: [customer-development, validation, startups, YC, lean-startup, interviews]
created: 2026-01-25
updated: 2026-01-25© guia-matthieu, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 2 other files (scripts) in skills/validation/customer-discovery of guia-matthieu/clawfu-skills.
Open the folder on GitHubat commit 4108f5c
Customer Discovery next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Customer Discovery this skillguia-matthieu/clawfu-skills | 150 | — | ~5.3k | Automated safety check: Pass | MIT | |
| Ceos Calendarbradfeld/ceos | 156 | — | ~2k | Automated safety check: Pass | MIT | |
| Chief Data Officer Advisoralirezarezvani/claude-skills | 28k | — | ~2.9k | Automated safety check: Pass | MIT | |
| Startup Business Analyst Business Caseaiskillstore/marketplace | 433 | 9 repos | ~2.9k | Automated safety check: Notes | None | |
| Prioritizemenkesu/awesome-pm-skills | 434 | — | ~4.6k | Automated safety check: Pass | Custom licence | |
| C Level AdvisorLeoYeAI/openclaw-master-skills | 2.2k | — | ~1.6k | Automated safety check: Pass | MIT |
bradfeld/ceos
A skill your agent uses when managing the rolling market calendar - conferences, launches, fundraising milestones, partner events, and team constraints
alirezarezvani/claude-skills
Chief Data Officer advisory for startups: AI training data rights and consent provenance, data product strategy (warehouse vs lakehouse vs mesh, build-vs-buy), B2B customer-data-as-asset valuation…
aiskillstore/marketplace
Generate comprehensive investor-ready business case document with market, solution, financials, and strategy
menkesu/awesome-pm-skills
Turns a pile of ideas, requests and goals into a confidence-scored roadmap plus a goals/OKR set the team can actually follow.
LeoYeAI/openclaw-master-skills
Provides strategic business advice by channelling the perspectives of 10 executive roles — CEO, CTO, COO, CPO, CMO, CFO, CRO, CISO, CHRO, and Executive Mentor — across decisions, trade-offs, and org…
LeoYeAI/openclaw-master-skills
Decision validation and thinking frameworks for startup founders.
guia-matthieu/clawfu-skills
Calculate A/B test statistical significance. An agent skill from guia-matthieu/clawfu-skills.
guia-matthieu/clawfu-skills
Analyze user retention by cohort. An agent skill from guia-matthieu/clawfu-skills.
guia-matthieu/clawfu-skills
Analyze your competitive landscape using Porter's Five Forces and modern frameworks—understand industry dynamics, identify strategic opportunities, and position your business for sustainable…
guia-matthieu/clawfu-skills
Monitor competitor websites for changes. An agent skill from guia-matthieu/clawfu-skills.
guia-matthieu/clawfu-skills
Transform long-form content into multiple short-form pieces.
guia-matthieu/clawfu-skills
Check email deliverability and DNS configuration. An agent skill from guia-matthieu/clawfu-skills.
Systematically validate your business hypotheses before building anything. Customer Discovery is an agent skill from guia-matthieu/clawfu-skills. Systematically validate your business hypotheses before building anything.
Customer Discovery fits situations like: : Starting a new venture to avoid building something nobody wants; before writing a line of code to validate problem-solution fit; pivoting decisions to systematically test new directions; early-stage fundraising to prove market validation.
Run `npx skills add guia-matthieu/clawfu-skills --skill customer-discovery -a claude-code`. Or copy the skill folder (skills/validation/customer-discovery in guia-matthieu/clawfu-skills) into .claude/skills/customer-discovery in your project. Claude Code loads it when a task matches its description.
Run `npx skills add guia-matthieu/clawfu-skills --skill customer-discovery -a codex`. Or copy the skill folder (skills/validation/customer-discovery in guia-matthieu/clawfu-skills) into .agents/skills/customer-discovery in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add guia-matthieu/clawfu-skills --skill customer-discovery -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/customer-discovery, .gemini/skills/customer-discovery, .github/skills/customer-discovery and .opencode/skills/customer-discovery in your project.
Going by SKILL.md and its folder, Customer Discovery needs Python for the scripts in its folder. Our summary lists: Python 3.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Customer Discovery is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 5.3k tokens (SKILL.md is roughly 21k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Customer Discovery: Ceos Calendar (bradfeld/ceos, 156 stars), Chief Data Officer Advisor (alirezarezvani/claude-skills, 28k stars), Startup Business Analyst Business Case (aiskillstore/marketplace, 433 stars) and Prioritize (menkesu/awesome-pm-skills, 434 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
guia-matthieu (a GitHub user) maintains it in guia-matthieu/clawfu-skills, which has 150 GitHub stars. The repository holds 31 skills in this directory. The repository was last updated on October 1, 2026.
Source: guia-matthieu/clawfu-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.