agentleFS
Zhangs-11Zhangs-11/zs-skills/deep-research/SKILL.md

deep-research

Skill2 starsChanged 3 months agoMITView on GitHub

系统研究主题或比较方案时用。不用于单条事实查询、当日资讯或单篇摘要。

196 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use community-led-growth, ph-community-outreach and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • nicepkgSkill

    community-led-growth

    Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.

    Also in 5 projects that use this

  • nicepkgSkill

    ph-community-outreach

    Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy.

    Also in 5 projects that use this

  • W-MoorerSkill

    academic-paper-reviewer

    Multi-perspective academic paper review with dynamic reviewer personas. Simulates 5 independent reviewers (EIC + 3 peer reviewers + Devil's Advocate) with field-specific expertise. Supports full review, re-review (verification), quick assessment, methodology focus, Socratic guided, and calibration modes. Triggers on: review paper, peer review, manuscript review, referee report, review my paper, critique paper, simulate review, editorial review, calibrate reviewer, reviewer calibration, measure reviewer accuracy.

    Also in 11 projects that use this

  • W-MoorerSkill

    academic-pipeline

    Orchestrator for the full academic research pipeline: research -> write -> integrity check -> review -> revise -> re-review -> re-revise -> final integrity check -> finalize. Coordinates deep-research, academic-paper, and academic-paper-reviewer into a seamless 10-stage workflow with mandatory integrity verification, two-stage peer review, and reproducible quality gates. Triggers on: academic pipeline, research to paper, full paper workflow, paper pipeline, end-to-end paper, research-to-publication, complete paper workflow.

    Also in 10 projects that use this

  • xfstudioSkill

    micro-saas-launcher

    Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing to sustainable revenue. Ship in weeks, not months. Use when: micro saas, indie hacker, small saas, side project, saas mvp.

    Also in 5 projects that use this

  • stophobiaSkill

    surprise-me

    Create a delightful, unexpected "wow" experience for the user by dynamically discovering and creatively combining other enabled skills. Triggers when the user says "surprise me" or any request expressing a desire for an unexpected creative showcase. Also triggers when the user is bored, wants inspiration, or asks for "something interesting".

    Also in 4 projects that use this

  • +4 more from nicepkg
  • +1 more from W-Moorer

The file

Files
SKILL.md

可追溯深度研究

目标不是堆满资料,而是让读者在有限时间内形成一个可检查的判断框架:研究对象为什么成为今天这样、它与真正可比对象差在哪里、这些历史能力和约束将怎样影响未来。

先固定研究问题

从用户真正要做的判断反推研究范围。明确研究对象、截止日期、读者、用途、时间跨度和需要比较的维度。能从上下文确定时直接开始;只有选择会实质改变研究对象或结论时,才一次询问一个关键变量。

按需要选择深度:

  • 快速框架:帮助陌生读者建立基本地图,保留核心结论、关键时间线、最小对比表和未知项。
  • 标准研究:完整走通纵向、横向、合并判断和事实核查。
  • 深入报告:用户明确要求长报告、重大决策或全面研究时,扩大来源、时间跨度、对照样本和反证覆盖;不以固定字数冒充深度。

建立证据底座

优先使用离主张最近的一手来源:官方文档、原始数据、源代码或规范、论文、财报、监管文件、正式公告和当事人完整访谈。二手资料适合发现线索与补充争议背景,不能替代它声称引用的一手来源。

为重要结论就近记录来源与日期。遇到来源冲突时并列呈现口径、时间和样本差异,不按数量投票;找不到足够证据时明确写“暂未核实”。研究对象、竞争格局、价格、人员、法规和产品状态可能变化时,以执行当天为截止时间重新核验。

纵向:解释它怎样走到今天

围绕会改变当前能力与约束的节点研究:

  1. 它在什么背景、需求和约束下出现,关键推动者是谁;
  2. 哪些成功、失败、产品转向、技术选择或外部变化构成真正转折;
  3. 哪些早期选择沉淀为今天的能力、路径依赖、组织惯性或包袱;
  4. 哪些常见历史叙事只是事后归因,缺少当时证据。

时间线只保留改变因果链的节点,不把所有发布日期排成流水账。

横向:用统一维度比较真实替代品

比较对象由用户或市场实际会在其中选择的替代方案决定,不只选名字相似者。先说明为什么选择这些对象,再用同一组维度比较目标用户、核心机制、能力边界、成本、分发或采用路径、主要优势与短板。

继续追问两件事:用户、客户或市场为什么选择它;又在什么条件下放弃它。市场份额、融资、声量或单项跑分不能单独代表产品质量或长期胜负。

合并两条轴

把历史形成的能力、路径依赖和现实约束映射到当前竞争差异,再推导未来。除非用户明确要求更多,最多给出三条真正不同的可能路径,并为每条写清:成立前提、最早可观察信号、主要反证和失效条件。相近趋势合并到同一路径下,不用增加条目制造全面感。

未来部分属于推断,不得写成已经发生的事实。若不同路径取决于用户的价值排序,说明实际取舍;若取决于尚未取得但可观察的数据,给出最短验证路径。

逐条核查关键主张

将会影响结论的说法拆成三类:

  • 事实:可由外部证据核验,例如日期、数字、功能、事件和公开表态;
  • 推断:从事实推出的原因、影响、趋势或未来判断;
  • 价值判断:取决于谁的目标、成本与偏好,例如“更好”“值得”“应该”。

只给事实使用证据等级:已证实、基本成立但需要收窄、存在争议、证据不足、明显错误。事实成立后仍要单独检查推断是否混淆相关性与因果、遗漏其他解释或越过适用范围。价值判断说明它服务谁、牺牲什么以及什么目标改变时结论会反转。

输出

按研究深度裁剪,默认顺序是:

  1. 核心结论;
  2. 关键时间线;
  3. 横向对比表;
  4. 纵横合并后的详细分析;
  5. 未来路径、前提与预警信号;
  6. 关键事实核查与仍待确认的问题。

先给结论,再给能支撑结论的证据。事实、推断和观点在语言上可区分;引用靠近对应主张。用户没有要求文件时直接在当前对话交付;要求沉淀、交接或仓库研究记录时,再写入符合目标项目惯例的 Markdown 文件。

完成标准

完成前确认:研究问题和截止时间明确;关键结论可追溯到足够新的事实源;纵向节点解释了当前能力或约束;横向对象是真实替代品且维度统一;主要反证和冲突信息没有被隐藏;事实、推断和价值判断没有混写;未来路径不超过用户要求的数量并带有前提、信号与失效条件;篇幅由问题需要决定而非固定字数。

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.