$ loading_
整合多来源检索结果，去重归纳并附来源与置信度说明。
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "knowledge-synthesis" 技能： 1. 下载 https://raw.githubusercontent.com/anthropics/knowledge-work-plugins/main/enterprise-search/skills/knowledge-synthesis/SKILL.md 2. 保存为 ~/.claude/skills/knowledge-synthesis/SKILL.md 3. 装好后重载技能，告诉我可以用了
请整合我提供的多个竞品搜索结果，去除重复信息，按产品功能、定价、目标用户分类总结，并为每条结论标注来源与置信度。
一份结构化竞品摘要，包含分类结论、引用来源与置信度说明。
基于以下多个来源的研究结果，生成一份统一综述：提炼核心观点，指出相互一致与冲突之处，并根据来源权威性和时间新鲜度给出置信度判断。
一份带有共识、分歧和置信度评估的研究综述。
我有一批关于某主题的搜索结果，请把它们压缩成简洁答案：合并重复内容，保留关键信息，列出主要来源，并说明哪些结论最可靠。
一份简明答案，覆盖重点结论、主要来源及可靠性判断。
The last mile of enterprise search. Takes raw results from multiple sources and produces a coherent, trustworthy answer.
Transform this:
~~chat result: "Sarah said in #eng: 'let's go with REST, GraphQL is overkill for our use case'"
~~email result: "Subject: API Decision — Sarah's email confirming REST approach with rationale"
~~cloud storage result: "API Design Doc v3 — updated section 2 to reflect REST decision"
~~project tracker result: "Task: Finalize API approach — marked complete by Sarah"
Into this:
The team decided to go with REST over GraphQL for the API redesign. Sarah made the
call, noting that GraphQL was overkill for the current use case. This was discussed
in #engineering on Tuesday, confirmed via email Wednesday, and the design doc has
been updated to reflect the decision. The related ~~project tracker task is marked complete.
Sources:
- ~~chat: #engineering thread (Jan 14)
- ~~email: "API Decision" from Sarah (Jan 15)
- ~~cloud storage: "API Design Doc v3" (updated Jan 15)
- ~~project tracker: "Finalize API approach" (completed Jan 15)
The same information often appears in multiple places. Identify and merge duplicates:
Signals that results are about the same thing:
How to merge:
When the same information exists in multiple sources, prefer:
1. The most complete version (fullest context)
2. The most authoritative source (official doc > chat)
3. The most recent version (latest update wins for evolving info)
Keep as separate items when:
Every claim in the synthesized answer must be attributable to a source.
Inline for direct references:
Sarah confirmed the REST approach in her email on Wednesday.
The design doc was updated to reflect this (~~cloud storage: "API Design Doc v3").
Source list at the end for completeness:
Sources:
- ~~chat: #engineering discussion (Jan 14) — initial decision thread
- ~~email: "API Decision" from Sarah Chen (Jan 15) — formal confirmation
- ~~cloud storage: "API Design Doc v3" last modified Jan 15 — updated specification
Not all results are equally trustworthy. Assess confidence based on:
| Recency | Confidence impact |
|---|---|
| Today / yesterday | High confidence for current state |
| This week | Good confidence |
| This month | Moderate — things may have changed |
| Older than a month | Lower confidence — flag as potentially outdated |
For status queries, heavily weight freshness. For policy/factual queries, freshness matters less.
| Source type | Authority level |
|---|---|
| Official wiki / knowledge base | Highest — curated, maintained |
…
围绕客户问题进行多来源调研与溯源，快速整理背景并支持准确回复。
跨多个 Notion 信息源检索并整合，生成带引用的结构化文档与报告。