Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Research Paper Writer

ASecurity

Write academic papers with AI assistance — outlining, drafting sections, tightening arguments, managing citations, and responding to reviewers. Use when turning research into a publishable manuscript.

2 stars
0 votes
0 copies
0 views
Added 9/29/2026
ai-agentsgo

Security Analysis

A100/100

Scanned 9/29/2026

$npx -y skills add aicodedecode/awesome-muse-skills --skill research-paper-writer --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Research Paper Writer?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Research Paper Writer
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-research-paper-writer/badge)](https://www.skillsdirectory.com/skills/aicodedecode-research-paper-writer)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: research-paper-writer
description: Write academic papers with AI assistance — outlining, drafting sections, tightening arguments, managing citations, and responding to reviewers. Use when turning research into a publishable manuscript.
category: ai-research
---

# Research Paper Writer

Writing a paper is engineering an argument: the claim, the evidence, and the story that connects 
them. AI assistance helps at every stage — but the researcher owns the argument, the evidence, 
and the honesty.

## Overview

Work section by section, not front to back. Start with the figures and results — the paper's 
skeleton. Write the methods from your lab notes while they're fresh. Draft the introduction last, 
when you know what story the results actually tell. Use AI for outlining, drafting, tightening 
prose, and checking consistency — never for inventing results, citations, or related work you 
haven't read.

## When to use

- Turning completed research into a conference or journal manuscript.
- Structuring a messy set of results into a coherent narrative.
- Revising: tightening prose, fixing flow, responding to reviewers.
- Writing related work honestly from papers you've actually read.

## Core concepts

- **Argument first**: one central claim per paper, supported by 2–4 sub-claims each tied to 
evidence. If you can't state the claim in one sentence, you're not ready to write.
- **Results-driven structure**: figures and tables first; the text explains what the reader sees. 
Write captions that stand alone.
- **Methods reproducibility**: enough detail for an expert to replicate — parameters, data 
versions, code links. Written from notes, not memory.
- **Honest related work**: cite what you read, characterize it fairly, position your contribution 
precisely. No strawmen, no citation padding.
- **Reviewer response**: address every comment — agree and change, or disagree with evidence. 
Never ignore; never be dismissive.
- **Integrity boundaries**: AI drafts prose; humans verify every claim, number, and citation. 
Fabricated references are career-ending — check each one.

## Practical workflow

1. State the one-sentence claim and list the evidence for each sub-claim. Cut results that don't 
serve the claim (save them for the next paper).
2. Build figures and tables; write standalone captions.
3. Outline section by section: the point of each paragraph in one line. Get feedback on the outline 
before drafting.
4. Draft methods from lab notes; results describing the figures; discussion interpreting honestly 
— including what didn't work.
5. Write the introduction last: the problem, why it matters, what you did, what you found — in 
that order.
6. Revise in passes: argument → structure → clarity → precision → proofread. Use AI for 
tightening, then verify every edit preserved meaning.

```text
Revision passes (one at a time):
1. ARGUMENT:  does every section serve the central claim?
2. STRUCTURE: does the order build the case logically?
3. CLARITY:   would a non-specialist follow the story?
4. PRECISION: are claims hedged correctly, numbers exact?
5. PROOFREAD: grammar, formatting, reference integrity
```

## Common pitfalls

- **Writing before the argument is clear**: drafting to discover what you think. Outline first; the 
outline is where thinking happens.
- **AI-invented citations**: models fabricate plausible references. Verify every citation exists 
and says what you claim.
- **Burying limitations**: hiding weaknesses reviewers will find anyway. State them; frame what 
they imply for future work.
- **Introduction first**: writing the intro before results are final produces fiction. Results 
first, intro last.
- **Ignoring the rebuttal**: defensive or dismissive reviewer responses. Engage each point 
substantively — reviewers are doing you a favor.
- **Salami slicing**: splitting one contribution across papers. One paper, one clear contribution, 
fully evidenced.

Attribution

aicodedecodeaicodedecode
View sourceSee grades on GitHubMore from aicodedecode →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698431 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →