中级Agent Skill

研究资料总结

围绕团队需要回答的问题,完成研究报告总结,而不只是压缩篇幅。提供论文、市场报告或提取后的正文后,这项 Skill 会帮助助手整理主要发现、研究方法、证据质量和限制,比较不同来源的结论,并保留引用线索,方便运营判断哪些信息可以用于当前决策。

浏览量
0
复制次数
0
收藏
0
编辑评分
83/100
01

这个 Skill 是做什么的

长报告里既有值得采用的发现,也有样本、方法和适用范围的限制。普通摘要容易只留下结论,这项 Skill 则用结构化模板把结论与依据放在一起,也可以围绕同一决策问题比较多份资料。

适合已经收集好来源、需要快速理解和整理的阶段。它不会自动上网补找报告,提取出的引用线索也需要回到原文核对。无法直接读取的 PDF,应先用合适工具提取正文,再交给助手总结。

02

它有什么特色

01

方法与优势

把发现、方法和限制分别记录,帮助读者区分哪些结论有原文支持,哪些只是进一步解释。运营据此可以检查研究对象、品类和市场是否与当前业务接近,避免只看到一个数字就直接套用。

02

适用任务

比较模板和引用线索便于后续复核,不需要重新从整份报告里寻找依据。把原始文件保留下来,在重要数字和说法进入策略汇报、公开文章或商业方案之前,再逐项确认其原始含义。

03

安装前的特殊要求

需要准备的输入

论文、报告或提取后的文档文本、决策问题、所需详略和引用格式。

Agent 与运行环境

使用支持 Skill 且能访问文件的 Agent。随包 Python 辅助工具需要 Python 3;提供数据前先查看样例结构。

需确认的适用边界

不负责联网发现来源。引用提取基于模式,需回查原文;PDF 文本提取可能需要其他工具。

04

安装与开始使用

将指令复制给 Codex 或 Claude Code,让助手从原始仓库下载固定提交,安装完整文件并检查所需依赖。

  1. 打开能访问本机文件和终端的 Codex 或 Claude Code。
  2. 复制下方指令发给正在使用的应用,由助手选择该应用的安装目录。
  3. 查看返回的安装路径和文件检查结果;需要时新建会话,再要求助手使用已安装的 Skill。
请在我当前使用的应用中安装 research-summarizer,直接执行文件安装,不要只解释步骤。 原始仓库:https://github.com/alirezarezvani/claude-skills.git 固定提交:6d2f02ea077eead1bee5411a31bcc6db5a11a70c Skill 路径:product-team/research-summarizer/skills/research-summarizer 1. 将这个版本下载到新目录。执行随包脚本前,先阅读 SKILL.md 和安装参考文件,不替换成其他作者的包。 2. Codex 安装到 ~/.agents/skills/research-summarizer,Claude Code 安装到 ~/.claude/skills/research-summarizer,只安装到我正在使用的应用。安装完整 Skill 文件夹,保留 scripts、references、assets 和随包声明;将仓库根目录许可证一并保留。先检查所有目标目录;已有安装时,说明差异后再决定是否替换。 3. 比较来源和安装目录的文件清单、文件哈希,检查文档要求的运行时、依赖及外部连接。只配置此 Skill 所需的本地依赖,适用时使用隔离环境;账号登录由我在本地完成,不把凭据贴进聊天。 4. 返回来源提交、实际安装路径、文件检查结果及尚未完成的运行环境配置,说明如何调用 research-summarizer。文件复制与应用发现分别检查,需要时新建会话。不要执行生产任务,也不要把安装完成说成已确认业务效果。
05

原始 Skill.md

以下为已核对版本未经改写的 SKILL.md。安装完整包才能保留引用的脚本、素材和指引。下方启动提示词为 EcomAgentTools 编写的示例。

---
name: "research-summarizer"
description: "Structured research summarization agent skill for non-dev users. Handles academic papers, web articles, reports, and documentation. Extracts key findings, generates comparative analyses, and produces properly formatted citations. Use when: user wants to summarize a research paper, compare multiple sources, extract citations from documents, or create structured research briefs. Plugin for Claude Code, Codex, Gemini CLI, and OpenClaw."
license: MIT
metadata:
  version: 1.0.0
  author: Alireza Rezvani
  category: product
  updated: 2026-03-16
---

# Research Summarizer

> Read less. Understand more. Cite correctly.

Structured research summarization workflow that turns dense source material into actionable briefs. Built for product managers, analysts, founders, and anyone who reads more than they should have to.

Not a generic "summarize this" — a repeatable framework that extracts what matters, compares across sources, and formats citations properly.

---

## Scope — Distinct From the research/ Domain

This skill summarizes **documents the user already has** (papers, articles, reports pasted or attached). It performs no web search and needs no MCP server. It is NOT:

- `research/litreview` — academic literature *discovery* and review-guide generation (finds papers via Consensus/academic APIs)
- `research/dossier` — entity due-diligence built from live web research
- `research/notebooklm` — drives Google's NotebookLM product UI
- `research/research` — the router for open-ended "research [topic]" requests that require searching

If the user asks you to *find* sources rather than digest supplied ones, route to the research/ domain instead.

---

## When This Skill Activates

Recognize these patterns from the user:

- "Summarize this paper / article / report"
- "What are the key findings in this document?"
- "Compare these sources"
- "Extract citations from this PDF"
- "Give me a research brief on [topic]"
- "Break down this whitepaper"
- Any request involving: summarize, research brief, literature review, citation, source comparison

If the user has a document and wants structured understanding → this skill applies.

---

## Workflow

### Workflow 1 — Single Source Summary

1. **Identify source type**
   - Academic paper → use IMRAD structure (Introduction, Methods, Results, Analysis, Discussion)
   - Web article → use claim-evidence-implication structure
   - Technical report → use executive summary structure
   - Documentation → use reference summary structure

2. **Scaffold the brief** — `python3 scripts/format_summary.py --template academic` (or `article`/`report`/`executive` per source type), then fill in every section from the source:
   ```
   Title: [exact title]
   Author(s): [names]
   Date: [publication date]
   Source Type: [paper | article | report | documentation]

   ## Key Thesis
   [1-2 sentences: the central argument or finding]

   ## Key Findings
   1. [Finding with supporting evidence]
   2. [Finding with supporting evidence]
   3. [Finding with supporting evidence]

   ## Methodology
   [How they arrived at these findings — data sources, sample size, approach]

   ## Limitations
   - [What the source doesn't cover or gets wrong]

   ## Actionable Takeaways
   - [What to do with this information]

   ## Notable Quotes
   > "[Direct quote]" (p. X)
   ```

3. **Assess quality**
   - Source credibility (peer-reviewed, reputable outlet, primary vs secondary)
   - Evidence strength (data-backed, anecdotal, theoretical)
   - Recency (when published, still relevant?)
   - Bias indicators (funding source, author affiliation, methodology gaps)

### Workflow 2 — Multi-Source Comparison

1. **Collect sources** (2-5 documents)
2. **Summarize each** using the single-source workflow above
3. **Build comparison matrix**

   ```
   | Dimension        | Source A        | Source B        | Source C        |
   |------------------|-----------------|-----------------|-----------------|
   | Central Thesis   | ...             | ...             | ...             |
   | Methodology      | ...             | ...             | ...             |
   | Key Finding      | ...             | ...             | ...             |
   | Sample/Scope     | ...             | ...             | ...             |
   | Credibility      | High/Med/Low    | High/Med/Low    | High/Med/Low    |
   ```

4. **Synthesize**
   - Where do sources agree? (convergent findings = stronger signal)
   - Where do they disagree? (divergent findings = needs investigation)
   - What gaps exist across all sources?
   - What's the weight of evidence for each position?

5. **Produce synthesis brief**
   ```
   ## Consensus Findings
   [What most sources agree on]

   ## Contested Points
   [Where sources disagree, with strongest evidence for each side]

   ## Gaps
   [What none of the sources address]

   ## Recommendation
   [Based on weight of evidence, what should the reader believe/do?]
   ```

### Workflow 3 — Citation Extraction

1. **Run the extractor** — `python3 scripts/extract_citations.py document.txt --output json` detects DOI/URL/author-year/numbered citations and deduplicates them
2. **Review and format** the extracted list in the requested style (APA 7 default); manually catch citations the regex missed
3. **Classify citations** by type:
   - Primary sources (original research, data)
   - Secondary sources (reviews, meta-analyses, commentary)
   - Tertiary sources (textbooks, encyclopedias)
4. **Output** sorted bibliography with classification tags

Supported citation formats:
- **APA 7** (default) — social sciences, business
- **IEEE** — engineering, computer science
- **Chicago** — humanities, history
- **Harvard** — general academic
- **MLA 9** — arts, humanities

---

## Tooling

### `scripts/extract_citations.py`

CLI utility for extracting and formatting citations from text.

**Features:**
- Regex-based citation detection (DOI, URL, author-year, numbered references)
- Multiple output formats (APA, IEEE, Chicago, Harvard, MLA)
- JSON export for integration with reference managers
- Deduplication of repeated citations

**Usage:**
```bash
# Extract citations from a file (APA format, default)
python3 scripts/extract_citations.py document.txt

# Specify format
python3 scripts/extract_citations.py document.txt --format ieee

# JSON output
python3 scripts/extract_citations.py document.txt --format apa --output json

# From stdin
cat paper.txt | python3 scripts/extract_citations.py --stdin
```

### `scripts/format_summary.py`

CLI utility that emits **blank structured summary scaffolds** — you (the model) fill them in from the source. It does not analyze content itself.

**Features:**
- 6 templates: academic, article, report, executive, comparison, literature
- Configurable scaffold depth (brief, standard, detailed)
- Text and JSON output for downstream tooling

**Usage:**
```bash
# Generate structured summary template
python3 scripts/format_summary.py --template academic

# Brief executive summary format
python3 scripts/format_summary.py --template executive --length brief

# All templates listed
python3 scripts/format_summary.py --list-templates

# JSON output
python3 scripts/format_summary.py --template article --output json
```

---

## Quality Assessment Framework

Rate every source on four dimensions:

| Dimension | High | Medium | Low |
|-----------|------|--------|-----|
| **Credibility** | Peer-reviewed, established author | Reputable outlet, known author | Blog, unknown author, no review |
| **Evidence** | Large sample, rigorous method | Moderate data, sound approach | Anecdotal, no data, opinion |
| **Recency** | Published within 2 years | 2-5 years old | 5+ years, may be outdated |
| **Objectivity** | No conflicts, balanced view | Minor affiliations disclosed | Funded by interested party, one-sided |

**Overall Rating:**
- 4 Highs = Strong source — cite with confidence
- 2+ Mediums = Adequate source — cite with caveats
- 2+ Lows = Weak source — verify independently before citing

---

## Summary Templates

See `references/summary-templates.md` for:
- Academic paper summary template (IMRAD)
- Web article summary template (claim-evidence-implication)
- Technical report template (executive summary)
- Comparative analysis template (matrix + synthesis)
- Literature review template (thematic organization)

See `references/citation-formats.md` for:
- APA 7 formatting rules and examples
- IEEE formatting rules and examples
- Chicago, Harvard, MLA quick reference

---

## Proactive Triggers

Flag these without being asked:

- **Source has no date** → Note it. Undated sources lose credibility points.
- **Source contradicts other sources** → Highlight the contradiction explicitly. Don't paper over disagreements.
- **Source is behind a paywall** → Note limited access. Suggest alternatives if known.
- **User provides only one source for a compare** → Ask for at least one more. Comparison needs 2+.
- **Citations are incomplete** → Flag missing fields (year, author, title). Don't invent metadata.
- **Source is 5+ years old in a fast-moving field** → Warn about potential obsolescence.

---

## Installation

### One-liner (any tool)
```bash
git clone https://github.com/alirezarezvani/claude-skills.git
cp -r claude-skills/product-team/research-summarizer ~/.claude/skills/
```

### Multi-tool install (run from the claude-skills repo root)
```bash
./scripts/convert.sh --skill research-summarizer --tool codex|gemini|cursor|windsurf|openclaw
```

### OpenClaw
```bash
clawhub install cs-research-summarizer
```

---

## Verification Loop

Before delivering any brief, check:

1. Every Key Finding cites a location in the source (section, page, or quote) — no unanchored claims.
2. `python3 scripts/extract_citations.py <file> --output json` exits 0 and its `total` matches the bibliography count in your output (investigate any gap).
3. Each source carries a 4-dimension quality rating (table above); weak sources are flagged, not silently included.
4. For comparisons: the matrix has one row per dimension and one column per source — no source skipped.
5. Nothing was invented: missing metadata is marked "not stated", never filled in.

---

## Related Skills

- **product-analytics** — Quantitative analysis. Complementary — use research-summarizer for qualitative sources, product-analytics for metrics.
- **competitive-teardown** — Competitive research. Complementary — use research-summarizer for individual source analysis, competitive-teardown for market landscape.
- **content-production** — Content writing. Research-summarizer feeds content-production — summarize sources first, then write.
- **product-discovery** — Discovery frameworks. Complementary — research-summarizer for desk research, product-discovery for user research.
06

开始使用

以下是主要功能的用例提示词,可以直接复制使用。

01

总结已提供的品类研究报告

总结已提供的品类研究报告 适用于:总结已提供的品类研究报告。请准备:论文、报告或提取后的文档文本、决策问题、所需详略和引用格式。

查看 Prompt 和变量收起 Prompt 和变量
请使用已安装的 research-summarizer Skill。任务:总结已提供的品类研究报告。输入:[INPUT]。限制:[CONSTRAINTS]。先检查缺失信息,再输出可审查的结果、依据、假设和下一步。不负责联网发现来源。引用提取基于模式,需回查原文;PDF 文本提取可能需要其他工具。

需要替换的变量

[INPUT]
论文、报告或提取后的文档文本、决策问题、所需详略和引用格式。
[CONSTRAINTS]
任务范围、允许的操作、输出格式和审核要求。
02

比较已提供论文的发现与局限

比较已提供论文的发现与局限 适用于:比较已提供论文的发现与局限。请准备:论文、报告或提取后的文档文本、决策问题、所需详略和引用格式。

查看 Prompt 和变量收起 Prompt 和变量
请使用已安装的 research-summarizer Skill。任务:比较已提供论文的发现与局限。输入:[INPUT]。限制:[CONSTRAINTS]。先检查缺失信息,再输出可审查的结果、依据、假设和下一步。不负责联网发现来源。引用提取基于模式,需回查原文;PDF 文本提取可能需要其他工具。

需要替换的变量

[INPUT]
论文、报告或提取后的文档文本、决策问题、所需详略和引用格式。
[CONSTRAINTS]
任务范围、允许的操作、输出格式和审核要求。
03

为决策简报提取并核对引用

为决策简报提取并核对引用 适用于:为决策简报提取并核对引用。请准备:论文、报告或提取后的文档文本、决策问题、所需详略和引用格式。

查看 Prompt 和变量收起 Prompt 和变量
请使用已安装的 research-summarizer Skill。任务:为决策简报提取并核对引用。输入:[INPUT]。限制:[CONSTRAINTS]。先检查缺失信息,再输出可审查的结果、依据、假设和下一步。不负责联网发现来源。引用提取基于模式,需回查原文;PDF 文本提取可能需要其他工具。

需要替换的变量

[INPUT]
论文、报告或提取后的文档文本、决策问题、所需详略和引用格式。
[CONSTRAINTS]
任务范围、允许的操作、输出格式和审核要求。
07

实际使用案例:核对两份资料是否支持“转化改善”的结论

商家提供经营报告和客服观察文章,两份资料对增长的解释不同。需要带来源位置的摘要、比较矩阵和能支持经营判断的综合结论。

使用步骤与 Prompt

  1. 准备下方案例输入资料,保留商品、政策和经营记录中的金额、单位及时间口径。
  2. 提取研究方法、样本、数字和局限,保留可追溯的引用,比较一致与冲突的证据,并说明能支持哪些决策。
  3. 提交下方完整 Prompt,查看右侧主要产物;需要交接给同事时,下载包含全部交付文件的压缩包。

案例输入资料:business-inputs.zip

Use the research-summarizer Skill.

Synthesize the supplied research notes for our ecommerce product team. Extract each source's question, method, sample, numerical findings and limitations; compare agreements and conflicts, retain traceable citations and quotations, and recommend the decisions the evidence can support plus the most useful next research step.

The attached business materials are:
- inputs/a.txt
- inputs/b.txt
- inputs/brief.txt

Deliver a complete result.md report that the operations team can read, plus any finished files needed for this task. Keep supporting calculations and evidence with the deliverables. Write the report in English; use the requested target language for customer-facing copy. The business datasets are fictional examples unless the brief explicitly names a live public website.

运行结果

下方直接展示本次 Prompt 产生的主要文件,保留实际输出语言。

Sales volume increased; the notes do not establish a conversion improvement

The operating report shows a flat 2.5% orders-to-sessions ratio despite 20% more orders. The support article gives a useful hypothesis about policy clarity, but its four selected conversations cannot establish a causal conversion improvement. Clarify confusing policy information, then measure the outcome with a defined funnel or experiment. Both sources are fictional research materials supplied for this case.

Source A: HarborMug weekly operating report

Author: Mia Lane. Organization: HarborMug. Document date: November 3, 2026. Type: internal technical report. Question: what changed between the two trading weeks?

Method and sample: two aggregate weekly rows, 100 orders/4,000 sessions then 120/4,800; no customer-level tracking or controlled experiment (A §2). Gross merchandise revenue increased from $2,400 to $2,880, +20%; refunds increased from $120 to $144; ad spend increased from $300 to $360. Gross excludes shipping revenue and tax.

Recalculation: 100/4,000 and 120/4,800 both equal 2.5%. Gross AOV remains $24. Net revenue after the supplied refund dollars is $2,280 then $2,736, +20%. Refund dollars/gross revenue remains 5%; this is not the percentage of orders returned. No realized profit can be established without the remaining costs and revenue definitions (A §§2–4).

Exact quotation: “Volume grew; conversion did not improve.” (A §3.) Read “conversion” here as the report's aggregate order/session ratio, not a deduplicated shopper purchase probability.

Source B: HarborMug support observations

Author: Alex Reed. Date: November 2, 2026. Type: supplied article text; no public URL. Question: could clearer delivery and return terms help shoppers?

Method and sample: four selected support conversations mentioning timing uncertainty, with no control group and no measured before/after conversion (B §2). The article's belief that conversion improved is unsupported by its own evidence and conflicts with Source A's aggregate ratio (B §1 versus A §3).

The policy facts are operationally useful: two-business-day dispatch, another three-to-five-business-day delivery estimate, $5 shipping below $50, free shipping at $50, US-only delivery and unused returns within 30 days requiring merchant refund approval (B §3). They do not prove that clarity caused any sales change.

Exact quotation: “Four conversations are a prompt to investigate, not a conversion study.” (B §2.) Convenience selection may overrepresent dissatisfied shoppers. Funding is not stated, the author is merchant-affiliated and opposing explanations were not tested (B §4).

Comparison and evidence quality

DimensionSource ASource B
Main claimVolume grew; order/session ratio flatPolicy clarity may help; improvement is only a belief
MethodTwo weekly aggregate rowsFour selected support conversations
Numeric scope220 orders, 8,800 sessions across both weeksFour conversations, no population denominator
StrengthArithmetic can be reproducedIdentifies a concrete customer question to investigate
CredibilityMedium: internal, not peer-reviewedLow: supplied opinion/article, no independent review
EvidenceMedium for descriptive arithmetic; low for causalityLow for conversion effects
RecencyHigh within the fictional exercise datesHigh within the fictional exercise dates
ObjectivityMedium: merchant-funded, limitations disclosedLow: merchant-affiliated convenience sample

Neither source is independent market evidence. The original extractor labels both citations primary; the operating table is primary descriptive data within the fixture, while the support article mixes primary observations with interpretation. Its interpretation should not acquire stronger status merely because a regex classified the citation.

Supported decisions and next research

First, keep dispatch and transit wording separate and show shipping thresholds near the buying decision. This follows the specific uncertainty in B §2 and the policy constraints in B §3. Second, retain the unchanged conversion finding in the weekly review rather than crediting the page for volume growth. Third, instrument unique shopper exposure and paid purchases, then define a comparison window or randomized test for policy presentation.

Before testing, inspect whether acquisition mix, stock or promotions changed; neither source covers those alternatives. Collect a consecutively sampled set of support questions, preserving anonymous record IDs and the denominator. Ask shoppers to explain delivery cost and timing without coaching. Use these observations to refine the intervention, not to manufacture a percentage uplift.

Bibliography and traceability

  1. Lane, M. (2026, November 3). HarborMug weekly operating report [Synthetic internal report]. HarborMug. Source a.txt, §§1–5. The extractor's supplied reference lists only the year; the full date above comes from the document header.
  2. Reed, A. (2026, November 2). HarborMug support observations [Synthetic supplied article]. HarborMug. Source b.txt, §§1–4. Public URL: not supplied.

brief.txt concatenates A and B and is not a third independent study. The original extraction tool found two citations, matching these two bibliography entries. Both quotations were checked verbatim against their source sections; the calculation file independently reproduces the numerical findings. No external research discovery or genuine merchant outcome is claimed.

案例中的商家经营资料为模拟数据;涉及网站检查时,报告中的页面观察来自所列公开网址。

08

风险与使用注意事项

已知限制

不负责联网发现来源。引用提取基于模式,需回查原文;PDF 文本提取可能需要其他工具。

证据与复核

核对源码及随包文件:GitHub 6d2f02ea077e。本次为静态审查,不代表已完成安装运行或业务效果测试。

采用结果前

使用获授权输入,不把密钥贴入提示词。采用前检查面向客户的声明、计算、代码改动及任何拟议的外部操作。

常见问题

它能做什么,有什么优势?

总结已提供文档、比较发现,并提取引用候选。结构化模板区分发现、方法、证据质量、局限和引用。

如何安装和开始使用?

按实际 Agent 选择方式,安装完整包,不要只复制页面中的 SKILL.md。 论文、报告或提取后的文档文本、决策问题、所需详略和引用格式。 开启新 Agent 会话,明确要求使用 research-summarizer。先用小型样本尝试下方一个场景,并检查输出。

适合哪些使用场景?

总结已提供的品类研究报告;比较已提供论文的发现与局限;为决策简报提取并核对引用

使用前需要了解哪些限制?

不负责联网发现来源。引用提取基于模式,需回查原文;PDF 文本提取可能需要其他工具。

本页核对了什么?

核对源码及随包文件:GitHub 6d2f02ea077e。本次为静态审查,不代表已完成安装运行或业务效果测试。

暂无评论。

发表评论

请先为每一项打分,再分享你的真实使用体验。

任务有效性
安装与使用难度
稳定性与边界
文档清晰度
首次获得有效结果
作者 / 维护者

Alireza Rezvani

核对源码及随包文件:GitHub 6d2f02ea077e。本次为静态审查,不代表已完成安装运行或业务效果测试。