AI Product Strategy Interviewer
PrepLabsAI/InterviewMentor
A VP of Product interviewer that simulates a product strategy interview focused on AI-native products.
Interpret product metrics against goals and surface actionable signals.
Install Product Health Analysis
$ npx skills add mohitagw15856/pm-claude-skills --skill product-health-analysis -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills product-health-analysis --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/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/product-health-analysis .claude/skills/product-health-analysis && 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 "product-health-analysis" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/product-health-analysis into .claude/skills/product-health-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-health-analysis", 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/mohitagw15856/pm-claude-skills/tree/main/skills/product-health-analysisType 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 mohitagw15856/pm-claude-skills --skill product-health-analysis -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills product-health-analysis --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/product-health-analysis .agents/skills/product-health-analysis && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "product-health-analysis" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/product-health-analysis into .agents/skills/product-health-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-health-analysis", 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 mohitagw15856/pm-claude-skills --skill product-health-analysis -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills product-health-analysis --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/product-health-analysis .cursor/skills/product-health-analysis && 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 "product-health-analysis" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/product-health-analysis into .cursor/skills/product-health-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-health-analysis", 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/mohitagw15856/pm-claude-skills.git --path skills/product-health-analysis--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 mohitagw15856/pm-claude-skills --skill product-health-analysis -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills product-health-analysis --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/product-health-analysis .gemini/skills/product-health-analysis && 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 "product-health-analysis" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/product-health-analysis into .gemini/skills/product-health-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-health-analysis", 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 mohitagw15856/pm-claude-skills product-health-analysisInstalls 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 mohitagw15856/pm-claude-skills --skill product-health-analysis -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/product-health-analysis .github/skills/product-health-analysis && 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 "product-health-analysis" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/product-health-analysis into .github/skills/product-health-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-health-analysis", 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 mohitagw15856/pm-claude-skills --skill product-health-analysis -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills product-health-analysis --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/product-health-analysis .opencode/skills/product-health-analysis && 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 "product-health-analysis" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/product-health-analysis into .opencode/skills/product-health-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-health-analysis", 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.
Facts
- Skill name
product-health-analysis- GitHub stars
- 1.4k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 733 words
- Files
- 4 (incl. references)
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Interpret product metrics against goals and surface actionable signals.
- Works in 4 steps: Acquisition — new users, source quality,… → Activation — time to first value,… → Engagement — DAU/MAU, feature adoption,… → …
- Asked to analyse product health
- SKILL.md covers Required Inputs, Metrics Framework, Process and Output Structure, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Product Health Analysis is an agent skill from mohitagw15856/pm-claude-skills. Interpret product metrics against goals and surface actionable signals. Use when asked to analyse product health, review key metrics, investigate a performance issue, produce a health report, or assess product-market fit signals. Produces a structured health report with RAG status, trend analysis, root cause hypotheses, and prioritised actions.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/signal-vs-noise.md`, `references/worked-example.md` and `templates/health-review.md`).
It sits in Product & Project Management, covering Product metrics, Forecasting and time series and Product strategy. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to analyse product health
- Review key metrics
- Investigate a performance issue
- Produce a health report
Example prompts
- “/product-health-analysis”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Acquisition — new users, source quality, CAC trends
- Activation — time to first value, onboarding completion rates
- Engagement — DAU/MAU, feature adoption, session depth
- Retention — D1/D7/D30 retention, churn rate, resurrection rate
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
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.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Product Health Analysis loads about 1.5k tokens when it runs, and up to ~3.6k if it reads all its reference files. Until then it costs about 93 tokens; SKILL.md has 733 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.
Safety
Auto-check passed
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.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 733 words, ~1,458 tokens.
Download SKILL.mdSave it as
.claude/skills/product-health-analysis/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- product-health-analysis
- description
- Interpret product metrics against goals and surface actionable signals. Use when asked to analyse product health, review key metrics, investigate a performance issue, produce a health report, or assess product-market fit signals. Produces a structured health report with RAG status, trend analysis, root cause hypotheses, and prioritised actions.
Product Health Analysis Skill
Transform raw metrics data into a clear health narrative — what's working, what's not, and what needs immediate attention.
Required Inputs
Ask the user for these if not provided:
- Metrics data (current values for key metrics — even rough numbers work)
- Targets or benchmarks (OKR targets, historical baselines, or industry benchmarks)
- Period (week / month / quarter being analysed)
- Product area or segment (are we looking at the whole product or a specific feature?)
Metrics Framework
Analyse across four layers:
- Acquisition — new users, source quality, CAC trends
- Activation — time to first value, onboarding completion rates
- Engagement — DAU/MAU, feature adoption, session depth
- Retention — D1/D7/D30 retention, churn rate, resurrection rate
Process
- For each metric, compare: current period vs. previous period, current vs. target
- Flag anything more than 10% off target as requiring investigation
- Look for correlations — does a drop in activation explain a retention dip 2 weeks later?
- Write a plain-English health summary (no jargon) suitable for sharing with non-data stakeholders
- Recommend top 3 areas for immediate investigation with suggested diagnostic steps
- Validate — Confirm every flagged metric has a plausible root cause hypothesis, not just a raw number, and every recommended action has a specific owner or team
Output Structure
Product Health Report — [Period]
Overall Health: 🟢 On Track / 🟡 Watch / 🔴 Action Required
| Metric | Current | Target | vs. Last Period | Status |
|---|---|---|---|---|
| [metric] | [value] | [target] | [+/-%] | [🟢/🟡/🔴] |
Key Observations: [3-5 bullet observations written in plain English]
Areas Requiring Investigation:
- [Metric + hypothesis + suggested diagnostic]
- [Metric + hypothesis + suggested diagnostic]
- [Metric + hypothesis + suggested diagnostic]
Recommended Actions: [Specific next steps with owners and timelines]
Deeper Materials
This skill ships with support files — use them when they are available:
references/signal-vs-noise.md— Product Health: Separating Signal from Dashboard Noise. Apply it while producing the output; it carries the calibration and judgment calls the method summary above compresses.templates/health-review.md— a fill-in version of the deliverable with the quality gates inline. Offer it when the user wants to work the document themselves rather than have it generated.
Show full SKILL.md (400 more words)Show less
Scoring Rubric (0–40)
Score any output of this skill before handing it over; 32+ is ship-quality.
| Dimension | 0 | 5 | 10 |
|---|---|---|---|
| Target & trend discipline | Metrics shown as bare snapshots; no targets or period-over-period comparison | Most metrics have targets and trends, but some RAG statuses don't follow from the numbers or targets are accepted uncritically | Every metric has target, trend, and a status that follows from both — and at least one target is itself challenged if it's no longer meaningful |
| Root cause depth | Movements listed without explanation ("activation dropped 27pts") | Flagged metrics have hypotheses, but they're generic ("onboarding friction") with no diagnostic to confirm them | Every flagged metric has a specific, falsifiable hypothesis plus a named diagnostic step, and at least one cross-metric correlation (e.g. activation → retention lag) is drawn |
| Segment honesty | Only blended aggregates reported; opposing segment trends invisible | Some segment cuts shown, but the headline observations still lean on averages that hide divergence | Every material aggregate is decomposed where segments diverge, and the divergence itself is surfaced as a finding, not a footnote |
| Verdict & actionability | No overall rating, or a rating asserted without evidence; actions missing or ownerless | Overall RAG present and roughly justified; actions exist but some lack owners, dates, or a link to a flagged metric | Overall rating argued from specific evidence (including against the good news), and every action has a named owner, a date, and traces to an investigation or observation |
Quality Checks
- Every metric includes both a target and a trend (not just a snapshot)
- At least one correlation is drawn between metrics (e.g., activation → retention)
- Every flagged metric has a root cause hypothesis, not just "it dropped"
- Observations are written for a non-technical stakeholder (no raw query language or data jargon)
- Overall health rating is justified with specific evidence
Anti-Patterns
- Do not report a single aggregate metric without segment breakdowns — averages hide opposing trends
- Do not flag a metric as healthy just because it is above the target — check if the target itself is meaningful
- Do not list metric movements without root cause hypotheses — observations without explanations are not analysis
- Do not mix product health metrics with business KPIs without explaining the relationship between them
- Do not omit recommended actions — a health report that only describes problems without prioritised next steps is incomplete
Example Trigger Phrases
- "Analyse product health."
- "Review key metrics."
- "Investigate a performance issue."
- "Produce a health report."
- "Assess product-market fit signals."
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (references) in skills/product-health-analysis of mohitagw15856/pm-claude-skills.
- SKILL.md
- references/signal-vs-noise.md
- references/worked-example.md
- templates/health-review.md
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Product Health Analysis 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 |
|---|---|---|---|---|---|---|
| Product Health Analysis this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.5k | Automated safety check: Pass | MIT | |
| AI Product Strategy InterviewerPrepLabsAI/InterviewMentor | 112 | — | ~4.5k | Automated safety check: Pass | MIT | |
| Investigate MetricPostHog/posthog | 40k | — | ~1.9k | Automated safety check: Pass | Custom licence | |
| Bmad Product Briefaj-geddes/claude-code-bmad-skills | 488 | — | ~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 | |
| Lean Analyticswondelai/skills | 2.4k | — | ~4.2k | Automated safety check: Pass | MIT |
Similar skills
- Official
Investigate Metric
PostHog/posthog
Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries.
Bmad Product Brief
aj-geddes/claude-code-bmad-skills
Lean facilitator for creating, updating, and validating a product brief — the Analysis-phase foundation of the BMAD Method.
SaaS Revenue and Growth Metrics
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.
Lean Analytics
wondelai/skills
Choose and audit startup metrics using Croll and Yoskovitz's "Lean Analytics".
Metrics Review
aAAaqwq/AGI-Super-Team
Review and analyze product metrics with trend analysis and actionable insights.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about Product Health Analysis
What does Product Health Analysis do?
Interpret product metrics against goals and surface actionable signals. Product Health Analysis is an agent skill from mohitagw15856/pm-claude-skills. Interpret product metrics against goals and surface actionable signals.
When should I use Product Health Analysis?
Product Health Analysis fits situations like: asked to analyse product health; review key metrics; investigate a performance issue; produce a health report.
How do I install Product Health Analysis in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill product-health-analysis -a claude-code`. Or copy the skill folder (skills/product-health-analysis in mohitagw15856/pm-claude-skills) into .claude/skills/product-health-analysis in your project. Claude Code loads it when a task matches its description.
How do I install Product Health Analysis in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill product-health-analysis -a codex`. Or copy the skill folder (skills/product-health-analysis in mohitagw15856/pm-claude-skills) into .agents/skills/product-health-analysis in your project. Codex loads it when a task matches its description.
Can I use Product Health Analysis in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill product-health-analysis -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/product-health-analysis, .gemini/skills/product-health-analysis, .github/skills/product-health-analysis and .opencode/skills/product-health-analysis in your project.
What does Product Health Analysis need to run?
SKILL.md names no scripts, command-line tools or credentials: Product Health Analysis is instructions for the agent only.
Does Product Health Analysis access the network?
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.
Is Product Health Analysis safe to install?
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.
What licence does Product Health Analysis use?
Product Health Analysis is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Product Health Analysis use?
About 1.5k tokens (SKILL.md is roughly 5.8k 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 2.2k tokens, read only when the agent opens those files.
What are the alternatives to Product Health Analysis?
Skills that share tags, products or a category with Product Health Analysis: AI Product Strategy Interviewer (PrepLabsAI/InterviewMentor, 112 stars), Investigate Metric (PostHog/posthog, 40k stars), Bmad Product Brief (aj-geddes/claude-code-bmad-skills, 488 stars) and SaaS Revenue and Growth Metrics (deanpeters/Product-Manager-Skills, 7.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Product Health Analysis?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.