Topic Synthesis Expertise
You have specialized knowledge for synthesizing content from multiple sources into coherent, expert-level knowledge bases. Your job is to perform true synthesis - not concatenation or summarization, but deep integration of concepts, patterns, and relationships across sources.
Core Mission
Transform disparate source materials into a unified knowledge base that:
- Identifies and defines core concepts clearly
- Maps relationships between concepts
- Extracts reusable patterns with context
- Documents anti-patterns and pitfalls
- Flags conflicts between sources
- Provides practical examples with citations
- Creates a coherent narrative flow
Critical: The downstream consumer is an LLM that treats skill content as authoritative instructions. True synthesis creates new understanding that the agent cannot derive on its own - connections between sources, resolved contradictions, and actionable patterns with when/why/how context. Apply the Expert Subtraction Principle throughout.
Overriding Principles
- Never fabricate domain knowledge. If sources are ambiguous or incomplete, say so explicitly. This rule overrides all others.
- Prefer precision over coverage. A focused, accurate synthesis is better than a broad, shallow one.
The Expert Subtraction Principle
Core Philosophy: Experts are systems thinkers who leverage their extensive knowledge and deep understanding to reduce complexity. Novices add. Experts subtract until nothing superfluous remains.
The principle in practice: True expertise manifests as removal, not addition. The expert's value is knowing what to leave out. A novice demonstrates knowledge by showing everything they know; an expert demonstrates understanding by showing only what matters.
When to Use
- Combining 2+ sources on a single topic
- Creating reference documentation from multiple inputs
- Building expertise skills from URLs/files
- When sources may conflict and need reconciliation
- Multi-document analysis requiring relationship mapping
Not for: Single-source summarization, copy-editing, translation
Knowledge Base Summary
- 8-phase synthesis process: Content Analysis -> Concept Extraction -> Relationship Mapping -> Pattern Extraction -> Anti-Pattern Documentation -> Conflict Detection -> Example Collection -> Narrative Construction
- Decision utility over section counts: include only the sections and entries that improve execution quality
- Explicit relationships: Use arrow notation (->) to show how concepts connect
- Conflict transparency: Always flag disagreements between sources with both perspectives
- Citation requirements: Every example, pattern, and anti-pattern must cite its source
- Source scope discipline: Cross-platform sources are contrast-only and never override primary-platform guidance
The 8-Phase Process (Summary)
- Content Analysis - Map what each source contributes
- Concept Extraction - Identify the smallest set of fundamental building blocks needed for clear decisions
- Relationship Mapping - Show dependencies, hierarchies, contrasts
- Pattern Extraction - Document reusable approaches (when/why/how)
- Anti-Pattern Documentation - What to avoid and why
- Conflict Detection - Flag and contextualize disagreements
- Example Collection - Concrete demonstrations with citations
- Narrative Construction - Build coherent flow from simple to complex
Full Methodology
See reference.md for the complete synthesis methodology including:
- Detailed phase instructions - Step-by-step guidance for each phase
- Output format template - Required structure for synthesis output
- Quality standards checklist - Self-check before completing
- Synthesis principles - Practices and common mistakes
- Good vs bad examples - Concrete comparisons
- Edge case handling - Similar sources, contradictions, sparse info, technical content
- Success criteria - How to evaluate synthesis quality
Output Structure
See the Synthesis Output Contract section in reference.md for the complete template.
Required synthesis sections: TL;DR, Decision Rules, Anti-Patterns, Quick Reference, Sources.
Conditional sections: Core Concepts, Patterns, Practical Examples, Deep Dives (include only when they add unique value).
Common Mistakes
- Concatenation disguised as synthesis - Just putting sources in sequence with headers
- Missing citations - Every pattern/example needs a source reference
- Hidden conflicts - Silently picking one source over another without flagging disagreement
- Abstract patterns - Patterns without when/why/how aren't actionable
- Assuming knowledge - Definitions must stand alone, not assume reader context
- Section quota chasing - Inflating section counts instead of improving decision quality
See Examples of Good vs Bad Synthesis in reference.md for concrete comparisons.