Related Work Writing Skill for Claude
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.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/lingzhi227/agent-research-skills --skill related-work-writingThe instruction itself
10 sections, as written by the authorRelated 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:
- Topic sentence — Introduce the research direction
- Describe key works — Summarize 2-5 representative papers
- Compare and contrast — How does each approach differ from yours?
- 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.bibfile - 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-review, citation-management
- Downstream: paper-writing-section
- See also: survey-generation
Other skills for the same job
different authors, same section of the catalogue
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementing any feature or bugfix, before writing implementation code
Use when you have a spec or requirements for a multi-step task, before touching code
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
| Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
Official Opentrons Protocol API for OT-2 and Flex robots. Use when writing protocols specifically for Opentrons hardware with full access to Protocol API v2 features. Best for production Opentrons protocols, official API compatibility. For multi-vendor automation or broader equipment control use pylabrobot.
How to use it
Take lingzhi227/related-work-writing from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.