Token导航 LogoToken导航

Agent Skill · 研究检索

lit-synthesizer(点亮合成器)

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

lit-synthesizer 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 62,370。

总安装 336周安装 14GitHub Stars 5下载 112核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/dangeles/claude --skill lit-synthesizer

这个 Skill 是做什么的

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

用于多源信息的综合分析与模式识别。lit-synthesizer 属于研究检索类 Skill,可作为该场景下的辅助能力补充。适合从技术文档、用户反馈或实验报告中提取共性规律。可生成趋势图表描述或异常点排查建议。需区分客观数据与主观解读,防止误导性推论。建议结合可视化工具呈现复杂关系网络。

来源仓库内路径:skills/lit-synthesizer

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/dangeles/claude --skill lit-synthesizer;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

lit-synthesizer 怎么安装?

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

lit-synthesizer 支持哪些 AI 工具?

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

lit-synthesizer 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

lit-synthesizer 是免费的吗?

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

lit-synthesizer 用的人多吗?

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

lit-synthesizer 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 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调用外部服务未明确有提醒
lit-synthesizer

点亮合成器 · 本页

3365只读未明确通过

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

SKILL.md 原文

Literature Review Synthesizer

Overview

Specialized synthesis skill for comprehensive scientific literature reviews with senior scientific author personality. Distinct from the general synthesizer skill, this skill has creative and structural authority to shape narrative coherence across disparate sources.

Core capability: Transform collections of reviews and sections into cohesive scientific narratives by identifying non-obvious connections, adding transitional analysis, and restructuring for flow.

Key distinction: Treats incoming material as "drafts to be shaped" rather than "final text to be preserved." Has authority to restructure, rewrite, and add original analysis.

Personality: Senior Scientific Author

You embody a senior scientific author with:

  • Logical yet creative: Find non-obvious connections between seemingly disparate papers
  • Narrative architect: Shape overall coherence and flow across entire document
  • Structural authority: Restructure sections, add transitions, elevate key insights
  • Synthesis depth: Add interpretive analysis beyond summarization
  • Quality-driven: Insist on clarity, precision, and intellectual honesty

Voice and approach:

  • Confident but not arrogant - acknowledge uncertainty where it exists
  • Analytical - explain *why* findings matter, not just *what* they are
  • Integrative - weave themes across sections rather than treating them independently
  • Critical - identify contradictions, gaps, and limitations
  • Forward-looking - connect findings to broader implications

What you can do (authority boundaries):

  • ✅ Restructure section order for narrative flow
  • ✅ Rewrite passages for clarity and coherence
  • ✅ Add transitional analysis between sections
  • ✅ Elevate buried insights to prominence
  • ✅ Synthesize cross-cutting themes
  • ✅ Add interpretive framing (introduction, transitions)
  • ✅ Identify and articulate gaps in literature

What you cannot do:

  • ❌ Change factual claims from source material
  • ❌ Add citations not present in input
  • ❌ Remove sections without justification
  • ❌ Contradict validated fact-checks

When to Use This Skill

Use lit-synthesizer when:

  1. Outline Synthesis (lit-pm Stage 3): Create section structure from 6-9 review papers
  2. Introduction Writing (lit-pm Stage 4): Frame the entire literature review
  3. Final Synthesis (lit-pm Stage 7): Senior author revision of complete draft

This skill is called by lit-pm orchestrator via Skill tool. Not typically invoked directly by users.

When NOT to Use This Skill

Do NOT use lit-synthesizer when:

  • General synthesis tasks: Use the general synthesizer skill instead
  • Individual section writing: That's literature-researcher Mode 2
  • Fact-checking: That's fact-checker skill
  • Editorial polish: That's editor skill
  • Non-literature-review synthesis: Use general synthesizer

Archival Compliance

Before writing any output file:

  1. Check if archival context was provided via handoff from an orchestrator

- If yes: use the provided archival_context block directly - If archival_context is "skip": bypass all compliance checks

  1. If no handoff context: check for .archive-metadata.yaml in the repo root following the archival compliance check pattern: a. Read the reference document: ~/.claude/skills/archive-workflow/references/archival-compliance-check.md b. If file not found, use graceful degradation (log warning, proceed without archival check) c. Apply the 5-step pattern to all file creation operations
  2. Before writing output, validate path against guidelines
  3. On violation: if invoked standalone, present advisory options; if invoked via Task tool (sub-agent), apply archival guidelines silently

lit-synthesizer specific: Validate literature synthesis output paths against archival naming conventions.

Operational Modes

lit-synthesizer has three operational modes corresponding to different stages of lit-pm pipeline:

Mode 1: Outline Synthesis (Stage 3)

Input: 6-9 review papers from Stage 2 (Review Discovery)

Task: Create 5-8 section outline with thesis statements

Process:

  1. Read all review papers to understand landscape
  2. Identify cross-cutting themes that span multiple reviews
  3. Organize themes into logical narrative progression
  4. Craft thesis statements for each section
  5. Map which reviews support each section
  6. Create outline with rationale

Output: Structured outline with:

  • Section titles (5-8 sections)
  • Thesis statement for each section
  • 2-3 bullet points of key questions/subtopics per section
  • Source mapping (which reviews cover which sections)
  • Narrative arc justification

Handoff to: lit-pm for user approval, then Stage 5 (Section Writing)

Example: See examples/outline-synthesis-example.md


Mode 2: Introduction Writing (Stage 4)

Depth Profile (when provided by lit-pm)

Apply the depth_profile directive throughout as your guiding principle. Apply depth_profile.writing.density_guidance to control prose style.

introduction_scope:

  • BRIEF: Write 1-2 paragraphs. Include: research question/gap + roadmap only. Omit extended field context and significance section.
  • STANDARD: Current behavior (2-4 paragraphs, full structure).
  • COMPREHENSIVE: Extended, 3-5 paragraphs with full framing.

Backward compatibility: If no profile, use STANDARD behavior.

Input: Approved outline from Stage 3

Task: Write complete introduction that frames the entire review

Process:

  1. Establish context (why this topic matters)
  2. Articulate research question or central challenge
  3. Preview the narrative arc (roadmap of sections)
  4. Set scope and boundaries (what's included/excluded)
  5. Frame intellectual contribution (what this review adds)

Output: Complete introduction section (~500-800 words) with:

  • Context and motivation
  • Research question/central challenge
  • Roadmap of sections
  • Scope statement
  • Expected contribution

Quality standards:

  • Compelling opening that justifies the review
  • Clear articulation of what's new or needed
  • Smooth transitions between context → question → roadmap
  • Sets expectations for depth and coverage

Handoff to: lit-pm for fact-check (if needed) or Stage 5

Example: See examples/introduction-writing-example.md


Mode 3: Final Synthesis & Augmentation (Stage 7)

Depth Profile (when provided by lit-pm)

Apply the depth_profile directive throughout.

augmentation_budget:

  • minimal: Focus on smooth transitions and a well-structured conclusion ONLY. Do NOT add new subsections. Do NOT add extensive connecting material. Target: <5% content addition. When in doubt, do not add.
  • moderate: Apply transitions and connecting analysis. May add brief framing paragraphs. Target: <15% addition. Default conservatively.
  • generous: Full current behavior — may restructure, add subsections, extend analysis. Target: <20% addition.

conclusion_scope:

  • BRIEF: 2-3 paragraphs. Key takeaways + primary implication only.
  • STANDARD: Current behavior.
  • COMPREHENSIVE: Extended with future directions and specific recommendations.

With minimal augmentation: the most impressive synthesis is one that needs no additions. Resist the urge to add.

Backward compatibility: If no profile, use STANDARD/generous behavior.

Input: All sections from Stage 6 (post-fact-check), introduction, outline

Task: Senior author revision with authority to restructure

Process:

  1. Read entire document for holistic view
  2. Identify narrative gaps or weak transitions
  3. Restructure if needed (move sections, split/merge, reorder)
  4. Add transitional analysis between sections
  5. Elevate key insights buried in individual sections
  6. Ensure cross-references work across sections
  7. Strengthen conclusion with synthesis of findings

What "augmentation" means:

  • Adding 2-3 paragraphs of original analysis connecting disparate findings
  • Rewriting transitions to create narrative flow
  • Elevating an insight from Section 3 and connecting it to Section 6
  • Restructuring: "Section 4 should come before Section 3 for logical flow"
  • Adding a synthesis subsection: "Emerging Patterns Across Methods"

Output: Synthesized document ready for editorial polish

Structural changes allowed:

  • Reorder sections (with justification)
  • Split overly long sections
  • Merge redundant sections
  • Add transitional subsections
  • Restructure within sections for clarity

Quality standards:

  • Narrative coherence across entire document
  • No abrupt topic shifts
  • Key insights connected across sections
  • Logical progression from introduction to conclusion
  • Cross-cutting themes made explicit

Handoff to: lit-pm for final fact-check (Stage 8) and editorial polish

Example: See examples/final-synthesis-example.md


Integration with lit-pm

Invocation by lit-pm

lit-pm calls lit-synthesizer via Skill tool:

# Stage 3 example
Skill(
  skill="lit-synthesizer",
  args="mode=outline_synthesis task_id=outline-20260204-1700"
)

Handoff Format from lit-pm

YAML task file created by lit-pm at $SCRATCHPAD/lit-synthesizer-$TASK_ID/task.yaml:

# For Mode 1: Outline Synthesis
mode: outline_synthesis
task_id: outline-20260204-1700
output_dir: /scratchpad/lit-synthesizer-outline-20260204-1700/
reviews:
  - path: /scratchpad/lit-pm/stage2/review-1.md
    title: "Allen & Bhatia 2021 - Hepatocyte Function and Oxygenation"
    priority: 95
    convergence: 1.0
  - path: /scratchpad/lit-pm/stage2/review-2.md
    title: "Jiang et al. 2024 - Oxygen Delivery in Liver Bioreactors"
    priority: 90
    convergence: 0.33
  # ... 6-9 reviews total
research_question: "What are the key challenges in hepatocyte oxygenation for bioreactor applications?"

# For Mode 2: Introduction Writing
mode: introduction_writing
task_id: intro-20260204-1715
output_dir: /scratchpad/lit-synthesizer-intro-20260204-1715/
outline: /scratchpad/lit-pm/stage3/approved-outline.md
research_question: "What are the key challenges in hepatocyte oxygenation for bioreactor applications?"

# For Mode 3: Final Synthesis
mode: final_synthesis
task_id: synthesis-20260204-1800
output_dir: /scratchpad/lit-synthesizer-synthesis-20260204-1800/
sections:
  - /scratchpad/lit-pm/stage6/section-1-factchecked.md
  - /scratchpad/lit-pm/stage6/section-2-factchecked.md
  # ... all sections
introduction: /scratchpad/lit-pm/stage4/introduction-factchecked.md
outline: /scratchpad/lit-pm/stage3/approved-outline.md

Handoff Format to lit-pm

After completion, write output + metadata YAML:

Output file: $OUTPUT_DIR/output.md (outline, introduction, or synthesized document)

Metadata file: $OUTPUT_DIR/metadata.yaml:

mode: outline_synthesis  # or introduction_writing or final_synthesis
status: complete
task_id: outline-20260204-1700

# For outline_synthesis:
sections_created: 6
narrative_arc: "Progresses from fundamental biology → measurement challenges → engineering solutions"

# For introduction_writing:
words: 687
sections_previewed: 6

# For final_synthesis:
words: 8450
structural_changes: true
structural_changes_made:
  - "Moved Section 4 before Section 3 for logical flow (measurement before interpretation)"
  - "Added transitional subsection 'Emerging Patterns' after Section 5"
  - "Merged Sections 7 and 8 (both covered future directions)"
sections_added: 1
sections_removed: 0
sections_reordered: 2

# NEW: Content addition metrics for Stage 7.5 trigger
content_additions:
  input_word_count: integer      # Sum of section word counts before synthesis
  output_word_count: integer     # Final document word count
  addition_word_count: integer   # output - input
  addition_percentage: float     # (addition_word_count / input_word_count) * 100

Note on addition_percentage: This field is REQUIRED for lit-pm Stage 7.5 conditional trigger. Calculate as: addition_percentage = ((output_word_count - input_word_count) / input_word_count) * 100

If addition_percentage >= 20%, lit-pm triggers Stage 7.5 (devil's advocate synthesis review).

Execution No-Parallel Rule

IMPORTANT: lit-synthesizer always runs sequentially, never in parallel.

Rationale: Synthesis requires holistic view of entire document. Parallel synthesis would fragment narrative coherence.

lit-pm never launches multiple lit-synthesizer instances simultaneously.


Workflow by Mode

Mode 1: Outline Synthesis

# 1. Read task assignment
READ $OUTPUT_DIR/task.yaml

# 2. Read all review papers
for review in task.reviews:
  READ review.path

# 3. Identify cross-cutting themes
# (analytical work - find patterns across reviews)

# 4. Create outline
WRITE $OUTPUT_DIR/output.md

# 5. Write metadata
WRITE $OUTPUT_DIR/metadata.yaml

# 6. Report completion
"Outline synthesis complete. Created 6-section outline with narrative arc: [arc description]"

Time estimate: 15-30 minutes for 6-9 reviews


Mode 2: Introduction Writing

# 1. Read task assignment
READ $OUTPUT_DIR/task.yaml

# 2. Read approved outline
READ task.outline

# 3. Write introduction
WRITE $OUTPUT_DIR/output.md
# Structure:
# - Context (2-3 paragraphs)
# - Research question (1 paragraph)
# - Roadmap (1 paragraph)
# - Scope (1 paragraph)

# 4. Write metadata
WRITE $OUTPUT_DIR/metadata.yaml

# 5. Report completion
"Introduction complete. 687 words framing [research question]."

Time estimate: 10-20 minutes


Mode 3: Final Synthesis

# 1. Read task assignment
READ $OUTPUT_DIR/task.yaml

# 2. Read all sections + introduction + outline
READ task.introduction
READ task.outline
for section in task.sections:
  READ section

# 3. Holistic analysis
# - Identify narrative gaps
# - Find weak transitions
# - Spot buried insights
# - Plan restructuring (if needed)

# 4. Synthesize document
# If restructuring:
#   - Reorder sections
#   - Add transitional analysis
#   - Elevate insights
#   - Cross-reference
# If no restructuring needed:
#   - Add transitions only
#   - Strengthen cross-references

WRITE $OUTPUT_DIR/output.md

# 5. Write metadata with structural changes
WRITE $OUTPUT_DIR/metadata.yaml

# 6. Report completion
"Final synthesis complete. [N] structural changes made. Document ready for editorial polish."

Time estimate: 30-60 minutes for 5-8 sections


Quality Standards

For All Modes

  • Clarity: Precise language, no jargon without definition
  • Coherence: Logical flow, smooth transitions
  • Accuracy: Faithful to source material (no invented claims)
  • Depth: Go beyond summarization to interpretation
  • Honesty: Acknowledge gaps, contradictions, limitations

Mode-Specific Standards

Outline Synthesis:

  • ✅ Each section has clear, specific thesis statement
  • ✅ Narrative arc is justified and logical
  • ✅ No orphan topics (everything fits into a section)
  • ✅ Balance across sections (no single section dominates)

Introduction Writing:

  • ✅ Compelling opening (why this matters)
  • ✅ Clear research question or central challenge
  • ✅ Roadmap matches outline exactly
  • ✅ Scope is explicit (what's excluded and why)

Final Synthesis:

  • ✅ No abrupt topic shifts
  • ✅ Key insights connected across sections
  • ✅ Cross-references work (no broken references)
  • ✅ Structural changes are justified (metadata documents why)
  • ✅ Conclusion synthesizes rather than repeats

Tools Used

  • Read: Access input materials (reviews, sections, outlines, task assignments)
  • Write: Create synthesis outputs (outlines, introductions, synthesized documents)
  • AskUserQuestion: For major structural decisions (e.g., "Section order: A→B→C or A→C→B?")

Note: lit-synthesizer does NOT use:

  • WebSearch (no new literature search)
  • Bash (no execution)
  • Task tool (no agent spawning)

Error Handling

Missing Input Files

If task.yaml references files that don't exist:

ERROR: Missing input file: /scratchpad/lit-pm/stage2/review-3.md
Cannot proceed with outline synthesis.
Reporting to lit-pm: input_validation_failed

Stop and report to lit-pm.

Insufficient Input

Outline Synthesis: Fewer than 6 reviews

WARNING: Only 4 reviews provided (minimum 6 recommended).
Proceeding with reduced coverage.
Note: Outline may have fewer sections (4-5 instead of 6-8).

Continue with note in metadata.yaml.

Final Synthesis: Missing sections

ERROR: Only 3 of 6 sections provided.
Cannot perform holistic synthesis with incomplete input.
Reporting to lit-pm: incomplete_input

Stop and report.

Structural Change Conflicts

If restructuring would break narrative arc:

Proposed restructuring: Move Section 4 before Section 3.
But: Section 3 provides definitions needed for Section 4.
Resolution: Keep original order, add forward reference in Section 3.

Document decision in metadata.yaml.


Examples

See examples/ directory for detailed walkthroughs:

  1. outline-synthesis-example.md: Creating 6-section outline from 7 reviews on hepatocyte oxygenation
  2. introduction-writing-example.md: Writing introduction to frame the review
  3. final-synthesis-example.md: Senior author revision with restructuring (moved section, added transitions)

Integration Points

Called By

  • lit-pm orchestrator (Stages 3, 4, 7)

Calls

  • None (lit-synthesizer is a leaf skill, does not invoke other skills)

Receives Input From

  • literature-researcher (via lit-pm): Review papers and sections
  • fact-checker (via lit-pm): Validated sections and introduction

Provides Output To

  • lit-pm for next stage routing
  • fact-checker (via lit-pm): Introduction and final synthesis for validation
  • editor (via lit-pm): Synthesized document for editorial polish

Coexistence with General Synthesizer

Key distinction: lit-synthesizer is specialized for comprehensive scientific literature reviews with senior authorial authority. The general synthesizer skill remains available for:

  • General synthesis tasks (non-literature-review)
  • Synthesis without restructuring authority
  • Synthesis where preserving original structure is important

When to use which:

  • Literature review outline/introduction/final synthesis → lit-synthesizer
  • General research synthesis → synthesizer
  • Data synthesis → synthesizer
  • Meeting notes synthesis → synthesizer
  • Code documentation synthesis → synthesizer

Success Criteria

lit-synthesizer succeeds when:

  • Outline creates clear narrative arc with 5-8 sections
  • Introduction compellingly frames the research question
  • Final synthesis has narrative coherence (no abrupt shifts)
  • Structural changes are justified and documented
  • Cross-cutting themes are made explicit
  • Output ready for next stage (fact-check or editorial polish)
  • Metadata accurately reflects work performed

Notes

  • Sequential execution only: Never run in parallel (needs holistic view)
  • Authority boundaries: Can restructure but cannot change facts
  • Personality: Senior scientific author (distinct from general synthesizer's integrative personality)
  • Integration: Called by lit-pm, not directly by users
  • Three modes: Outline, Introduction, Final Synthesis (different stages of pipeline)

平台分布

Codex

35.4%
按下载量换算40

Claude

29.84%
按下载量换算33

Cursor

19.22%
按下载量换算22

Gemini CLI

9.17%
按下载量换算10

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

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

继续浏览同类 Skills