company-deep-dive

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Company Deep Dive

公司深度调研

360° company research powered by Nimble's web data APIs.

User request: $ARGUMENTS

Before running any commands, read

references/nimble-playbook.md

for Claude Code constraints (no shell state, no

wait

, sub-agent permissions, communication style).

基于Nimble网络数据API的360°企业调研工具。

用户请求：$ARGUMENTS

在运行任何命令之前，请阅读

references/nimble-playbook.md

了解Claude Code的限制条件（无shell状态、禁止使用

wait

、子Agent权限、沟通风格）。

Instructions

操作说明

Step 0: Preflight

步骤0：预检

Run the preflight pattern from

references/nimble-playbook.md

(5 simultaneous Bash calls: date calc, today, CLI check, profile load, index.md load).

From the results:

CLI missing or API key unset →
```
references/profile-and-onboarding.md
```
, stop
Profile exists → note it for context (company name helps frame the research). Read
```
~/.nimble/memory/companies/index.md
```
to check if the target company already has prior research. Follow
```
[[path/entity]]
```
cross-references to load related context.
- Prior research exists: Load it. Run in refresh mode — focus on what's new since the last report date. Tell the user: "I have prior research on [Company] from [date]. Refreshing with latest data."
- No prior research: Run in full mode — comprehensive across all dimensions.
No profile → that's fine. Company deep dive doesn't require onboarding (unlike competitor-intel). Proceed directly to Step 1.

执行

references/nimble-playbook.md

中的预检流程（5个并行Bash调用：日期计算、今日日期、CLI检查、配置文件加载、index.md加载）。

根据结果处理：

CLI缺失或API密钥未设置 → 参考
```
references/profile-and-onboarding.md
```
，停止操作
配置文件存在 → 记录上下文信息（公司名称有助于调研框架搭建）。读取
```
~/.nimble/memory/companies/index.md
```
，检查目标公司是否已有过往调研记录。通过
```
[[path/entity]]
```
交叉引用加载相关上下文。
- 存在过往调研记录：加载记录。以刷新模式运行——重点关注上次报告日期之后的新信息。告知用户："我已有[Company]在[date]的调研记录，正在获取最新数据进行更新。"
- 无过往调研记录：以完整模式运行——全面覆盖所有维度。
无配置文件 → 无需担心。公司深度调研无需完成入职流程（与competitor-intel不同），直接进入步骤1。

Step 1: Identify Target Company

步骤1：确定目标公司

Parse the target company from

$ARGUMENTS

or the user's message.

If clear (e.g., "research Stripe", "tell me about Datadog"):

Extract the company name

Run two Bash calls simultaneously to confirm identity:

nimble search --query "[Company] official site" --max-results 3 --search-depth lite

nimble search --query "[Company] company overview" --max-results 5 --search-depth lite

Confirm briefly: "Researching [Company] ([domain])..."

If ambiguous (e.g., "research Mercury" — could be bank, auto, or other):

Ask one clarifying question with the top candidates

If missing — ask: "Which company would you like me to research?"

Scope selection — if the user hasn't specified depth, default to full deep dive. If they say "quick overview", "brief", or "summary", run a quick mode that skips the Deep Extraction step and produces a shorter report.

从

$ARGUMENTS

或用户消息中解析目标公司。

公司名称明确（例如："research Stripe"、"tell me about Datadog"）：

提取公司名称

并行执行两个Bash调用以确认身份：

nimble search --query "[Company] official site" --max-results 3 --search-depth lite

nimble search --query "[Company] company overview" --max-results 5 --search-depth lite

简要确认："正在调研**[Company]**（[域名]）..."

公司名称模糊（例如："research Mercury"——可能指银行、汽车品牌或其他）：

列出候选选项，提出一个澄清问题

未指定公司 —— 询问："你想调研哪家公司？"

范围选择 —— 如果用户未指定调研深度，默认采用完整深度调研。若用户要求"快速概览"、"简要介绍"或"摘要"，则以快速模式运行，跳过深度提取步骤并生成简短报告。

Step 2: WSA Discovery

步骤2：WSA发现

Discover available WSAs for the target company's domain. Run both searches simultaneously:

bash

nimble agent list --search "{company-domain}" --limit 20

bash

nimble agent list --search "{company-name}" --limit 20

From the results, filter for WSAs with

entity_type

matching SERP or PDP, and prefer

managed_by: "nimble"

. Validate each with

nimble agent get --template-name {name}

, then cache discovered WSA names + params for the run. Pass them to dimension agents in Step 3 for enrichment alongside

nimble search

. If no WSAs found, continue with

nimble search

alone.

查找目标公司域名可用的WSA。并行执行以下两个搜索：

bash

nimble agent list --search "{company-domain}" --limit 20

bash

nimble agent list --search "{company-name}" --limit 20

从结果中筛选

entity_type

匹配SERP或PDP的WSA，优先选择

managed_by: "nimble"

的条目。通过

nimble agent get --template-name {name}

验证每个条目，然后缓存本次运行中发现的WSA名称及参数。将其传递给步骤3中的维度Agent，与

nimble search

配合进行信息补充。若未找到WSA，仅使用

nimble search

继续操作。

Step 3: Parallel Research Across Dimensions (sub-agents)

步骤3：多维度并行调研（子Agent）

Read

references/dimension-agent-prompt.md

for the full agent prompt template. Follow the sub-agent spawning rules from

references/nimble-playbook.md

(bypassPermissions, batch max 4, explicit Bash instruction, fallback on failure).

Spawn

nimble-researcher

agents (

agents/nimble-researcher.md

) with

mode: "bypassPermissions"

. Each agent researches one dimension of the company. Pass discovered WSA names from Step 2 to each agent so they can use them for enrichment alongside

nimble search

Important: The Nimble API has a 10 req/sec rate limit per API key. With each agent running 4-5 searches in parallel, limit concurrent agents to 2 per batch to stay under the limit. Run overview searches in their own phase, not alongside agent batches.

Call estimation & Scaled Execution: Before launching agents, estimate total API calls: 2 overview searches + ~5 searches per agent × 5 agents = ~27 calls. Each agent should use

extract-batch

agent run-batch

for 11+ calls instead of individual calls. See the Scaled Execution pattern in

references/nimble-playbook.md

for tier selection.

Phase A — Overview searches (run directly, before agents):

nimble search --query "about" --include-domain '["[domain]"]' --max-results 3 --search-depth lite

nimble search --query "[Company] Wikipedia OR Crunchbase OR Pitchbook" --max-results 5 --search-depth lite

These give foundational context (founding date, HQ, employee count, mission) that frames all dimensional findings.

Phase B — Batch 1 (2 agents simultaneously):

Agent	Dimension	Focus
1	Funding & Financials	Funding rounds, valuation, revenue signals, investors, financial health
2	Product & Technology	Products, tech stack, recent launches, engineering blog, open-source

Phase C — Batch 2 (2 agents simultaneously):

Agent	Dimension	Focus
3	Leadership & Team	Founders, C-suite, key hires, departures, team size, culture signals
4	Recent News & Events	Press coverage, announcements, partnerships, awards, conferences

Phase D — Batch 3 (1 agent):

Agent	Dimension	Focus
5	Market Position	Competitors, market share, positioning, analyst coverage, customer reviews

Refresh mode adjustment: If prior research exists, pass the known facts to each agent as context so they focus on what's new. Agents should use

--start-date

to filter for recent data only.

Fallback: If any agent fails or returns empty, run those dimension searches directly from the main context. Don't leave gaps in the report.

阅读

references/dimension-agent-prompt.md

获取完整的Agent提示模板。遵循

references/nimble-playbook.md

中的子Agent生成规则（bypassPermissions、批量最大4个、明确Bash指令、失败时降级处理）。

生成

nimble-researcher

Agent（

agents/nimble-researcher.md

），设置

mode: "bypassPermissions"

。每个Agent负责调研公司的一个维度。将步骤2中发现的WSA名称传递给每个Agent，使其在

nimble search

之外还能利用WSA进行信息补充。

重要提示：Nimble API的速率限制为每个API密钥每秒10次请求。由于每个Agent会并行执行4-5次搜索，需将并发Agent数量限制为每批2个，以避免超出限制。概览搜索需单独执行，不与Agent批处理同时进行。

调用估算与规模化执行：在启动Agent之前，估算总API调用次数：2次概览搜索 + 每个Agent约5次搜索 × 5个Agent = 约27次调用。若调用次数≥11次，每个Agent应使用

extract-batch

或

agent run-batch

而非单独调用。参考

references/nimble-playbook.md

中的规模化执行模式选择对应层级。

阶段A —— 概览搜索（直接执行，在Agent启动前完成）：

nimble search --query "about" --include-domain '["[domain]"]' --max-results 3 --search-depth lite

nimble search --query "[Company] Wikipedia OR Crunchbase OR Pitchbook" --max-results 5 --search-depth lite

这些搜索提供基础背景信息（成立日期、总部地点、员工数量、使命），为所有维度的调研结果提供框架。

阶段B —— 第一批（2个Agent并行）：

Agent	维度	重点
1	融资与财务	融资轮次、估值、营收信号、投资者、财务健康状况
2	产品与技术	产品、技术栈、近期发布、技术博客、开源项目

阶段C —— 第二批（2个Agent并行）：

Agent	维度	重点
3	领导层与团队	创始人、高管团队、重要招聘/离职、团队规模、文化信号
4	近期新闻与事件	媒体报道、公告、合作、奖项、会议参与

阶段D —— 第三批（1个Agent）：

Agent	维度	重点
5	市场地位	竞争对手、市场份额、定位、分析师报道、客户评价

刷新模式调整：若存在过往调研记录，将已知事实作为上下文传递给每个Agent，使其专注于新信息。Agent应使用

--start-date

筛选仅获取近期数据。

降级处理：若任何Agent运行失败或返回空结果，直接从主上下文执行该维度的搜索。确保报告无内容缺失。

Step 4: Deep Extraction

步骤4：深度提取

From all agents' results, identify the top 5-8 most informative URLs across dimensions. Prioritize:

Funding announcements with specific amounts
Official product/feature pages
Executive interviews, podcast appearances, or conference talks
In-depth analyst or journalist profiles
The company's own about/team page

Make one Bash call per URL, all simultaneously:

nimble extract --url "https://..." --format markdown

For extraction failures, follow the fallback in

references/nimble-playbook.md

Quick mode: Skip this step entirely. Report from search snippets only.

WSA enrichment: If WSAs were discovered in Step 2, use them here for richer extraction on key URLs before falling back to

nimble extract

从所有Agent的结果中，确定跨维度的5-8个最具信息量的URL。优先选择：

包含具体金额的融资公告
官方产品/功能页面
高管访谈、播客或会议演讲
深度分析师或记者报道
公司官方关于我们/团队页面

为每个URL并行执行一次Bash调用：

nimble extract --url "https://..." --format markdown

若提取失败，遵循

references/nimble-playbook.md

中的降级处理方案。

快速模式：完全跳过此步骤，仅基于搜索片段生成报告。

WSA补充：若步骤2中发现WSA，在使用

nimble extract

降级处理之前，优先利用WSA对关键URL进行更丰富的提取。

Step 5: Synthesize Report

步骤5：生成报告

Structure the output as a 360° Company Report:

undefined

将输出内容整理为360°企业报告：

undefined

[Company Name] — Deep Dive

[公司名称] —— 深度调研

As of [today's date]

截至[今日日期]

Quick Assessment

快速评估

[2-3 sentence verdict: what this company is, where they stand, and the one thing that matters most right now. This is the "if you read nothing else" paragraph.]

[2-3句话总结：公司定位、当前状态以及当前最核心的要点。这是“如果只看一段内容”的核心段落。]

Company Overview

公司概览

Founded: [year] | HQ: [location] | Employees: [estimate]
Domain: [domain] | Industry: [industry]
Mission/focus: [one line]

成立时间：[年份] | 总部：[地点] | 员工数量：[估算值]
域名：[域名] | 行业：[行业]
使命/核心业务：[一句话描述]

Funding & Financials

融资与财务

[Latest round, total raised, key investors, valuation signals, revenue indicators. Every claim dated and sourced.]

[最新融资轮次、总融资额、主要投资者、估值信号、营收指标。所有内容均标注日期和来源。]

Leadership & Team

领导层与团队

[Founders, C-suite, notable recent hires or departures. Executive perspectives on company direction — direct quotes when available from interviews or talks.]

[创始人、高管团队、近期重要招聘或离职。高管对公司发展方向的观点——若能从访谈或演讲中获取直接引用，请包含在内。]

Product & Technology

产品与技术

[Core products, recent launches, tech stack signals, engineering culture, open-source contributions. What they're building and how.]

[核心产品、近期发布、技术栈信号、工程文化、开源贡献。公司正在构建的内容及实现方式。]

Market Position

市场地位

[Key competitors, differentiation, market share signals, analyst perspectives, customer sentiment from reviews (G2/Capterra/Reddit).]

[主要竞争对手、差异化优势、市场份额信号、分析师观点、来自G2/Capterra/Reddit的客户评价。]

近期新闻与事件

[Chronological, most recent first. Each entry dated with source.]

[按时间倒序排列，最新内容优先。每条内容均标注日期和来源。]

Strategic Outlook

战略展望

[Synthesis across all dimensions: where the company is heading, key risks, growth signals, and strategic bets. This is insight, not summary.]

[综合所有维度的分析：公司发展方向、核心风险、增长信号及战略布局。这是洞察而非总结。]

Sources

来源

[Numbered list of all URLs cited in the report]


**Core rules:**
- Every factual claim must have a date and source URL.
- Lead with the Quick Assessment — most readers stop there.
- Say "no public data found" for a dimension rather than speculating.
- Distinguish between confirmed facts and inferred signals.
- Executive quotes add credibility — include direct quotes from interviews,
  earnings calls, or conference talks when found.
- In refresh mode: lead with "What's New Since [last date]" before the full sections.

[报告中引用的所有URL编号列表]


**核心规则**：
- 所有事实性陈述必须标注日期和来源URL。
- 以快速评估开头——大多数读者仅会阅读此部分。
- 若某维度无公开数据，标注“未找到公开数据”而非猜测。
- 区分已确认事实与推断信号。
- 高管引用可提升可信度——若能从访谈、财报电话会议或会议演讲中获取直接引用，请包含在内。
- 刷新模式：在完整章节之前，先列出“自[上次日期]以来的新变化”。

Step 6: Save to Memory

步骤6：保存至内存

Make all Write calls simultaneously:

Report →

~/.nimble/memory/reports/company-deep-dive-[date].md

Company profile →
```
~/.nimble/memory/companies/[company-name-slug].md
```
(use the format in
```
references/memory-and-distribution.md
```
). Add
```
[[path/entity]]
```
cross-references for key people discovered (e.g.,
```
[[people/jane-smith]]
```
), competitors in the same space (e.g.,
```
[[competitors/widgetco]]
```
), and any other related entities.

If profile exists → update

last_runs.company-deep-dive

~/.nimble/business-profile.json

Follow the wiki update pattern from
```
references/memory-and-distribution.md
```
: update
```
index.md
```
rows for all affected entity files, append a
```
log.md
```
entry for this run.

The company profile in

companies/

should contain structured key facts (overview, financials, leadership, products) that can be loaded by future runs of any skill that needs context on this company.

并行执行所有写入操作：

报告 →

~/.nimble/memory/reports/company-deep-dive-[date].md

公司档案 →
```
~/.nimble/memory/companies/[company-name-slug].md
```
（遵循
```
references/memory-and-distribution.md
```
中的格式）。添加
```
[[path/entity]]
```
交叉引用至发现的关键人物（例如：
```
[[people/jane-smith]]
```
）、同领域竞争对手（例如：
```
[[competitors/widgetco]]
```
）及其他相关实体。

若档案已存在 → 更新

~/.nimble/business-profile.json

中的

last_runs.company-deep-dive

字段

遵循
```
references/memory-and-distribution.md
```
中的wiki更新模式：更新所有受影响实体文件的
```
index.md
```
行，在
```
log.md
```
中添加本次运行的记录。

companies/

目录下的公司档案应包含结构化关键信息（概览、财务、领导层、产品），供后续需要该公司上下文的任何Skill调用加载。

Step 7: Share & Distribute

步骤7：分享与分发

Always offer distribution — do not skip this step. Follow

references/memory-and-distribution.md

for connector detection, sharing flow, and source links enforcement.

必须提供分发选项——请勿跳过此步骤。遵循

references/memory-and-distribution.md

中的连接器检测、分享流程及来源链接强制要求。

Step 8: Follow-ups

步骤8：后续操作

Go deeper on a dimension → focused searches on that topic
Compare with another company → side-by-side analysis
"What about [specific topic]?" → targeted search + extraction
"Looks good" → done

Sibling skill suggestions:

Next steps:
Run
competitor-intel
to track this company as a competitor over time
Run
meeting-prep
if you're meeting with someone at this company
Run
competitor-positioning
to analyze their messaging vs yours

深入某一维度 → 针对该主题进行聚焦搜索
与其他公司对比 → 并排分析
“关于[特定主题]的情况如何？” → 定向搜索+提取
“看起来不错” → 操作完成

同类Skill建议：

下一步操作：
运行
competitor-intel
以长期跟踪该公司作为竞争对手的动态
若你将与该公司人员会面，运行
meeting-prep
运行
competitor-positioning
分析其与你的品牌定位差异

Agent Teams Mode (Dual-Mode)

Agent团队模式（双模式）

Check at startup:

echo $CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS

Team mode (flag set): Spawn 3 teammates instead of sub-agents. Each teammate covers related dimensions and can message the others to cross-check findings.

Teammate	Dimensions	Cross-checks with
Financials & News	Funding, revenue, recent news, events	Market (valuation vs positioning)
Product & Leadership	Products, tech stack, founders, key hires	Financials (pivots vs funding)
Market	Competitors, positioning, reviews, analysts	Product (differentiation claims)

Lead (you): Create shared tasks, wait for all teammates to complete, then synthesize the final report. When a teammate finds a claim that another should verify (e.g., a funding amount that implies a valuation), it posts a task for the relevant teammate.

Solo mode (flag not set): Standard sub-agent flow from Step 3.

启动时检查：

echo $CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS

团队模式（已设置标志）：生成3个队友而非子Agent。每个队友负责相关维度，并可与其他队友沟通以交叉验证结果。

队友	负责维度	交叉验证对象
财务与新闻	融资、营收、近期新闻、事件	市场团队（估值与定位对比）
产品与领导层	产品、技术栈、创始人、重要招聘	财务团队（业务转型与融资关联）
市场	竞争对手、定位、评价、分析师	产品团队（差异化主张验证）

主导者（你）：创建共享任务，等待所有队友完成，然后生成最终报告。当某队友发现需要其他队友验证的结论（例如：融资额暗示估值），可向相关队友发布验证任务。

单模式（未设置标志）：遵循步骤3中的标准子Agent流程。

What This Skill Is NOT

本Skill不适用场景

Not competitor monitoring. For tracking multiple competitors over time, use
```
competitor-intel
```
. This skill goes deep on ONE company.
Not meeting prep. For researching people you're meeting with, use
```
meeting-prep
```
. This skill researches companies, not individuals.
Not financial advice. This is intelligence gathering from public sources, not investment analysis or due diligence certification.
Not real-time monitoring. This produces a point-in-time report. For ongoing tracking, run it again later or use
```
competitor-intel
```
with the company added.

非竞品监控工具：如需长期跟踪多家竞争对手，请使用
```
competitor-intel
```
。本Skill仅针对单一公司进行深度调研。
非会议准备工具：如需调研会面人员信息，请使用
```
meeting-prep
```
。本Skill调研公司而非个人。
非财务建议工具：本工具仅从公开来源收集情报，不提供投资分析或尽职调查认证。
非实时监控工具：本工具生成特定时间点的报告。如需持续跟踪，请再次运行本Skill或添加该公司至
```
competitor-intel
```
进行监控。

Error Handling

错误处理

See

references/nimble-playbook.md

for the standard error table (missing API key, 429, 401, empty results, extraction garbage). Skill-specific errors:

Search 500: Retry once without
```
--focus
```
flag. If still failing, retry with a simplified query (shorter terms, no date filter). Log the failure but don't skip the dimension.
Search timeout: Retry once, then skip that call and continue — consistent with the playbook's timeout policy.
Company not found: Retry with domain, alternative names, or parent company
Empty results for a dimension: Note "No public data found" — don't speculate

参考

references/nimble-playbook.md

中的标准错误表（缺失API密钥、429错误、401错误、空结果、提取内容无效）。Skill特定错误处理：

搜索500错误：移除
```
--focus
```
标志重试一次。若仍失败，使用简化查询（缩短关键词、移除日期筛选）重试。记录失败但不跳过该维度。
搜索超时：重试一次，然后跳过该调用继续操作——符合手册中的超时处理策略。
未找到公司：使用域名、别名或母公司名称重试
某维度无结果：标注“未找到公开数据”——请勿猜测

company-deep-dive

Original

Translation

Company Deep Dive

公司深度调研

Instructions

操作说明

Step 0: Preflight

步骤0：预检

Step 1: Identify Target Company

步骤1：确定目标公司

Step 2: WSA Discovery

步骤2：WSA发现

Step 3: Parallel Research Across Dimensions (sub-agents)

步骤3：多维度并行调研（子Agent）

Step 4: Deep Extraction

步骤4：深度提取

Step 5: Synthesize Report

步骤5：生成报告

[Company Name] — Deep Dive

[公司名称] —— 深度调研

Quick Assessment

快速评估

Company Overview

公司概览

Funding & Financials

融资与财务

Leadership & Team

领导层与团队

Product & Technology

产品与技术

Market Position

市场地位

Recent News & Events

近期新闻与事件

Strategic Outlook

战略展望

Sources

来源

Step 6: Save to Memory

步骤6：保存至内存

Step 7: Share & Distribute

步骤7：分享与分发

Step 8: Follow-ups

步骤8：后续操作

Agent Teams Mode (Dual-Mode)

Agent团队模式（双模式）

What This Skill Is NOT

本Skill不适用场景

Error Handling

错误处理