Product Strategist
alirezarezvani/claude-skills
OKR cascade toolkit for product leaders: generates aligned company-to-team OKRs from five strategy types and scores how well they line up.
Choose and audit startup metrics using Croll and Yoskovitz's "Lean Analytics".
$ npx skills add wondelai/skills --skill lean-analytics -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install wondelai/skills lean-analytics --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/wondelai/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/lean-analytics .claude/skills/lean-analytics && 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 "lean-analytics" agent skill from https://github.com/wondelai/skills/tree/main/lean-analytics into .claude/skills/lean-analytics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lean-analytics", 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/wondelai/skills/tree/main/lean-analyticsType 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 wondelai/skills --skill lean-analytics -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install wondelai/skills lean-analytics --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wondelai/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/lean-analytics .agents/skills/lean-analytics && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "lean-analytics" agent skill from https://github.com/wondelai/skills/tree/main/lean-analytics into .agents/skills/lean-analytics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lean-analytics", 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 wondelai/skills --skill lean-analytics -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install wondelai/skills lean-analytics --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wondelai/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/lean-analytics .cursor/skills/lean-analytics && 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 "lean-analytics" agent skill from https://github.com/wondelai/skills/tree/main/lean-analytics into .cursor/skills/lean-analytics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lean-analytics", 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/wondelai/skills.git --path lean-analytics--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 wondelai/skills --skill lean-analytics -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install wondelai/skills lean-analytics --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wondelai/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/lean-analytics .gemini/skills/lean-analytics && 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 "lean-analytics" agent skill from https://github.com/wondelai/skills/tree/main/lean-analytics into .gemini/skills/lean-analytics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lean-analytics", 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 wondelai/skills lean-analyticsInstalls 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 wondelai/skills --skill lean-analytics -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/wondelai/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/lean-analytics .github/skills/lean-analytics && 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 "lean-analytics" agent skill from https://github.com/wondelai/skills/tree/main/lean-analytics into .github/skills/lean-analytics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lean-analytics", 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 wondelai/skills --skill lean-analytics -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install wondelai/skills lean-analytics --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wondelai/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/lean-analytics .opencode/skills/lean-analytics && 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 "lean-analytics" agent skill from https://github.com/wondelai/skills/tree/main/lean-analytics into .opencode/skills/lean-analytics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lean-analytics", 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.
lean-analyticsChoose and audit startup metrics using Croll and Yoskovitz's "Lean Analytics".
Lean Analytics is an agent skill from wondelai/skills. Choose and audit startup metrics using Croll and Yoskovitz's "Lean Analytics". Use when the user mentions "what metrics should we track", "KPIs", "north star metric", "One Metric That Matters (OMTM)", "vanity metrics", "analytics dashboard", "DAU/MAU", "churn benchmark", or "measure product-market fit". Also trigger when choosing metrics for a startup or feature, auditing a dashboard for vanity metrics, setting metric targets and baselines, or instrumenting a product by business model and stage. Covers…
Its SKILL.md is about 4.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `references/business-model-metrics.md`, `references/case-studies.md` and `references/five-stages.md`).
It sits in Product & Project Management, covering Product strategy, OKRs and executive reporting and Product metrics. The repository describes itself as: Wondel.ai Agent Skills — Business, Marketing, UX & Coding Frameworks from Bestselling Books. 50 skills + 12 guided journeys for Claude Code, Codex, Cursor & other agentskills.io… The licence is MIT.
5 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit c172996. 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.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
amazon.comFrom 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.
Lean Analytics loads about 4.2k tokens when it runs, and up to ~21k if it reads all its reference files. Until then it costs about 189 tokens; SKILL.md has 2,266 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); files beside SKILL.md are not scanned.
The full file from wondelai/skills at commit c172996, republished under its MIT licence (© wondelai). 2,266 words, ~4,235 tokens.
.claude/skills/lean-analytics/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.A data discipline for startups distilled from Alistair Croll and Benjamin Yoskovitz's Lean Analytics: separate metrics that change decisions from numbers that merely flatter, then point the whole company at the One Metric That Matters for your business model and stage. Use it to choose metrics, audit dashboards, set targets, and plan instrumentation.
Focus on the one metric that matters right now — everything else is noise that feels like progress. Startups die from lack of focus more often than lack of data. The discipline is knowing your business model, knowing your stage, and tracking the single number that tells you whether the riskiest part of the business is working. A metric earns attention only if it changes what you do next.
Goal: 10/10. Rate metric choices, dashboards, and instrumentation plans 0-10 against these principles. Report the current score and the specific changes needed to reach 10/10.
Core concept: A good metric is comparative (versus last week, versus another cohort), understandable (the team can recall and debate it), a ratio or rate (not an ever-growing total), and behavior-changing — if a number won't change what you do, stop measuring it. Vanity metrics — total signups, page views, cumulative anything — only go up and only make you feel good.
Why it works: The output of analytics is decisions, not data. Ratios are inherently comparative and operable, while totals hide decay: total registered users rises even while the product bleeds actives. Forcing every metric through the "what will we do differently?" test converts reporting into learning.
Key insights:
Applications:
| Context | Application | Example |
|---|---|---|
| Dashboard audit | Rewrite each total as a ratio | Total signups → % of visitors activating within 7 days |
| Board reporting | Show cohorts, not cumulative curves | Retention by signup month replaces "users over time" |
| Feature decision | Demand a behavior-changing metric | "If D7 retention doesn't rise 10%, the feature comes out" |
See references/good-metrics.md when auditing a dashboard or running a metric through the four tests — full test definitions, the 10-row vanity rewrite table, a worked cohort-retention example, segmentation rules, the correlation-to-causation experiment loop, and a metric-definition template.
Core concept: At any moment there is one number that matters above all others — the one that tells you whether the current riskiest assumption is working. Pick it, display it everywhere, and let it drive every experiment until you graduate to the next stage.
Why it works: The OMTM answers the most important question you have right now, forces you to draw a line in the sand so "good" is defined before results arrive, and focuses the entire company. A dashboard of forty numbers diffuses accountability; one number creates a shared scoreboard and a culture of experimentation.
Key insights:
Applications:
| Context | Application | Example |
|---|---|---|
| Quarterly planning | One OMTM per stage; experiments ladder up to it | Stickiness stage → all bets target week-4 retention |
| Dashboard design | OMTM big, 4-6 supporting metrics small | Wall display: paid conversion 3.2% huge; CAC, churn, NPS below |
| Team alignment | Pre-commit the miss response | "Under 10% by March 1 → we pivot to the agency segment" |
Ethical boundary: The line in the sand disciplines the company's bets, not individuals — turning the OMTM into personal quotas invites gaming and hides truth.
See references/omtm.md when choosing or rotating the OMTM, pairing a counter-metric, or drawing the line in the sand — the six-step selection procedure, the 6x3 stage x model matrix, a 7-row counter-metric gaming table, line-in-the-sand and rotation-trigger rules, and three worked examples.
Core concept: Your business model dictates which metrics exist and which matter. Lean Analytics defines six archetypes — e-commerce, SaaS, free mobile app, media site, user-generated content, and two-sided marketplace — each with its own metric tree and its own definition of "working."
Why it works: Copying another company's north star fails because metrics encode the mechanics of a model: a marketplace lives or dies on liquidity, a SaaS business on churn, a media site on engaged attention. Naming your model first turns "what should we measure?" from a brainstorm into a lookup.
Key insights:
Applications:
| Context | Application | Example |
|---|---|---|
| New product instrumentation | Name the model, install its metric tree | Subscription box → primary model SaaS; churn tracked before AOV |
| North-star debate | Derive from model mechanics, don't copy | Marketplace adopts fill rate, not a SaaS-style MRR target |
| Investor dashboard | Report the model's canonical ratios | SaaS deck: MRR growth, net churn, LTV:CAC, CAC payback |
See references/business-model-metrics.md when instrumenting a product or picking a model's canonical ratios — metric trees for all six models with formulas, instrumentation notes, measurement failure modes, and hybrid-model guidance.
Core concept: Startups move through five stages — Empathy, Stickiness, Virality, Revenue, Scale — and each has a gate. The OMTM is the intersection of business model and current stage; working on a later stage's metric before passing the current gate is the canonical startup mistake.
Why it works: Sequencing prevents waste. Virality poured into a product that doesn't retain is a leaky bucket; paid acquisition before unit economics burns runway with precision. Each gate de-risks the next, larger investment of money and time.
Key insights:
Applications:
| Context | Application | Example |
|---|---|---|
| Growth-spend decision | Check the stickiness gate first | D30 retention at 4% → fix onboarding before buying ads |
| Roadmap prioritization | Stage picks the OMTM; OMTM picks the work | Stickiness stage ships onboarding fixes, not a referral program |
| Fundraising narrative | Pitch the passed gate and its evidence | "Week-4 retention flat at 35% — raising to scale acquisition" |
See references/five-stages.md when locating your stage or deciding whether you've passed a gate — the per-stage playbook with gating metrics, exit-criteria checklists, premature-scaling symptoms, and funding/runway interactions.
Core concept: A metric without a target is trivia. Use published baselines as starting heuristics — not laws — to define "good enough," then draw your line in the sand: a number, a date, and a pre-committed action if you miss.
Why it works: Baselines convert open-ended measurement into falsifiable bets. Knowing that ~5% monthly churn is the early-SaaS ceiling tells you whether to optimize or rebuild; without a line, every result can be rationalized and no experiment can fail.
Key insights:
Applications:
| Context | Application | Example |
|---|---|---|
| Target setting | Baseline → line in the sand → pre-commitment | "Churn under 4% by Q3 or we rebuild onboarding" |
| Anomaly triage | Compare to your own baseline before benchmarks | Conversion fell 2.4% → 1.9% in a week — investigate the release |
| Channel evaluation | Re-derive benchmarks per channel | Paid social converts 0.8%, search 4% — budget follows the line |
See references/case-studies.md when you want a full worked walkthrough — three scenarios: SaaS dashboard to OMTM, marketplace liquidity discovery, and a mobile app fixing stickiness before growth.
| Mistake | Why It Fails | Fix |
|---|---|---|
| A dashboard with 40 metrics | Diffuses focus; nobody owns anything | One OMTM big, 4-6 supporting metrics, archive the rest |
| Celebrating cumulative charts | Totals can't go down, so they hide decay | Plot rates, conversions, and cohort retention instead |
| Copying another company's north star | Metrics encode model mechanics you don't share | Derive the OMTM from your model × stage |
| Skipping cohorts | Blended averages mask whether the product improves | Track each signup cohort separately over time |
| Optimizing virality before stickiness | Growth multiplies churn — the leaky bucket | Pass the retention gate, then build invite loops |
| Measuring what's easy, not what's risky | Decisions still get made on gut | Instrument the riskiest assumption first |
| No line in the sand | Every result gets rationalized; experiments can't fail | Pre-commit target, date, and miss response |
| Confusing correlation with causation | You pump a metric that doesn't drive the outcome | Run a controlled experiment before investing |
| Question | If No | Action |
|---|---|---|
| Can you name your OMTM right now? | Focus is diffused across a dashboard | Pick one metric from current model × stage |
| Would this metric change what you do next? | You're reporting, not deciding | Drop it, or define the decision it gates |
| Is it a ratio or rate, not a total? | Vanity risk — totals only go up | Rewrite as a conversion, retention, or per-user rate |
| Do you know your business model archetype? | Wrong metric tree installed | Name one of the six models; adopt its metrics |
| Do you know your stage (Empathy → Scale)? | Probably optimizing a later stage too early | Find the first unpassed gate; that's your stage |
| Is there a target with a date and a miss plan? | Goalposts will move after results | Draw the line in the sand in writing |
| Is the data cohorted and segmented? | Averages are hiding the truth | Build cohort tables; split by channel and segment |
| Is a counter-metric guarding the OMTM? | The OMTM will be gamed | Pair it, e.g. signup growth × 30-day retention |
Alistair Croll is an entrepreneur and analyst who co-founded web performance company Coradiant, founded Solve For Interesting, and chairs Startupfest among other technology conferences. Benjamin Yoskovitz is a founding partner at venture studio Highline Beta and a serial founder and startup investor. They wrote Lean Analytics for Eric Ries's Lean Series.
© wondelai, 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 5 other files (references) in lean-analytics of wondelai/skills.
Open the folder on GitHubat commit c172996
Lean Analytics 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 |
|---|---|---|---|---|---|---|
| Lean Analytics this skillwondelai/skills | 2.4k | — | ~4.2k | Automated safety check: Pass | MIT | |
| Product Strategistalirezarezvani/claude-skills | 28k | 2 repos | ~1.8k | Automated safety check: Pass | MIT | |
| Team OKR Brainstormphuryn/pm-skills | 27k | — | ~1.1k | Automated safety check: Pass | MIT | |
| AI Product Strategy InterviewerPrepLabsAI/InterviewMentor | 112 | — | ~4.5k | Automated safety check: Pass | MIT | |
| Bmad Product Briefaj-geddes/claude-code-bmad-skills | 487 | — | ~1.7k | Automated safety check: Notes | Custom licence | |
| SaaS Revenue and Growth Metricsdeanpeters/Product-Manager-Skills | 7.2k | 1 repos | ~5.8k | Automated safety check: Pass | Custom licence |
alirezarezvani/claude-skills
OKR cascade toolkit for product leaders: generates aligned company-to-team OKRs from five strategy types and scores how well they line up.
phuryn/pm-skills
Drafts three alternative sets of team OKRs, each with an inspiring objective and measurable key results, tied to the company strategy you provide.
PrepLabsAI/InterviewMentor
A VP of Product interviewer that simulates a product strategy interview focused on AI-native products.
aj-geddes/claude-code-bmad-skills
Lean facilitator for creating, updating, and validating a product brief — the Analysis-phase foundation of the BMAD Method.
deanpeters/Product-Manager-Skills
Explains and calculates SaaS revenue, retention and growth metrics such as MRR, ARPU, GRR and NRR, to read momentum, churn and product-market-fit signals.
phuryn/pm-skills
Designs a product metrics dashboard: a North Star and input metrics, a definition table with data sources, chart types and alert thresholds, and a screen layout.
wondelai/skills
Navigate the technology adoption lifecycle from early adopters to mainstream market.
wondelai/skills
Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models.
wondelai/skills
Run a structured 5-day process to prototype, test, and validate product ideas with real users.
wondelai/skills
Design habit-forming product loops using the Hook Model (Trigger, Action, Variable Reward, Investment).
wondelai/skills
Diagnose and fix retention problems using behavior design (B=MAP).
wondelai/skills
Design products and pricing around validated willingness to pay, from Ramanujam & Tacke's "Monetizing Innovation".
Categories
Choose and audit startup metrics using Croll and Yoskovitz's "Lean Analytics". Lean Analytics is an agent skill from wondelai/skills. Choose and audit startup metrics using Croll and Yoskovitz's "Lean Analytics".
Lean Analytics fits situations like: the user mentions what metrics should we track; north star metric; one Metric That Matters (OMTM); analytics dashboard.
Run `npx skills add wondelai/skills --skill lean-analytics -a claude-code`. Or copy the skill folder (lean-analytics in wondelai/skills) into .claude/skills/lean-analytics in your project. Claude Code loads it when a task matches its description.
Run `npx skills add wondelai/skills --skill lean-analytics -a codex`. Or copy the skill folder (lean-analytics in wondelai/skills) into .agents/skills/lean-analytics 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 wondelai/skills --skill lean-analytics -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lean-analytics, .gemini/skills/lean-analytics, .github/skills/lean-analytics and .opencode/skills/lean-analytics in your project.
SKILL.md names no scripts, command-line tools or credentials: Lean Analytics is instructions for the agent only.
SKILL.md names 1 domain. As links in the text: amazon.com. 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. Review the folder before installing.
Lean Analytics is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 4.2k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 17k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Lean Analytics: Product Strategist (alirezarezvani/claude-skills, 28k stars), Team OKR Brainstorm (phuryn/pm-skills, 27k stars), AI Product Strategy Interviewer (PrepLabsAI/InterviewMentor, 112 stars) and Bmad Product Brief (aj-geddes/claude-code-bmad-skills, 487 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
wondelai (a GitHub organization) maintains it in wondelai/skills, which has 2,356 GitHub stars. The repository holds 61 skills in this directory. The repository was last updated on September 10, 2026.
Source: wondelai/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.