Token导航 LogoToken导航

Agent Skill · 研究检索

synthesize(synthesize 搜索)

synthesize 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

synthesize 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为执行命令;许可证信息还不明确,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 70,604。

总安装 210周安装 9GitHub Stars 42下载 73核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:synthesize(synthesize 搜索)
来源仓库:https://github.com/taylorhuston/local-life-manager
仓库路径:skills/synthesize
安装命令:
npx skills add https://github.com/taylorhuston/local-life-manager --skill synthesize
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/taylorhuston/local-life-manager --skill synthesize

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

synthesize 搜索用于查找、检索和筛选相关信息。适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词、任务场景快速定位候选结果。通过 npx skills add 命令从指定 GitHub 仓库安装,需结合原始 README 确认具体用法。

安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写操作。该工具适用于需要高效信息检索和筛选的研究与决策场景。

来源仓库内路径:skills/synthesize

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/taylorhuston/local-life-manager --skill synthe…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要执行命令,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

synthesize 怎么安装?

在终端执行 npx skills add https://github.com/taylorhuston/local-life-manager --skill synthesize。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

synthesize 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

synthesize 需要什么权限?

权限级别是执行命令。安装流程涉及命令执行,可能通过 npx skills add https://github.com/taylorhuston/local-life-manager --skill synthesize 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

synthesize 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

synthesize 用的人多吗?

公开数据是累计安装 210 次,近一周安装 9 次,下载 73 次,GitHub 42 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

synthesize 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。

先想清楚的地方

  • 需要执行命令,装到常用环境前要先评估影响面。
  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 不能接受 Skill 在你机器上执行命令的人。
  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
synthesize

synthesize 搜索 · 本页

21042执行命令未明确有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Create and incrementally build synthesis documents from multiple sources.

Output Location

All synthesis documents go in: my-vault/06 Knowledge Base/Synthesis/[Topic]/

Structure:

my-vault/06 Knowledge Base/Synthesis/
└── ADHD/
    ├── ADHD Synthesis.md              # Main synthesis
    ├── ADHD Sources.md                # Sources table + processing log
    └── ADHD Medications Synthesis.md  # Sub-topic (if created)

Queue Files

Queues live in: .claude/skills/synthesize/references/queues/[topic].json

{
  "name": "ADHD",
  "topic_folder": "ADHD",
  "batch_size": 3,
  "max_discovered_per_source": 3,
  "watch_patterns": [
    "my-vault/06 Knowledge Base/Capture/Videos/**/*ADHD*.md",
    "my-vault/01 Inbox/*adhd*.md",
    "my-vault/04 Personal/Health/*ADHD*.md"
  ],
  "sources": [
    {"path": "my-vault/path/to/note.md", "status": "pending", "type": "local"},
    {"path": "my-vault/path/to/video.md", "status": "processed", "type": "local"},
    {"url": "https://example.com/study", "status": "pending", "type": "web",
     "discovered_from": "src-2", "context": "Key study on medication timing"},
    {"search": "Barkley 2023 executive function", "status": "pending", "type": "search",
     "discovered_from": "src-2", "context": "Referenced as foundational research"}
  ],
  "last_run": "2026-01-14T10:00:00Z"
}

Source types:

  • local - Path to existing note in my-vault
  • web - URL to fetch and process
  • search - Search query to find the source (use WebSearch, then fetch best result)

Source status values: pending, processed, skipped

watch_patterns: Glob patterns for /synthesize update to scan. Paths matching these patterns get added to the queue automatically (if not already present).

Commands

  • /synthesize [topic] - Continue processing the named synthesis
  • /synthesize list - Show all active synthesis queues and progress
  • /synthesize new [topic] - Create a new synthesis queue
  • /synthesize add [topic] [path-or-glob] - Add sources to a queue
  • /synthesize update [topic] - Scan watch_patterns for new sources and add to queue

Architecture

This skill uses a coordinator + subagent pattern for efficient processing:

  • Coordinator (Sonnet/Opus): Manages state, spawns extractors, merges findings into synthesis
  • Extractors (Haiku subagents): Each reads one source, extracts structured findings in parallel

This allows processing 6-10 sources per batch instead of 2-3, with ~3x throughput improvement.

Workflow

Starting a Session

  1. Load queue file for the topic
  2. Read the main synthesis doc (or create from template if first run)
  3. Read the sources file
  4. Identify next N pending sources (N = 6-10 for parallel extraction)

Phase 1: Parallel Extraction (Haiku Subagents)

Spawn 6-10 Haiku extractors in parallel using the Task tool:

Task tool call:
- model: haiku
- subagent_type: general-purpose
- prompt: (see Extractor Prompt Template below)

Extractor Prompt Template:

Read this file and extract [TOPIC]-relevant findings in a structured format.

FILE: [full path to source]

Return your findings as a simple list in this format:
CATEGORY: [Category Name]
- Finding 1 (be specific, include numbers/names if mentioned)
- Finding 2
...

Only include substantive findings relevant to understanding [TOPIC].
Skip metadata, timestamps, and filler.
If the source has little new information, just return "MINIMAL_CONTENT".

For web sources, modify prompt to use WebFetch first:

1. Use WebFetch to retrieve: [URL]
2. Extract [TOPIC]-relevant findings from the content...

For search sources, modify prompt to search first:

1. Use WebSearch to find: [search query]
2. Use WebFetch on the best result
3. Extract [TOPIC]-relevant findings...

Phase 2: Merge Findings (Coordinator)

Once all extractors return:

  1. Collect all extraction results
  2. Review for:

- New findings to add to existing categories - Findings that warrant new categories - Contradictions with existing content → add to Open Questions - Dense categories → add to Suggested Sub-Topics

  1. Update synthesis doc with citations (^[src-N])
  2. Add sources to Sources table
  3. Mark sources as processed in queue

Phase 3: Discovery (Coordinator)

While reviewing extractions, watch for references worth following up:

  • Studies or papers cited
  • Articles or books mentioned
  • Other videos or talks referenced
  • Experts or researchers named

Limit: 3 discovered sources per source processed.

Discovery

While processing each source, watch for references worth following up:

  • Studies or papers cited
  • Articles or books mentioned
  • Other videos or talks referenced
  • Experts or researchers named (for potential lookup)

Limit: 3 discovered sources per source processed.

For each valuable reference:

  1. Check if already in queue (deduplicate by URL, title, or path)
  2. Add to queue with:

- type: web if URL available, search if just a name/title - discovered_from: source ID where you found it - context: why it's relevant (1 sentence) - status: pending

Prioritize discoveries that:

  • Are directly cited as evidence for claims
  • Come from credible sources (peer-reviewed, recognized experts)
  • Fill gaps in the current synthesis

Skip discovering:

  • Tangential references not central to the topic
  • Sources that would require paid access (note in processing log if significant)
  • Generic resources (e.g., "see Wikipedia for more")

Ending a Session

  1. Write updated synthesis doc
  2. Write updated sources file
  3. Write updated queue file with new last_run timestamp
  4. Add entry to Processing Log (include discovery count)
  5. Report: ` Processed X items. Discovered Y new sources. Z items remaining. Run /synthesize [topic] to continue. `

If all sources processed:

Synthesis complete. X total sources processed.
Review Suggested Sub-Topics for potential expansion.

Updating a Synthesis (/synthesize update [topic])

Use this to find new sources that match watch_patterns without reprocessing old ones.

  1. Load queue file for the topic
  2. Collect all paths from watch_patterns using Glob
  3. Filter out any paths already in sources (regardless of status)
  4. Add new matches to sources with:

- type: local - status: pending

  1. Update queue file
  2. Report: ` Found X new sources matching watch_patterns. Queue now has Y pending items. Run /synthesize [topic] to process. `

If no new sources found:

No new sources found. Synthesis is up to date with watch_patterns.

Tip: Run /synthesize update [topic] periodically after adding new notes or video summaries to keep the synthesis current.

Synthesis Document Template

Create at: my-vault/06 Knowledge Base/Synthesis/[Topic]/[Topic] Synthesis.md

---
class: Synthesis
topic: [Topic Name]
created: [Date]
lastUpdated: [Date]
status: in-progress
---

## Overview

[2-3 sentence summary of the topic - updated as understanding deepens]

## Key Findings

### [Category]

- Finding with specific details ^[src-1]
- Another finding that multiple sources support ^[src-1] ^[src-3]

<!-- Add categories as needed based on source content -->

## Open Questions

<!-- Contradictions, uncertainties, areas needing human judgment -->

- **[Topic]**: Source A says X ^[src-1], but Source B says Y ^[src-2].

## Suggested Sub-Topics

<!-- Categories that could warrant their own synthesis -->

- **[Sub-topic]** - X sources touched on this; may warrant dedicated synthesis

---
*Sources and processing log: [[Topic Sources]]*

Sources Document Template

Create at: my-vault/06 Knowledge Base/Synthesis/[Topic]/[Topic] Sources.md

---
class: Note
parent: "[[Topic Synthesis]]"
---

## Sources

| ID | Title | Date | Type | Discovered | Path/URL |
|----|-------|------|------|------------|----------|
| src-1 | Source Title | 2025-03 | Video | - | [[path/to/note]] |
| src-2 | Study Name | 2024-11 | Web | from src-1 | [link](url) |

## Processing Log

- **2026-01-14**: Initial synthesis. Processed 3 items. Created categories for X, Y, Z. Discovered 2 new sources.
- **2026-01-15**: Processed 3 items. Flagged contradiction on [topic]. Discovered 1 new source.

Length Discipline

Core content (Overview through Suggested Sub-Topics) must stay under 300 lines.

Guidelines:

  • Overview: 5 lines max
  • Categories: 8 max in main doc
  • Points per category: 15 max
  • Open Questions: 10 max

When a category exceeds ~40-50 lines or has 5+ sources going deep:

  1. Summarize tightly in the main doc (5-10 key points)
  2. Add to Suggested Sub-Topics
  3. Sub-topic syntheses get their own doc in the same folder, linking back to parent

Handling Contradictions

When new information conflicts with existing content:

  1. Do not silently replace the existing information
  2. Move both claims to Open Questions with citations: - **Medication timing**: Take with food for reduced side effects ^[src-2], but empty stomach for faster absorption ^[src-5]. May depend on specific medication.
  3. If a clear resolution exists (newer research, more credible source, broader consensus), note it: - **Resolved**: Earlier sources suggested X, but consensus now supports Y ^[src-8] ^[src-9] ^[src-10]

Citation Format

Use ^[source-id] inline, where source-id matches the ID column in the Sources table.

  • Single source: Finding here ^[src-1]
  • Multiple sources: Well-supported finding ^[src-1] ^[src-3] ^[src-7]
  • Conflicting sources: Note in Open Questions section

Adding Sources to Queue

Manual Addition

/synthesize add adhd my-vault/path/to/specific/note.md

Glob Pattern

/synthesize add adhd "my-vault/06 Knowledge Base/Capture/Videos/**/*ADHD*.md"

By Tag (search and add)

When adding, search for relevant notes:

  • Notes with topic in filename
  • Notes with relevant tags
  • Video summaries from relevant channels

Deduplicate against existing sources in queue before adding.

Creating Sub-Topic Syntheses

When a sub-topic warrants its own document:

  1. Create new queue: /synthesize new "ADHD Medications"
  2. Set topic_folder to match parent: "ADHD" (keeps files together)
  3. Add relevant sources (can include already-processed sources from parent for deeper dive)
  4. In parent synthesis, add link: See also: [[ADHD Medications Synthesis]]
  5. In sub-topic synthesis Overview, note parent: Deep-dive from [[ADHD Synthesis]]

平台分布

Codex

32.09%
按下载量换算23

Claude

30.7%
按下载量换算22

Cursor

19.24%
按下载量换算14

Gemini CLI

8.44%
按下载量换算6

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

执行命令

安装流程涉及命令执行,可能通过 npx skills add https://github.com/taylorhuston/local-life-manager --skill synthesize 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills