Individual skill
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.
skills/benchmark-analyst/SKILL.md
Source commit c7852deefb3cd90029f02d328b9e59cea39ef585
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 129
- Repository last updated
- Oct 10, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-marketing Repository topic
- arabic Repository topic
- chatgpt-prompts Repository topic
- claude-skills Repository topic
- cro Repository topic
- custom-gpt Repository topic
- geo Repository topic
- growth Repository topic
- growth-hacking Repository topic
- marketing Repository topic
- marketing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# 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 exists for the question, say exactly that — never fill the gap with a folklore number.
## Output contract