基准尽职调查
- 作者仓库星标 0
- 作者更新于 2026年8月24日 07:33
- 作者仓库 claude-code-skills
- 领域
- 通用
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @daymade · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 命令执行
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
第 0 阶段——通过证据而不是外表来奠定基础(在任何代理人之前执行此操作)
浪费 12 代理扇出的最快方法是将其构建在您“从外观推断”的基础上。两种故障模式重复出现,并且都烧毁了实际运行:从名称/域推断实体之间的关系。 “他们的内容存在于`academy.example.com`,而且他们是创始人,所以他们必须拥有这个社区”——而实际上他们只是受邀的客人。共享域、相似名称或共现是一种观察,而不是所有权。在将任何 A↔B 关系视为事实之前,请先向权威来源进行验证。
# 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:
1. **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.
2. **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 in `gaps` — **never** filled by guessing.
- **Verification agent** — *adversarial, default-skeptical* stance. Grade every claim `L1–L4` and rule `坐实 / 大体可信 / 存疑 / 证伪-水分`. The job is to actively hunt **falsifying** evidence, especially for the headline claims (the trophy stat, "#1 ranking", funding amount, user counts). `bubble_summary` names 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):
1. Subject background **+ headline-claim attribution** (the #1 bubble target)
2. Corporate base — entity, founding, funding/valuation
3. Core product/business **real metrics** — user counts, revenue, rankings, awards, cross-verified against third parties
4. Playbook teardown — platform matrix, persona, content types, how they borrow other people's audiences, how personal IP funnels to the product
5. Comparison sample — a structurally-similar peer or parallel path
6. Sector + how this class of playbook usually wins **and usually fails**
**Phase 3 — synthesis: due-diligence conclusion** (single agent, consumes all verdicts):
1. Real relationship map (correcting the common misreadings from Phase 0)
2. **Bubble-busting table** — claim | evidence level | verdict | one-line basis, sorted by most-water-first
3. Playbook teardown — concrete, copyable actions
4. **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**):
1. **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
2. Landing points — exactly how the commissioner uses it (their to-B service / their own IP / their tooling)
3. 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 `qcc` family of skills for 工商 data.
- **Social-platform playbook data** — the `agent-reach` CLI 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-fill `Workflow` script 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
```
章节与文件索引
按说明文件中的顺序排列。
关键:内联运行,切勿上下文:fork
保护专员的一条规则:两条注入通道
第 0 阶段——通过证据而不是外表来奠定基础(在任何代理人之前执行此操作)
四阶段编排
不要重建已经存在的东西
文件/命令 -> deep-research · context: fork · Workflow · Task · osint-investigate · qcc · context · ⚠️ to-verify
内容校验值 -> 4e1e08d7c39f
当前原文的自动摘译,尚未人工审校。
关键:内联运行,切勿上下文:fork
该技能是一个协调器 - 它生成并行收集+验证代理(通过
Workflow工具或Task代理),并可能调用其他技能(deep-research,osint-investigate,qcc)。子代理不能生成子代理或调用技能。设置context: fork会默默地破坏整个扇出。不要添加context字段。 (同样的约束 osint-investigate 文档 - 这是一个硬性的运行时规则,而不是偏好。)保护专员的一条规则:两条注入通道
特工看到的一切都恰好通过两个渠道流动。将它们分开是这项技能中最重要的原则: 渠道 · 内容 · 注入事实 · 已经验证的关于基准的公共事实(关系、谁拥有什么、标记为
⚠️ to-verify的标题声明) · 每个代理 — 收集、验证、综合 COMMISSIONER_CONTEXT · 专员的 私人 现实 — 真实资源、客户名称、战略意图、他们实际可以利用的内容 · 只有最终的映射代理(第四阶段)第 0 阶段——通过证据而不是外表来奠定基础(在任何代理人之前执行此操作)
浪费 12 代理扇出的最快方法是将其构建在您“从外观推断”的基础上。两种故障模式重复出现,并且都烧毁了实际运行:从名称/域推断实体之间的关系。 “他们的内容存在于
academy.example.com,而且他们是创始人,所以他们必须拥有这个社区”——而实际上他们只是受邀嘉宾。共享域、相似名称或共现是一种观察,而不是所有权。在将任何 A↔B 关系视为事实之前,请先向权威来源进行验证。四阶段编排
使用
Workflow工具(首选 - 确定性扇出,请参阅references/workflow_orchestration_template.md中的准备填充模板)或Task代理。根据用户想要的彻底程度调整代理计数(几个维度用于快速阅读,6+ 多个维度用于深入审核)。第 1 + 2 阶段 — 收集 → 验证,每个维度,作为管道(每个维度在其收集完成时验证;没有全局障碍):不要重建已经存在的东西
这项技能的优势是对抗性泡沫破坏+归因+专员映射层。下面的管道并不新颖——重用它:扇出收集/源治理——借用了
deep-research的主导代理+子代理模式。 (这里的独特之处在于怀疑验证立场和 L1-L4 气泡分级,而不是并行性。)人-主体身份/足迹检查 - 调用osint-investigate(ACH 假设矩阵,Bellingcat 式枢轴)而不是重新推导身份归因。