analyze-metrics

analyze-metrics is a skill for Claude Code from samkawsarani/sams-product-plugins. It costs 95 tokens per session (1,256 once invoked), scanned A, original, MIT.

A product-data analysis skill for finding patterns in usage, adoption, conversion, retention, revenue, and payment data. It can apply common product-management methods such as funnel and cohort analysis.

In plain words
What is it for?
Use it to assess feature adoption, conversion funnels, customer retention, revenue, payments, or other product metrics.
Why use it?
It helps turn raw CSV, spreadsheet, database, or query results into calculated measures, trends, problems, and suggested actions.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the analyze-metrics plugin — 1 skill shipped together

Good fit Use it to assess feature adoption, conversion funnels, customer retention, revenue, payments, or other product metrics.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/samkawsarani/sams-product-plugins/analyze-metrics
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add samkawsarani/sams-product-plugins --skill analyze-metrics
Clone the repo
git clone --depth 1 https://github.com/samkawsarani/sams-product-plugins

Made for: Claude Code.

Or install analyze-metrics, the plugin that ships this one along with the rest of its 1 skill.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for analyze-metrics

README.md
[![agentmods](https://agentmods.dev/badge/skills/samkawsarani/sams-product-plugins/analyze-metrics/github.svg)](https://agentmods.dev/skills/samkawsarani/sams-product-plugins/analyze-metrics)
Your own site
<a href="https://agentmods.dev/skills/samkawsarani/sams-product-plugins/analyze-metrics"><img src="https://agentmods.dev/badge/skills/samkawsarani/sams-product-plugins/analyze-metrics/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for analyze-metrics

Your own site · 80×15
<a href="https://agentmods.dev/skills/samkawsarani/sams-product-plugins/analyze-metrics"><img src="https://agentmods.dev/badge/skills/samkawsarani/sams-product-plugins/analyze-metrics.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 95 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,256 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00095 $0.01256
Opus 5 $0.00048 $0.00628
Sonnet 5 $0.00019 $0.00251
Haiku 4.5 $0.00010 $0.00126

Measured 11d ago against content hash 893b558e70a4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

analyze-metrics scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/calculate_metrics.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/analyze-metrics/skills/analyze-metrics/SKILL.md · 126 lines

How it starts

The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Dependency Check

Before starting, verify required dependencies:

  1. python3 (required): Run command -v python3.
    • If missing: Tell the user: "Python 3 is required to run metric calculation scripts. Install it with brew install python or brew install uv && uv python install, then try again." Stop here.

Product Metrics Analysis

Analyze product data to surface insights, identify patterns, and provide actionable recommendations. Apply appropriate PM frameworks based on the question and data at hand.

Core Capabilities

  1. Pattern Recognition - Identify trends, anomalies, and insights in product data
  2. Framework Application - Apply AARRR, North Star, PMF metrics, or cohort analysis as appropriate
  3. Metric Calculation - Calculate growth rates, conversion rates, retention, and other key metrics
  4. Actionable Insights - Surface specific, concrete recommendations based on the data

Analysis Workflow

1. Understand the Context

Before diving into data, clarify:

  • What question is being asked?
  • What type of data is available?
  • What time period or cohorts are relevant?
  • What product/feature is being analyzed?

2. Choose the Right Framework

Select the framework that best fits the question:

  • AARRR (Pirate Metrics) - For full-funnel analysis or identifying bottlenecks
  • Product-Market Fit Metrics - For evaluating early traction or new feature adoption
  • Cohort Analysis - For understanding retention or behavior over time
  • North Star Framework - For strategic alignment or prioritization decisions

→ Read references/frameworks.md for detailed framework guidance and when to use each.

3. Calculate Metrics

Use scripts/calculate_metrics.py for common calculations:

# Core product metrics
python scripts/calculate_metrics.py growth_rate <old_value> <new_value>
python scripts/calculate_metrics.py conversion_rate <conversions> <total>
python scripts/calculate_metrics.py retention_rate <active_users> <cohort_size>
python scripts/calculate_metrics.py churn_rate <churned_users> <starting_users>
python scripts/calculate_metrics.py dau_mau_ratio <dau> <mau>
python scripts/calculate_metrics.py ltv <arpu> <churn_rate>
python scripts/calculate_metrics.py ltv_cac_ratio <ltv> <cac>
python scripts/calculate_metrics.py arpu <total_revenue> <total_users>
python scripts/calculate_metrics.py funnel <step1> <step2> <step3> ...

# Fintech/Payments metrics
python scripts/calculate_metrics.py take_rate <revenue> <tpv>
python scripts/calculate_metrics.py payment_acceptance_rate <approved> <total_attempts>
python scripts/calculate_metrics.py chargeback_rate <chargebacks> <total_transactions>
python scripts/calculate_metrics.py atv <tpv> <num_transactions>
python scripts/calculate_metrics.py fraud_rate <fraudulent> <total_transactions>
python scripts/calculate_metrics.py net_revenue <gross_revenue> <processing_fees> <chargebacks> <refunds>

Read the full file on GitHub · 126 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 126 lines · 95 tokens per session scan A 893b558e70a4

Subscribe to this mod's changes

analyze-metrics is a skill published in the GitHub repository samkawsarani/sams-product-plugins (2 stars, last pushed 1mo ago), licensed MIT. It adds 95 tokens to every session and 1,256 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens