benchmark-analyst
Marketing benchmark triage skill. Use whenever metrics are shared with questions like "is this good?", "is this normal?", or "should I worry?" — ad metrics, email rates, conversion rates, SaaS metrics, social engagement. Compares the user's numbers against published, sourced benchmarks using panel-matching rules (same platform, model, market, and denominator), refuses folklore stats, and outputs a verdict: which metrics are actually abnormal and which are benchmark anxiety.
npx skills add growthack88/growth-marketing-os --skill benchmark-analyst --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Benchmark Analyst — Claude Skill **By [Mahmoud Omar](https://mahmoudomar.com)** · Install this in Claude (Projects, Skills, or system prompt) — ideally alongside the [benchmarks library](../../benchmarks/) as knowledge files — and "is this number good?" gets a disciplined answer instead of a vibe. ## Core method Every "is X good?" question gets processed through four gates before any verdict: 1. **PANEL MATCH** — identify the user's context (platform, business model, market, company size) and compare only against benchmarks from a matching panel. A Shopify SMB is judged against Littledata medians, not enterprise averages; an opt-in trial against opt-in benchmarks, never opt-out. 2. **DENOMINATOR CHECK** — confirm what the metric is actually measured against (per recipient vs per clicker, per follower vs per impression, placed orders vs delivered orders). If the user's definition is unclear, ask ONCE. 3. **VINTAGE CHECK** — state the year of any benchmark used. Flag anything pre-2024 as dated, and anything AI-search-related older than 6 months as possibly stale. 4. **SOURCE OR SILENCE** — only cite benchmarks traceable to a named study with a sample. If no reliable benchmark exist
- Core method
- Output contract
- Behavior rules
- Example invocation
- 🦆 Built by Mahmoud Omar
What does the benchmark-analyst skill do?
Marketing benchmark triage skill. Use whenever metrics are shared with questions like "is this good?", "is this normal?", or "should I worry?" — ad metrics, email rates, conversion rates, SaaS metrics, social engagement. Compares the user's numbers against published, sourced benchmarks using panel-matching rules (same platform, model, market, and denominator), refuses folklore stats, and outputs a verdict: which metrics are actually abnormal and which are benchmark anxiety.
How do I install it?
Run `npx skills add growthack88/growth-marketing-os --skill benchmark-analyst --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From growthack88/growth-marketing-os, a repository with 70 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.