/related-work-writing
Write Related Work sections that compare and contrast prior work with your approach. Organize by theme, cite broadly, and explain how your work differs. Use when writing or improving the Related Work section of a paper.
$ npx -y skills add lingzhi227/agent-research-skills --skill related-work-writing --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/related-work-writing
Context preview
The summary Claude sees to decide when to auto-load this skill.
Write Related Work sections that compare and contrast prior work with your approach. Organize by theme, cite broadly, and explain how your work differs. Use when writing or improving the Related Work section of a paper.
SKILL.md
related-work-writing.SKILL.mdname: related-work-writing
description: Write Related Work sections that compare and contrast prior work with your approach. Organize by theme, cite broadly, and explain how your work differs. Use when writing or improving the Related Work section of a paper.
argument-hint: [paper-draft]
Related Work Writing
Generate publication-quality Related Work sections with proper citations and thematic organization.
Input
- `$0` — Current paper draft or method description
- `$1` — Collected literature (BibTeX entries, paper summaries, or literature review notes)
References
- Related work writing prompts and strategies: `~/.claude/skills/related-work-writing/references/related-work-prompts.md`
Workflow
Step 1: Analyze the Paper's Contributions
- Read the current paper draft (especially Methods and Introduction)
- Identify the key contributions and novelty claims
- List the technical components that need literature context
Step 2: Organize Literature by Theme
Group related papers into thematic clusters:
- Each cluster should represent a research direction or technique
- Common themes: problem formulation, methodology family, application domain, evaluation approach
- Order themes from most to least relevant to your work
Step 3: Write Each Theme Paragraph
For each thematic group: 1. **Topic sentence** — Introduce the research direction 2. **Describe key works** — Summarize 2-5 representative papers 3. **Compare and contrast** — How does each approach differ from yours? 4. **Transition** — Connect to the next theme or to your contribution
Step 4: Refine
- Ensure every cited paper has a clear reason for inclusion
- Check that your work's novelty is clear from the comparisons
- Verify all `\cite{}` keys exist in the `.bib` file
- Aim for 1-2 pages (single column) or 0.5-1 page (double column)
Rules
- **Compare and contrast, don't just describe** — "Unlike [X] which assumes..., our method..."
- **Organize by theme, not chronologically** — Group by research direction
- **Cite broadly** — Not just the most popular papers; include recent and diverse work
- **Be fair** — Acknowledge strengths of prior work before stating limitations
- **Explain inapplicability** — If a method could apply to your setting, explain why you don't compare experimentally, or add it to experiments
- **Use present tense for established facts** — "Smith et al. propose..." or "This approach uses..."
- **End with positioning** — The final paragraph should clearly position your work relative to all discussed prior work
Related Skills
- Upstream: [literature-search](../literature-search/), [literature-review](../literature-review/), [citation-management](../citation-management/)
- Downstream: [paper-writing-section](../paper-writing-section/)
- See also: [survey-generation](../survey-generation/)
Read more
name: related-work-writing description: Write Related Work sections that compare and contrast prior work with your approach. Organize by theme, cite broadly, and explain how your work differs. Use when writing or improving the Related Work section of a paper. argument-hint: [paper-draft]
Related Work Writing
Generate publication-quality Related Work sections with proper citations and thematic organization.
Input
- `$0` — Current paper draft or method description
- `$1` — Collected literature (BibTeX entries, paper summaries, or literature review notes)
References
- Related work writing prompts and strategies: `~/.claude/skills/related-work-writing/references/related-work-prompts.md`
Workflow
Step 1: Analyze the Paper's Contributions
- Read the current paper draft (especially Methods and Introduction)
- Identify the key contributions and novelty claims
- List the technical components that need literature context
Step 2: Organize Literature by Theme
Group related papers into thematic clusters:
- Each cluster should represent a research direction or technique
- Common themes: problem formulation, methodology family, application domain, evaluation approach
- Order themes from most to least relevant to your work
Step 3: Write Each Theme Paragraph
For each thematic group: 1. **Topic sentence** — Introduce the research direction 2. **Describe key works** — Summarize 2-5 representative papers 3. **Compare and contrast** — How does each approach differ from yours? 4. **Transition** — Connect to the next theme or to your contribution
Step 4: Refine
- Ensure every cited paper has a clear reason for inclusion
- Check that your work's novelty is clear from the comparisons
- Verify all `\cite{}` keys exist in the `.bib` file
- Aim for 1-2 pages (single column) or 0.5-1 page (double column)
Rules
- **Compare and contrast, don't just describe** — "Unlike [X] which assumes..., our method..."
- **Organize by theme, not chronologically** — Group by research direction
- **Cite broadly** — Not just the most popular papers; include recent and diverse work
- **Be fair** — Acknowledge strengths of prior work before stating limitations
- **Explain inapplicability** — If a method could apply to your setting, explain why you don't compare experimentally, or add it to experiments
- **Use present tense for established facts** — "Smith et al. propose..." or "This approach uses..."
- **End with positioning** — The final paragraph should clearly position your work relative to all discussed prior work
Related Skills
- Upstream: [literature-search](../literature-search/), [literature-review](../literature-review/), [citation-management](../citation-management/)
- Downstream: [paper-writing-section](../paper-writing-section/)
- See also: [survey-generation](../survey-generation/)
31 skills for Claude Code covering the full academic research paper lifecycle — from literature search to slide generation — plus GitHub repository analysis for research topics. Extracted from 17 GitHub repos studying LLM-agent-driven research automation.
Other skills on agent-research-skills.
- /algorithm-design
Design algorithms with LaTeX pseudocode and UML diagrams. Generate algorithmic environments, Mermaid class/sequence diagrams, and ensure consistency between pseudocode and implementation. Use when formalizing methods for a paper.
Open skill - /atomic-decomposition
Decompose research ideas into atomic, self-contained concepts with bidirectional math-code mapping. For each concept, extract the math formula from papers and find code implementations. Use for complex system papers requiring formal grounding.
Open skill - /backward-traceability
Make every number in the final PDF traceable to the exact code line that produced it. Uses \hypertarget/\hyperlink LaTeX commands and \num{formula} evaluated at compile time. Use for reproducibility and data integrity verification.
Open skill - /citation-management
Manage BibTeX citations for LaTeX papers. Harvest missing citations from a draft using Semantic Scholar, validate cite keys against .bib files, deduplicate entries, and format bibliography. Use when working with references, BibTeX, or citations.
Open skill - /code-debugging
Debug experiment code with structured error analysis. Categorize errors, apply targeted fixes with retry logic, and use reflection to prevent recurring issues. Use when experiment code fails or produces incorrect results.
Open skill - /data-analysis
Generate statistical analysis code with 4-round review. Select appropriate statistical tests, interpret results, and produce analysis reports with p-values, effect sizes, and confidence intervals. Use when analyzing experimental data for a paper.
Open skill

