Claude Skill MartBrowse skillsWhat is a Skill?
Back to list

Benchmark Due Diligence

Runs an adversarial teardown of a founder, KOL, company, or product you envy — separating marketing bubble from real signal and mapping the validated playbook onto your own resources.

Data & AnalyticsAdvanced1,323212AI score 8/10Last updated: Aug 8, 2026

What it does

Instead of a neutral briefing, this skill assumes the benchmark's story is inflated until proven otherwise, then runs a four-phase orchestration:

  • Phase 0 — foundation by evidence: never infer ownership from shared names or domains; verify the real entity graph and, above all, the attribution of the headline stat ("took product X from 0 → 1M users" — founder, or the growth lead who left?). It also separates what you actually own from what merely belongs to your clients.
  • Phase 1+2 — collect → verify pipeline: parallel collection agents attach a source URL and source_kind (self-reported/marketing vs independent third party) to every finding; adversarial verification agents grade evidence L1–L4 and issue verdicts (confirmed / mostly credible / doubtful / debunked-bubble), actively hunting falsifying evidence.
  • Phase 3 — attribution breakdown: what share of the success is product vs market timing vs personal-IP marketing vs operations, with explicit separation of replicable method from luck and non-transferable endowment. Includes a bubble-busting table sorted most-water-first.
  • Phase 4 — what this means for YOU: a resource-mapping table tagging each playbook element ✅ borrow-able / ⚠️ not replicable / 🔄 already doing / 🚫 bubble-don't-copy, plus landing points and an action list.

A notable design detail: a two-channel injection rule keeps your private context (client names, strategic intent) out of any agent that performs web searches — it reaches only the final mapping phase.

Who it's for

  • Founders who suspect a rival's traction numbers are mostly PR
  • Investors and strategy leads who need headline claims (Product Hunt #1, user counts, valuations) stress-tested
  • Marketers who want to copy a creator's growth formula but need to know which parts are luck
  • Consultants who want benchmark reports to end in an action plan, not a summary

Examples

  1. "This founder claims 0→1M users — is that real?" The skill makes headline-claim attribution the top verification target and cross-checks against third-party sources.
  2. Teardown of a competitor's distribution playbook: platform matrix, persona, content types, how they borrow other people's audiences, and how personal IP funnels into the product.
  3. Pre-investment screen: entity and funding checks (with qcc for mainland-China registration data), a structurally similar peer comparison, and how this class of playbook typically fails.

· · · Install guide · · ·

Install in the Claude app (no terminal)
  1. Download the ZIP with the button below.
  2. In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
  3. Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
Download ZIP
Install in Claude Code

Let Claude do it — paste this into Claude Code

Install the skill I found on Claude Skill Mart.
Copy the benchmark-due-diligence folder from the GitHub repo daymade/claude-code-skills into my ~/.claude/skills/benchmark-due-diligence/.
When it's done, tell me in one line what this skill can do.

Install with a command instead

git clone https://github.com/daymade/claude-code-skills.git && mkdir -p ~/.claude/skills && cp -r claude-code-skills/benchmark-due-diligence ~/.claude/skills/

This is a third-party skill. Check the source repository before installing.

  1. Open a terminal (Terminal on macOS, Git Bash or WSL on Windows).
  2. Create the skills folder if needed: mkdir -p ~/.claude/skills
  3. Clone the repository: git clone https://github.com/daymade/claude-code-skills.git
  4. Copy just this skill: cp -r claude-code-skills/benchmark-due-diligence ~/.claude/skills/
  5. Confirm that ~/.claude/skills/benchmark-due-diligence/ contains both SKILL.md and the references/ folder — without the references, the grading rubric and mapping framework won't work.
  6. Restart Claude Code and check that benchmark-due-diligence appears in your skill list.
  7. Try it: "Do a due-diligence teardown on company X — how much of their success is real?" Web search must be enabled; the skill fans out many parallel agents, so expect high token usage.
  8. Important: this is an orchestrator skill. Never run it inside a subagent or add a context: fork field, or the entire fan-out will silently break.