/cs-pmf-check
/cs:pmf-check — Are you before or after product/market fit? A focused Andreessen-mode interrogation that scores the felt signals + the Sean Ellis 40% gate and issues BEFORE-PMF / APPROACHING-PMF / AFTER-PMF with explicit confidence and a single next move.
$ npx -y skills add alirezarezvani/claude-skills --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/cs-pmf-check
Context preview
What this command does when you run it.
/cs:pmf-check — Are you before or after product/market fit? A focused Andreessen-mode interrogation that scores the felt signals + the Sean Ellis 40% gate and issues BEFORE-PMF / APPROACHING-PMF / AFTER-PMF with explicit confidence and a single next move.
Command definition
cs-pmf-check.mdname: "cs-pmf-check"
description: "/cs:pmf-check — Are you before or after product/market fit? A focused Andreessen-mode interrogation that scores the felt signals + the Sean Ellis 40% gate and issues BEFORE-PMF / APPROACHING-PMF / AFTER-PMF with explicit confidence and a single next move."
/cs:pmf-check — Product/Market Fit Interrogation
**Command:** `/cs:pmf-check`
A focused slice of the `cs-andreessen` persona aimed at one question: are you before or after product/market fit? Per Andreessen, PMF is the only milestone that matters and it is **not subtle** — if you have to squint to see it, you don't have it.
When to Run
- "Are we at product/market fit?"
- You're deciding whether to scale (spend on growth/sales) or keep iterating on the product.
- You're tempted to raise/hire/expand and want a hard read on whether the fit is real first.
What You Get
A focused interrogation, then a deterministic verdict:
1. **The felt-signal test** (Andreessen): are customers buying as fast as you can make it? Is usage growing as fast as you can add servers? Is money piling up? Are you hiring support as fast as you can? 2. **The Sean Ellis 40% gate** (Ellis, not Andreessen): do ≥40% of users say they'd be "very disappointed" without you? 3. **Verdict:** `BEFORE-PMF` / `APPROACHING-PMF` / `AFTER-PMF` + explicit confidence. 4. **One next move:** before PMF → what to change (product/segment/team). After PMF → pour fuel, stop deliberating, feed demand.
Discipline
- **PMF is not subtle.** "Approaching" is the honest verdict for warm-but-ambiguous signals; don't
inflate it to "after."
- **Retention is the strongest single signal.** A leaky bucket means you are before PMF no matter
how good acquisition looks.
- **Label the Ellis test as Ellis's, not Andreessen's.** Confidence levels mandatory.
- **No capitulation** to wishful reads without new evidence.
Workflow
python ../skills/andreessen/scripts/pmf_signal_scorer.py \
--ellis-pct 45 --retention 8 --organic 7 --demand 8 --frequency 7
Related
- Agent: [`cs-andreessen`](../agents/cs-andreessen.md)
- Skill: [`andreessen`](../skills/andreessen/SKILL.md)
- Parent command: [`/cs:andreessen`](./cs-andreessen.md)
---
**Version:** 1.0.0
Read more
name: "cs-pmf-check" description: "/cs:pmf-check — Are you before or after product/market fit? A focused Andreessen-mode interrogation that scores the felt signals + the Sean Ellis 40% gate and issues BEFORE-PMF / APPROACHING-PMF / AFTER-PMF with explicit confidence and a single next move."
/cs:pmf-check — Product/Market Fit Interrogation
**Command:** `/cs:pmf-check`
A focused slice of the `cs-andreessen` persona aimed at one question: are you before or after product/market fit? Per Andreessen, PMF is the only milestone that matters and it is **not subtle** — if you have to squint to see it, you don't have it.
When to Run
- "Are we at product/market fit?"
- You're deciding whether to scale (spend on growth/sales) or keep iterating on the product.
- You're tempted to raise/hire/expand and want a hard read on whether the fit is real first.
What You Get
A focused interrogation, then a deterministic verdict:
1. **The felt-signal test** (Andreessen): are customers buying as fast as you can make it? Is usage growing as fast as you can add servers? Is money piling up? Are you hiring support as fast as you can? 2. **The Sean Ellis 40% gate** (Ellis, not Andreessen): do ≥40% of users say they'd be "very disappointed" without you? 3. **Verdict:** `BEFORE-PMF` / `APPROACHING-PMF` / `AFTER-PMF` + explicit confidence. 4. **One next move:** before PMF → what to change (product/segment/team). After PMF → pour fuel, stop deliberating, feed demand.
Discipline
- **PMF is not subtle.** "Approaching" is the honest verdict for warm-but-ambiguous signals; don't
inflate it to "after."
- **Retention is the strongest single signal.** A leaky bucket means you are before PMF no matter
how good acquisition looks.
- **Label the Ellis test as Ellis's, not Andreessen's.** Confidence levels mandatory.
- **No capitulation** to wishful reads without new evidence.
Workflow
python ../skills/andreessen/scripts/pmf_signal_scorer.py \ --ellis-pct 45 --retention 8 --organic 7 --demand 8 --frequency 7
Related
- Agent: [`cs-andreessen`](../agents/cs-andreessen.md)
- Skill: [`andreessen`](../skills/andreessen/SKILL.md)
- Parent command: [`/cs:andreessen`](./cs-andreessen.md)
---
**Version:** 1.0.0
362 production-ready Claude Code skills, plugins, and agent skills for 13 AI coding tools. The most comprehensive open-source library of Claude Code skills and agent plugins — also works with OpenAI Codex, Gemini CLI, Cursor, and 9 more coding agents.
Repo: alirezarezvani/claude-skills
Other commands on claude-skills.
- /focused-fix
Deep-dive feature repair — systematically fix an entire feature/module across all its files and dependencies. Usage: /focused-fix <feature-path>
Open command - /clean
Clean up merged branches locally and on remote, keeping only main, dev, and gh-pages.
Open command - /cm
Stage working tree changes and create a Conventional Commit (no push).
Open command - /cp
Stage, commit, and push the current branch following git governance rules.
Open command - /pr
Create a pull request from the current branch.
Open command - /plugin-audit
Comprehensive audit pipeline for skills, plugins, agents, and commands. Validates structure, quality, security, marketplace compliance, cross-platform compatibility, and ecosystem integration. Runs all built-in validation tools, invokes domain-appropriate agents for code review,
Open command