data-analysis-standard

Solid

Structure a product data analysis, metric deep-dive, funnel analysis, or cohort study. Use when asked to analyse product metrics, investigate a drop in conversion, explain a data change to stakeholders, or find the root cause of a metric movement. Produces a structured analysis with question, root cause, confidence level, and recommended action.

Data & Documents 915 stars 165 forks Updated 3 days ago MIT

Install

View on GitHub

Quality Score: 93/100

Stars 20%
99
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Data Analysis Standard Skill Turn raw numbers into product decisions. Structure every analysis with a clear question, methodology, finding, and recommended action. ## Analysis Framework: The 4-Question Method Every analysis starts here: 1. **What changed?** (describe the metric and its movement) 2. **Why did it change?** (root cause — segment, funnel step, cohort, channel) 3. **So what?** (business or product impact) 4. **Now what?** (recommended action with confidence level) Never deliver data without answering all four. A chart with no narrative is not an analysis. --- ## Metric Triage Template Use when a metric has moved unexpectedly: ``` METRIC: [Name] MOVEMENT: [X% change over Y period] BASELINE: [What was normal] SEGMENTATION CHECK: - By platform (iOS / Android / Web)? - By user cohort (new / returning / power users)? - By acquisition channel? - By geography? - By plan/tier? ROOT CAUSE HYPOTHESIS: 1. [Most likely explanation] — Evidence: [data point] 2. [Alternative explanation] — Evidence: [data point] 3. [Ruling out] — Eliminated because: [reason] CONCLUSION: [Single sentence answer to "why did this change?"] CONFIDENCE: [High / Medium / Low] — based on [data available] ``` --- ## Funnel Analysis Structure | Stage | Metric | Current | Benchmark/Target | Drop-off % | Notes | |---|---|---|---|---|---| | [Top of funnel] | [Users] | [N] | [N] | — | | | [Step 2] | [Users] | [N] | [N] | [X%] | | | [Step 3] | [Users] | [N] | [N] | [X%] | | | [Conversion] | [U...

Details

Author
mohitagw15856
Repository
mohitagw15856/pm-claude-skills
Created
4 months ago
Last Updated
3 days ago
Language
Shell
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

product-health-analysis

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.

915 Updated 3 days ago
mohitagw15856
AI & Automation Listed

data-analysis

Performs statistical data analysis, data cleaning, and insight extraction covering KPI calculation, trend analysis, cohort analysis, funnel analysis, and attribution modeling. Use when user asks about data analysis, statistics, KPI, metrics, trend analysis, cohort, funnel analysis, attribution, forecast, 데이터 분석, 지표, 통계, 코호트, or 퍼널.

3 Updated today
Yoodaddy0311
AI & Automation Solid

product-analytics

Use when defining product KPIs, building metric dashboards, running cohort or retention analysis, or interpreting feature adoption trends across product stages.

16,642 Updated yesterday
alirezarezvani
AI & Automation Featured

data-analyst

Data exploration and analysis partner for Product Managers. Use when the user needs to query databases, analyze metrics, create dashboards, or extract insights from data. Triggers include "query", "analyze data", "metrics", "BigQuery", "SQL", "dashboard", "what does the data say", or when working with quantitative information.

2,266 Updated today
jeremylongshore
AI & Automation Listed

metrics-briefing

CEO-level metrics interpretation through 9-category framework (market learning, product value, usage, pipeline, retention, B2C->B2B, execution, economics, PMF). For raw analytics data queries, use your analytics skill (e.g., posthog-analytics) instead.

0 Updated today
Layneformalized225