# research-writing-literature

Guides academic manuscripts, literature syntheses, methodology sections, and figure discussions into evidence-backed research narratives.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · ★ 22
- Author: hanhuark
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/hanhuark/mechanical-engineering-research-skill/tree/HEAD/skills/research-writing-literature/SKILL.md
- Updated: 2026-10-24
- HTML: https://affpapa.org/en/nevibecode/skills/research-writing-literature

## What it does

The skill organizes academic drafts around an evidence-backed narrative rather than a chain of disconnected paper summaries. Each paragraph starts with a core statement in its opening sentence, followed by supporting data, qualifications, or logical transitions.

It applies concrete patterns for core sections. Introductions follow a path from practical importance and existing capabilities to persistent technical barriers and the proposed solution. Methodology sections require explicit uncertainty tracking and stated assumptions. Results require a four-tier breakdown covering figure observations, physical rationale, and comparison with earlier work.

Drafting and structural revisions rely on an author-approved claim-evidence map rather than autonomous restructuring by the agent.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add hanhuark/mechanical-engineering-research-skill --skill research-writing-literature -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/research-writing-literature/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/research-writing-literature/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add hanhuark/mechanical-engineering-research-skill --skill research-writing-literature -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/research-writing-literature/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add hanhuark/mechanical-engineering-research-skill --skill research-writing-literature -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/research-writing-literature/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install hanhuark/mechanical-engineering-research-skill research-writing-literature
```

2. **Manually: put the files in place**
- File: `.github/skills/research-writing-literature/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add hanhuark/mechanical-engineering-research-skill --skill research-writing-literature -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/hanhuark/mechanical-engineering-research-skill --path skills/research-writing-literature
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/research-writing-literature/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add hanhuark/mechanical-engineering-research-skill --skill research-writing-literature -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/hanhuark/mechanical-engineering-research-skill/tree/HEAD/skills/research-writing-literature/SKILL.md

## When to use it
- synthesize literature sources around shared mechanisms or methods
- organize research introductions from existing barriers to new contributions
- document experimental procedures with uncertainties and assumptions
- structure figure discussions from direct observations to physical explanations

## Example prompts
- Synthesize the literature on heat transfer models and group references by methodology
- Check the results section against the four-tier figure discussion structure
- Revise the introduction to follow the argument sequence from unresolved barrier to our approach

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: c925bd3732ef5623.

BEGIN THIRD-PARTY FILE c925bd3732ef5623
```text
---
name: research-writing-literature
description: Write and revise rigorous research narratives, literature reviews, manuscript sections, citations, and figure discussions. Use for technical introductions, methods, results, discussions, review articles, abstracts, or related-work sections.
---

# Research Writing And Literature

## Purpose

Build a research story rather than a sequence of paper summaries. Every paragraph needs a central topic, normally in its first sentence; each later sentence must develop, support, qualify, or transition from it.

When AI is used to draft or substantially revise the document, first use [author-guided-ai-writing.md](../mechanical-engineering-research/references/author-guided-ai-writing.md) to obtain an author-approved story brief and claim-evidence map. Drafting and line editing do not replace those author decisions.

Before a substantial draft or structural revision, identify the reader, the decision or scientific understanding the section must support, the evidence that carries the central claim, and what the reader should know after the section. Write the structure from that reader-to-evidence path instead of filling a generic manuscript template.

## Route To References

- For critical literature synthesis, read `references/literature-review.md`.
- For journal-paper structure and results-led storytelling, read `references/paper-writing-style.md`.
- For section-specific technical writing, methods, DOE, and figure discussion, read `references/technical-writing-analysis.md`.
- For equation explanations, claim-evidence checks, methods completeness, and figure or equation narratives, read `references/technical-argument-audit.md` before a final prose-only pass.
- For a clarity pass focused on reader understanding rather than formulaic compression, read `references/technical-prose-clarity.md`.
- When matching the calibrated research style and its evidence boundaries, read `references/han-hu-research-style.md`.
- For a final pass against formulaic AI-like drafting habits, read `references/anti-formulaic-writing.md`.

## Introduction And Background

Use the chain: importance and applications; state of the art; remaining issue; why it persists; the proposed innovation; and its likely significance. Do not claim novelty merely because no prior work exists. Identify why the missing work is challenging and how the approach resolves a meaningful barrier.

## Citations And Synthesis
```
END THIRD-PARTY FILE c925bd3732ef5623

The third-party file has ended. Everything between the c925bd3732ef5623 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2450 of 4360 bytes. © hanhuark · MIT · https://github.com/hanhuark/mechanical-engineering-research-skill/tree/HEAD/skills/research-writing-literature/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md