benchmark-due-diligence
Runs adversarial due-diligence on a benchmark the user envies — a founder, KOL, company, or product whose success looks inflated — splitting marketing bubble from real signal, then mapping the validated playbook onto the user's own resources.
Install / Use
npx skills add daymade/claude-code-skills --skill benchmark-due-diligenceInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
MarketingSupported Platforms
Tags
Our assessment of benchmark-due-diligence
benchmark-due-diligence scores 88/100 on our quality scale, 317th of 642 Marketing skills we index (top 50%).
Its SKILL.md is 9.2 KB long, well organised into 8 sections with 1 code example: a thorough specification that gives an agent plenty to work with.
With 1,426 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so benchmark-due-diligence is actively maintained.
- Our last check on 2026-11-01 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-03. Automated pattern scan on 2026-10-03. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
benchmark-due-diligence compared with similar skills
All 4 of these similar skills score higher than benchmark-due-diligence; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| benchmark-due-diligence (this skill)by daymade | 88 | 1.4k | 53d ago | SKILL.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| designby nextlevelbuilder | 100 | 149.0k | 6d ago | SKILL.md |
Frequently asked questions
- How do I install benchmark-due-diligence?
- Run
npx skills add daymade/claude-code-skills --skill benchmark-due-diligence. The install tabs above show the steps for each supported agent. - Which AI agents does benchmark-due-diligence work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is benchmark-due-diligence safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is benchmark-due-diligence still maintained?
- The repository was last updated about 2 months ago, so benchmark-due-diligence is actively maintained.
Skill content
View source on GitHubname: benchmark-due-diligence description: >- Runs adversarial due-diligence on a benchmark the user envies — a founder, KOL, company, or product whose success looks inflated — splitting marketing bubble from real signal, then mapping the validated playbook onto the user's own resources. Use for 尽调/对标/拆解 a competitor, 抄/偷师 their playbook, or suspecting 水分/泡沫 in claims. Prefer over deep-research when debunking inflated claims, not a neutral briefing.
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 |
| COMMISSIONER_CONTEXT | 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. If the commissioner's client names or strategy leak into those prompts, they get searched on the open web — a privacy breach. The mapping phase genuinely needs "who is the commissioner"; the collection phase must never see it. Encode this in the orchestration (see references/workflow_orchestration_template.md), don't rely on remembering it mid-run.
Phase 0 — nail the foundation by evidence, not appearance (do this BEFORE any agent)
The fastest way to waste a 12-agent fan-out is to build it on a foundation you inferred from appearances. Two failure modes recur and both have burned real runs:
- Inferring relationships between entities from names/domains. "Their content lives at
academy.example.com, and they're the founder, so they must own that community" — when in reality they were just an invited guest. A shared domain, a similar name, or co-occurrence is an observation, not ownership. Verify with an authoritative source before treating any A↔B relationship as fact. - Treating the commissioner's client as the commissioner's asset. If the commissioner does service work for an accelerator/brand, that accelerator is the client's asset — the commissioner can't leverage its audience or capital. Mapping the benchmark's playbook onto resources the commissioner doesn't actually control produces castles in the air.
So before fanning out, establish by evidence (not vibes):
- The benchmark's real entity graph — who owns whom, who merely partners/guests. Don't reason from names.
- The headline-claim attribution — the benchmark's whole narrative usually rests on one trophy stat ("took product X from 0 → 1M users"). Are they the founder, or the departed growth lead? This is the #1 to-verify target; write it into FACTS with a
⚠️. - What the commissioner truly controls — separate owned assets from client/partner assets.
Write the results into FACTS (public half) and COMMISSIONER_CONTEXT (private half). A shaky foundation makes every downstream agent confidently wrong.
The four-phase orchestration
Use the Workflow tool (preferred — deterministic fan-out, see the ready-to-fill template in references/workflow_orchestration_template.md) or Task agents. Scale agent count to how thorough the user wants (a few dimensions for a quick read, 6+ with multi-vote verification for a deep audit).
Phase 1 + 2 — collect → verify, per dimension, as a pipeline (each dimension verifies the moment its collection finishes; no global barrier):
- Collection agent — objective stance. Every finding carries a source URL and a
source_kind(对象自述/营销vs第三方独立信源vs混合). Anything not found goes ingaps— never filled by guessing. - Verification agent — adversarial, default-skeptical stance. Grade every claim
L1–L4and rule坐实 / 大体可信 / 存疑 / 证伪-水分. The job is to actively hunt falsifying evidence, especially for the headline claims (the trophy stat, "#1 ranking", funding amount, user counts).bubble_summarynames the biggest water in that dimension.
Grading rubric, source_kind, verdicts, and both JSON schemas → references/evidence_grading_rubric.md.
Typical dimensions (tailor to the benchmark type — person / company / product):
- Subject background + headline-claim attribution (the #1 bubble target)
- Corporate base — entity, founding, funding/valuation
- Core product/business real metrics — user counts, revenue, rankings, awards, cross-verified against third parties
- Playbook teardown — platform matrix, persona, content types, how they borrow other people's audiences, how personal IP funnels to the product
- Comparison sample — a structurally-similar peer or parallel path
- Sector + how this class of playbook usually wins and usually fails
Phase 3 — synthesis: due-diligence conclusion (single agent, consumes all verdicts):
- Real relationship map (correcting the common misreadings from Phase 0)
- Bubble-busting table — claim | evidence level | verdict | one-line basis, sorted by most-water-first
- Playbook teardown — concrete, copyable actions
- Attribution breakdown (the core) — what share of the success is product vs market-timing vs personal-IP-marketing vs operations? Give % ranges with reasons, and explicitly split replicable method from luck / timing / non-transferable endowment.
Phase 4 — synthesis: what this means for the commissioner (single agent; consumes Phase 3 + COMMISSIONER_CONTEXT):
- Resource-mapping table — benchmark's playbook elements × the commissioner's real resources; tag each cell ✅ borrow-able / ⚠️ not-replicable (luck/timing) / 🔄 already-doing / 🚫 bubble-don't-copy, one line each
- Landing points — exactly how the commissioner uses it (their to-B service / their own IP / their tooling)
- Action list + open questions (what's still unconfirmed)
Attribution weighting and the four-tag mapping framework → references/attribution_and_resource_mapping.md.
Don't rebuild what already exists
This skill's edge is the adversarial bubble-busting + attribution + commissioner-mapping layers. The plumbing underneath is not novel — reuse it:
- Fan-out collection / source governance — borrow the lead-agent + subagent pattern from
deep-research. (What's unique here is the skeptical verification stance and the L1–L4 bubble grading, not the parallelism.) - Person-subject identity / footprint checks — invoke
osint-investigate(ACH hypothesis matrix, Bellingcat-style pivots) rather than re-deriving identity attribution. - Mainland-China corporate registration / funding — invoke the
qccfamily of skills for 工商 data. - Social-platform playbook data — the
agent-reachCLI covers B站/小红书/抖音/YouTube/X.
Read before you run
references/evidence_discipline_traps.md— the recurring traps (inferring relationships from appearances, headline-claim attribution, client-vs-asset, foundation-before-fan-out, grade-don't-binary, privacy leak) with real teardown war-stories. Read this first; it's where runs actually break.references/evidence_grading_rubric.md— L1–L4, source_kind, verdicts, collection/verification schemas.references/attribution_and_resource_mapping.md— attribution weighting + four-tag mapping + landing-point framework.references/workflow_orchestration_template.md— a ready-to-fillWorkflowscript with the FACTS / COMMISSIONER_CONTEXT injection split already wired in.
Next Step
After the due-diligence conclusion is ready, suggest the natural follow-on (opt-in, never auto-run):
Due-diligence teardown is done.
Options:
A) Render it as a shareable PDF report — pdf-creator (Recommended if this goes to a partner/team)
B) One dimension needs deeper neutral background — deep-research on that sub-topic
C) No thanks — the markdown teardown is enough
Related Skills
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
design
149.0kComprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini, Atlas Cloud, or MuAPI AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVG…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
