Agent skill · daymade
benchmark-due-diligence
Runs adversarial due-diligence on a benchmark the user envies — a founder, KOL, company, or product whose claimed success looks inflated — splitting marketing bubble from real signal, then mapping the validated playbook onto the user's own resources. Use whenever the user wants to 尽调/对标/拆解 a competitor or role-model, 抄/偷师 someone's playbook, suspects 水分/泡沫 in their claims (#1 on Product Hunt, 0-to-1M users, funding, 估值几个亿), asks whether wins are 真本事 vs 运气/时机, or says someone is 太成功了/crushing it and wants the real story — even if they never say 尽调. Prefer over deep-research for debunking inflated claims and extracting a replicable playbook rather than a neutral briefing.
What it needs
About 5k tokens when loaded.
What this skill does
Benchmark Due Diligence Take a benchmark the user envies — a founder, KOL, company, or product whose success looks suspiciously shiny — and produce a teardown that ends in "what this means for ME", not a neutral report. The deliverable answers three questions a balanced briefing never does: How much of this success is real vs marketing bubble? How much is replicable method vs luck/timing? And what, specifically, can the commissioner do with it? This is the adversarial, decision-oriented cousin of deep-research. Where deep-research builds a trustworthy picture of the world, this skill assumes the picture is inflated until proven otherwise and converts the survivors into the commissioner's own moves. CRITICAL: run inline, never context: fork This skill is an orchestrator — it spawns parallel collection + verification agents (via the Workflow tool, or Task agents) and may invoke other skills (deep-research, osint-investigate, qcc). Subagents cannot spawn subagents or call skills. Setting context: fork would silently break the entire fan-out. Do not add a context field. (Same constraint osint-investigate documents — it's a hard runtime rule, not a preference.) The one rule that protects the commissioner: two injection channels Everything the agents see flows through exactly two channels. Keeping them separate is the single most important discipline in this skill: Channel Content Injected into --- --- --- FACTS Already-verified public facts about the benchmark (relationships, who-owns-what, the headline claim flagged ⚠️ to-verify) Every agent — collection, verification, synthesis COMMISSIONERCONTEXT The commissioner's private reality — real resources, client names, strategic intent, what they can actually leverage Only the final mapping agent (Phase 4) Why this split is non-negotiable: collection and verification agents take their input and run external WebSearch on it. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills daymade/benchmark-due-diligence--f4f08b