lit-synthesis
Deep reading and synthesis of literature corpus. Theoretical mapping, thematic clustering, and debate identification using Zotero MCP for full-text access.
What this skill does
# Literature Synthesis You help sociologists move from a corpus of papers to a deep understanding of a field. This is the analytical bridge between finding papers (lit-search) and writing about them (lit-writeup). ## The Lit Trilogy This skill is the middle step in a three-skill workflow: | Skill | Role | Key Output | |-------|------|------------| | **lit-search** | Find papers via OpenAlex | `database.json`, download checklist | | **lit-synthesis** | Analyze & organize via Zotero | `field-synthesis.md`, `theoretical-map.md`, `debate-map.md` | | **lit-writeup** | Draft prose | Publication-ready Theory section | **Input**: Papers in Zotero (imported from lit-search or user's existing library) **Output**: Organized understanding of the field ready for writing ## When to Use This Skill Use this skill when users: - Have a corpus of papers (from lit-search or their own collection) - Need to understand the theoretical landscape before writing - Want to identify debates, tensions, and competing positions - Need to organize papers thematically or by theoretical tradition - Want deep reading notes, not just metadata extraction ## Core Principles 1. **Read deeply, not widely**: Better to understand 15 papers thoroughly than 50 superficially. 2. **Theoretical traditions matter**: Papers exist within intellectual lineages. Map who cites whom and why. 3. **Debates are gold**: Competing positions create space for contributions. Find the tensions. 4. **Organization serves writing**: The clusters and maps you create should directly feed lit-writeup's architecture phase. 5. **Full text when possible**: Abstracts tell you *what*; full text tells you *how* and *why*. ## Zotero MCP Integration This skill uses **Zotero MCP** for accessing your library: ### Setup Install the Zotero MCP server: ```bash uv tool install "git+https://github.com/54yyyu/zotero-mcp.git" zotero-mcp setup ``` See `mcp/zotero-setup.md` for detailed configuration. ### Key Capabilities | Tool | Purpose | |------|---------| | `zotero_search_items` | Find papers by keyword, author, tag | | `zotero_semantic_search` | Conceptual similarity search | | `zotero_get_item_metadata` | Retrieve full metadata + BibTeX | | `zotero_get_annotations` | Extract PDF highlights and notes | | `zotero_search_notes` | Search your reading notes | ### Workflow Integration 1. **From lit-search**: Import the BibTeX export into Zotero 2. **Acquire PDFs**: Use Zotero's "Find Available PDF" or manual download 3. **Read and annotate**: Highlight key passages, add notes 4. **lit-synthesis reads**: Access annotations via MCP for analysis ## Workflow Phases ### Phase 0: Corpus Audit **Goal**: Assess what's in the corpus and identify gaps. **Process**: - Review the database from lit-search (or user's Zotero collection) - Count papers by year, journal, author, theoretical tradition - Identify potential gaps in coverage - Prioritize which papers need deep reading vs. skimming **Output**: `corpus-audit.md` with statistics and reading priorities. > **Pause**: User confirms corpus coverage and reading priorities. --- ### Phase 1: Deep Reading **Goal**: Close read priority papers and extract analytical insights. **Process**: - For each priority paper, read full text via Zotero MCP - Extract: argument structure, theoretical framework, key concepts, methodological approach - Note: how theory is deployed, what evidence supports claims, limitations acknowledged - Create structured reading notes **Output**: `reading-notes/` directory with per-paper notes. > **Pause**: User reviews reading notes for key papers. --- ### Phase 2: Theoretical Mapping **Goal**: Identify intellectual traditions and lineages. **Process**: - Identify which theoretical frameworks appear across papers - Map citation relationships (who cites whom) - Note foundational texts and their descendants - Identify "camps" or schools of thought - Document key concepts and how they're used **Output**: `theoretical-map.md` with traditions, key theorists, and concept definitions. > **Pause**: User reviews theoretical landscape. --- ### Phase 3: Thematic Clustering **Goal**: Organize papers by what they study and how. **Process**: - Group papers by empirical focus (population, setting, phenomenon) - Group papers by theoretical approach - Group papers by methodological strategy - Identify papers that bridge multiple clusters - Note within-cluster consensus and variation **Output**: `thematic-clusters.md` with organized paper groupings. > **Pause**: User reviews clustering logic. --- ### Phase 4: Debate Mapping **Goal**: Identify tensions, disagreements, and competing positions. **Process**: - Find explicit disagreements (papers that critique each other) - Find implicit tensions (contradictory findings or incompatible assumptions) - Identify unresolved questions the field is grappling with - Note where evidence is mixed or contested - Document the "state of the debate" for each tension **Output**: `debate-map.md` with positions, evidence, and unresolved questions. > **Pause**: User reviews debates and selects focus areas. --- ### Phase 5: Field Synthesis **Goal**: Create comprehensive understanding ready for writing. **Process**: - Synthesize across phases into coherent field understanding - Identify the most productive gaps for contribution - Recommend which lit-writeup cluster (Gap-Filler, Theory-Extender, etc.) fits - Create the handoff document for lit-writeup **Output**: `field-synthesis.md` with integrated understanding and writing recommendations. --- ## Output Files ``` lit-synthesis/ ├── corpus-audit.md # Phase 0: What's in the corpus ├── reading-notes/ # Phase 1: Per-paper notes │ ├── author2020-title.md │ ├── author2019-title.md │ └── ... ├── theoretical-map.md # Phase 2: Traditions and lineages ├── thematic-clusters.md # Phase 3: Paper groupings ├── debate-map.md # Phase 4: Tensions and positions └── field-synthesis.md # Phase 5: Integrated understanding ``` ## Reading Note Template For each paper in Phase 1: ```markdown # [Author Year] - [Short Title] ## Bibliographic Info - Full citation: [from Zotero] - DOI: [link] ## Core Argument [1-2 sentences: What is the paper arguing?] ## Theoretical Framework - Tradition: [e.g., Bourdieusian, institutionalist, interactionist] - Key concepts used: [list] - How theory is deployed: [description vs. extension vs. critique] ## Empirical Strategy - Data: [what kind] - Methods: [how analyzed] - Sample: [who/what] ## Key Findings 1. [Finding 1] 2. [Finding 2] 3. [Finding 3] ## Contribution Claim [What does the paper claim to contribute?] ## Limitations (as noted by authors) - [Limitation 1] - [Limitation 2] ## My Notes [Your analytical observations, connections to other papers, questions raised] ## Key Quotes > "[Quote 1]" (p. X) > "[Quote 2]" (p. Y) ## Tags [theoretical-tradition] [empirical-focus] [method] [relevant-to-my-project] ``` ## Model Recommendations | Phase | Model | Rationale | |-------|-------|-----------| | **Phase 0**: Corpus Audit | **Sonnet** | Data processing, statistics | | **Phase 1**: Deep Reading | **Opus** | Analytical reading, synthesis | | **Phase 2**: Theoretical Mapping | **Opus** | Pattern recognition, intellectual history | | **Phase 3**: Thematic Clustering | **Sonnet** | Organization, categorization | | **Phase 4**: Debate Mapping | **Opus** | Tension identification, nuance | | **Phase 5**: Field Synthesis | **Opus** | Integration, strategic judgment | ## Starting the Synthesis When the user is ready to begin: 1. **Check Zotero setup**: > "Do you have Zotero MCP configured? If not, let's set that up first (see `mcp/zotero-setup.md`)."
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.