agentleFS
Natan-MohartNatan-Mohart/24-finance-skills-for-claude/skills/peer-benchmarking/SKILL.md

peer-benchmarking

Skill15 starsChanged 3 months agoMITView on GitHub

Compares a company's key financial ratios against true peer medians and quartiles, flagging which peers were excluded and why, so the read is defensible rather than a single flattering comparison. Use whenever the user wants to benchmark a company against competitors, needs a peer comparison for a board deck or investor update, or has a benchmarking claim with no stated peer set or exclusion logic behind it.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    State exclusions explicitly: If a company in the obvious peer group is excluded (different fiscal year, recent M&A distorting the numbers, …

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Peer Benchmarking

When to use

Use whenever a performance claim needs external context, "our margin is strong" means nothing without knowing what peers actually post, or when preparing a board or investor update that will get challenged on comparability. Also use to check a benchmarking claim someone else made, where the peer set and exclusions were never stated.

What it does

Builds a defensible peer comparison: a real peer set (not cherry-picked), calendarized to the same period, with median and quartile ranges per metric, and an explicit note on which companies were excluded and why. The output is a range with a position in it, not a single flattering number lifted from the best comparison available.

Method

  1. Define the peer set by real comparability criteria — similar business model, similar scale (revenue or headcount band), similar growth stage, similar geography — not just "companies in the same industry label."
  2. State exclusions explicitly. If a company in the obvious peer group is excluded (different fiscal year, recent M&A distorting the numbers, private and unreported), name it and why. An unexplained exclusion is exactly how benchmarking gets cherry-picked.
  3. Calendarize before comparing. Companies with different fiscal year ends are not directly comparable on a raw calendar-quarter basis — align to trailing twelve months or the nearest common period.
  4. Compute median and quartile range per metric, not just an average — an average can be dragged by one outlier peer; the quartile range shows where the real distribution sits.
  5. Place the subject company's actual number inside that range and state the percentile plainly: "24th percentile on gross margin" is a finding; "below average" is not.
  6. Separate metrics where the company is structurally different (different revenue recognition, different capital intensity) — flag these instead of forcing a comparison that isn't apples-to-apples.
  7. State what the benchmark implies for action, not just where the company sits — a bottom-quartile metric with a plausible structural explanation needs different follow-up than one with no explanation at all.

Inputs

  • The company's own financials for the metrics being benchmarked
  • Candidate peer companies with comparability rationale
  • Peer financial data (public filings, industry surveys, or available comparables)
  • The specific metrics that matter for this comparison

Output format

Peer set with comparability rationale; explicit exclusion list with reasons; calendarized metric table; median and quartile range per metric; subject company's percentile position per metric; a plain read on what the position implies.

Example

A SaaS company claims "our gross margin beats the industry" citing one hand-picked competitor. Rebuilding the peer set with eight comparable companies (similar ARR band, similar go-to-market motion) calendarized to trailing twelve months shows the company actually sits at the 40th percentile, not top of class — the original claim relied on comparing against the one peer with unusually low margin, not a representative set.

Common pitfalls

  • Comparing against whichever peer happens to look most favorable instead of a defensible, stated peer set.
  • Averaging instead of showing the quartile range, hiding how spread out the real comparison actually is.
  • Comparing raw numbers across different fiscal year ends without calendarizing first.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.