Synthesis and Analogy
Synthesizes information from multiple sources into coherent insights and applies analogical reasoning to transfer knowledge across domains. Use when conducting literature reviews, integrating stakeholder feedback, reconciling conflicting viewpoints, identifying cross-source patterns, creating explanatory analogies ("X is like Y"), finding creative solutions through cross-domain transfer, or testing whether analogies hold (surface vs deep). Use when user mentions "synthesize", "combine sources", "analogy", "similar to", "transfer from", "integrate findings".
Install
/plugin marketplace add lyndonkl/claudeThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add lyndonkl/claude --skill synthesis-and-analogygit clone --depth 1 https://github.com/lyndonkl/claude.git /tmp/claude
mkdir -p ~/.claude/skills
cp -r /tmp/claude/skills/synthesis-and-analogy ~/.claude/skills/synthesis-and-analogyPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Synthesis & Analogy ## Table of Contents - [Workflow](#workflow) - [Synthesis Techniques](#synthesis-techniques) - [Analogy Techniques](#analogy-techniques) - [Common Patterns](#common-patterns) - [Guardrails](#guardrails) - [Quick Reference](#quick-reference) ## Workflow Copy this checklist and track your progress: ``` Synthesis & Analogy Progress: - [ ] Step 1: Clarify goal and gather sources/domains - [ ] Step 2: Choose approach (synthesis, analogy, or both) - [ ] Step 3: Apply synthesis or analogy techniques - [ ] Step 4: Test quality and validity - [ ] Step 5: Refine and deliver insights ``` **Step 1: Clarify goal** For synthesis: What sources? What question are we answering? What conflicts need resolving? For analogy: What's source domain (familiar)? What's target domain (explaining)? What's goal (explain, solve, ideate)? See [Common Patterns](#common-patterns) for typical goals. **Step 2: Choose approach** Synthesis only → Use [Synthesis Techniques](#synthesis-techniques). Analogy only → Use [Analogy Techniques](#analogy-techniques). Both → Start with synthesis to find patterns, then use analogy to explain or transfer. For straightforward cases → Use [resources/template.md](resources/template.md). For complex multi-domain synthesis → Study [resources/methodology.md](resources/methodology.md). **Step 3: Apply techniques**
Details
- Skill name
synthesis-and-analogy- Repository
- lyndonkl/claude
- Path
skills/synthesis-and-analogy/SKILL.md- Repo updated
- 1 September 2026
FAQ
What does the Synthesis and Analogy skill do?
Synthesizes information from multiple sources into coherent insights and applies analogical reasoning to transfer knowledge across domains. Use when conducting literature reviews, integrating stakeholder feedback, reconciling conflicting viewpoints, identifying cross-source patterns, creating explanatory analogies ("X is like Y"), finding creative solutions through cross-domain transfer, or testing whether analogies hold (surface vs deep). Use when user mentions "synthesize", "combine sources", "analogy", "similar to", "transfer from", "integrate findings".
How do I install the Synthesis and Analogy skill?
Claude Code plugin: /plugin marketplace add lyndonkl/claude. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Synthesis and Analogy popular?
It lives in lyndonkl/claude, which has 200 GitHub stars and 25 forks.
Related skills
Abstraction Concrete Examples
200lyndonkl/claude
Builds structured abstraction ladders that translate high-level principles into concrete, actionable examples across 3-5 levels. Bridges communication gaps, reveals hidden assumptions, and tests whether abstract ideas work in practice. Use when explaining concepts at different expertise levels, moving between abstract principles and concrete implementation, identifying edge cases by testing ideas against scenarios, designing layered documentation, decomposing complex problems into actionable steps, or bridging strategy-execution gaps.
Academic Letter Architect
200lyndonkl/claude
Guides the creation of evidence-based academic recommendation letters, reference letters, and award nominations that combine concrete examples, meaningful comparisons, and genuine enthusiasm. Use when writing recommendation letters for students, postdocs, or colleagues, or when user mentions recommendation letter, reference, nomination, letter of support, endorsement, or needs help with strong advocacy and comparative statements.
Adr Architecture
200lyndonkl/claude
Documents significant architectural and technical decisions with full context, alternatives considered, trade-offs analyzed, and consequences understood. Creates a decision trail that helps teams understand why decisions were made. Use when choosing between technology options, making infrastructure decisions, establishing standards, migrating systems, or when user mentions ADR, architecture decision, technical decision record, or decision documentation.
Systemic Protagonist
200lyndonkl/claude
Renders a market, protocol, institution, codebase, supply chain, disease, or ecosystem as a legible protagonist without faking agency. Builds the POSIWID character sheet (revealed objective function vs. stated purpose), the agency ledger of verb repairs, the gateway-proxy admission test, the traveling-object device, the instrumented threshold scene, and climax by constraint violation. Use when the subject of a piece is a system rather than a person, when a draft says "the market decided" or "the industry learned", when analysis reads as a data dump with no protagonist, or when user mentions sy
Symmetry Validation Suite
200lyndonkl/claude
Provides empirical test protocols and metrics to validate whether hypothesized symmetries actually hold in data or models before committing to equivariant architecture. Includes invariance/equivariance testing, group structure verification, and distribution analysis under transforms. Use when testing invariance, validating equivariance, checking symmetry assumptions, debugging symmetry-related model failures, or needing data-driven validation before architecture decisions.
TDD
100adriannoes/awesome-agentic-ai
Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.