research-paper-writing
Skill13 starsChanged 33 days agoMITView on GitHub
Improve academic paper writing quality for ML/CV/NLP-style papers with clear section structure, paragraph flow, and reviewer-facing presentation. Use when drafting or revising Abstract, Introduction, Related Work, Method, Experiments, or Conclusion; polishing figures/tables; checking claim-support alignment; or performing self-review before submission.
29 other projects use a version of this, 9 of them edited.
Adopted by
Most recently taken up by
- 2743959925-netizen/claude-skillstheir own version, first seen Nov 16, 2026
- DragonGong/skillsedited, first seen Nov 16, 2026
- ashleysbrain/skillstheir own version, first seen Nov 8, 2026
- delorenj/skillstheir own version, first seen Nov 7, 2026
- ethosagent/ethostheir own version, first seen Nov 3, 2026
- Gavin-Tao/claude-skillsedited, first seen Nov 2, 2026
Used with
Projects with it also use frontend-design, skill-creator and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
BlockSkillfrontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
Also in 6 projects that use this
SentrySkillskill-creator
Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.
Also in 4 projects that use this
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 3 projects that use this
Other versions29 projects use a version of this.
Word for word · 0
None found.
Edited · 9
- Master-cai/Research-Paper-Writing-Skills★ 6.5k99% same
- sii-research/SocioVerse2★ 1493% same
- ZeyuLing/research_autocode_skills★ 999% same
- tuoxie2046/claude-code-research-skills★ 599% same
- arnabdeypolimi/claude_code_setup★ 499% same
- Gavin-Tao/claude-skills★ 399% same
- DragonGong/skills★ 199% same
- talhaMah56/claude_skills★ 099% same
- yunyancuo/keresearch★ 099% same
Wrote their own version · 20
- Tommy-yw/RunbookHermes★ 546same name
- RedWoodOG/Hermes-Desktop★ 177same name
- pcdp577/evidence-grounded-manuscript-skills★ 53same name
- ethosagent/ethos★ 23same name
- delorenj/skills★ 17same name
- Samin12/skills★ 8same name
- yuiseki/GeoAI-master-skills★ 3same name
- 0mlkrizzz655335v/claude-skills-zh★ 2same name
- john-data-chen/hermes-agent-backup★ 2same name
- tunnckoCore/skills★ 2same name
10 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-resource-disciplineSkill
- human-facing-doc-authoringSkill
- literature-surveySkill
- project-onboardingSkill
- research-slides-authoringSkill
- research-software-engineeringSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
28 rules. 0 are common, 23 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 27 edited versions we read keep these.
23
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Use this skill to rewrite a research paper into a reviewer-friendly, high-clarity draft.
- Very specific: line 20
Use section-specific guidance in references/.
- Distinctive: line 22
Run reverse outlining after writing each section.
- Distinctive: line 23
Check every major claim in Abstract/Introduction against experimental evidence.
- Very specific: line 24
Run final-paper adversarial review with references/paper-review.md.
- Distinctive: line 28
Keep one paragraph for one message only.
- Distinctive: line 33
Treat visual quality as core content, not decoration.
- Distinctive: line 34
Use a clean teaser and pipeline figure.
- Distinctive: line 35
Use readable, minimal-ink tables.
- Distinctive: line 36
Keep formatting consistent and tidy.
- Distinctive: line 40
Use this quick test whenever the user asks whether a paragraph "flows" or is clear.
- Distinctive: line 42
Read as an external reader:
- Distinctive: line 47
Run reverse outlining for the current section:
- Distinctive: line 48
Write down thesis/main claim.
- Distinctive: line 49
Write down each paragraph topic sentence.
- Distinctive: line 50
Write down the evidence/explanation points under each paragraph.
- Distinctive: line 51
Check mapping: topic sentence -> thesis, and evidence -> topic sentence.
- Distinctive: line 53
If flow is still weak, add temporary section headers and explicit transition phrases during revision, then remove unnecessary headers …
- Very specific: line 75
Use references/paper-review.md for the full checklist and workflow.
- Distinctive: line 77
Add an end-of-draft self-review question list in five dimensions:
- Distinctive: line 83
Treat claim-evidence alignment as a hard constraint, especially for Abstract and Introduction.
- Distinctive: line 91
Avoid writing style that looks like incremental patching of a naive baseline.
- Distinctive: line 92
Keep terminology stable across the full paper.
- Distinctive: line 93
If a claim cannot be supported by results, weaken or remove the claim.
- Distinctive: line 94
Before finalizing, append and answer a five-dimension self-review question list, then revise the paper based on unresolved items.
- Very specific: line 95
Do not load all section references (Introduction/Abstract/Related Work/Method/Experiments/Conclusion) at once.
- Distinctive: line 99
When asked to rewrite or draft sections, return:
- Distinctive: line 163
When upstream evolves the references files, we may selectively cherry-pick changes (per ATTRIBUTION.md "Pulling updates from upstream").
“Common” is measured: kept by at least 6 in 10 of the 27 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Research Paper Writing
Overview
Use this skill to rewrite a research paper into a reviewer-friendly, high-clarity draft. Prioritize first-impression quality (figures/tables/layout), logical flow, and evidence-backed claims.
Core Workflow
- Clarify the paper story before sentence-level edits.
- Use section-specific guidance in
references/. - Rewrite paragraph-by-paragraph with one message per paragraph.
- Run reverse outlining after writing each section.
- Check every major claim in Abstract/Introduction against experimental evidence.
- Run final-paper adversarial review with
references/paper-review.md.
Global Principles
- Keep one paragraph for one message only.
- State the paragraph message in the first sentence.
- Make nouns self-contained; define new terms before reusing them.
- Maintain sentence-to-sentence flow (cause, contrast, consequence, or refinement).
- Iterate with adversarial self-review: read as a skeptical reviewer.
- Treat visual quality as core content, not decoration.
- Use a clean teaser and pipeline figure.
- Use readable, minimal-ink tables.
- Keep formatting consistent and tidy.
Paragraph Clarity Check (Important)
Use this quick test whenever the user asks whether a paragraph "flows" or is clear.
- Read as an external reader:
- Does this paragraph have one explicit message?
- Does the first sentence state what this paragraph will do?
- Are all key nouns/terms readable without hidden context?
- Does each sentence connect to the previous one with a clear relation (cause, contrast, consequence, refinement, example)?
- Run reverse outlining for the current section:
- Write down thesis/main claim.
- Write down each paragraph topic sentence.
- Write down the evidence/explanation points under each paragraph.
- Check mapping: topic sentence -> thesis, and evidence -> topic sentence.
- Revise or remove any paragraph that cannot be mapped cleanly.
- If flow is still weak, add temporary section headers and explicit transition phrases during revision, then remove unnecessary headers before finalizing.
Source reference for this check:
references/does-my-writing-flow-source.md
Section Guides
Load only the needed section file:
- Introduction:
references/introduction.md - Abstract:
references/abstract.md - Related Work:
references/related-work.md - Method:
references/method.md - Experiments:
references/experiments.md - Conclusion:
references/conclusion.md - Paper review (Paper Review):
references/paper-review.md - Paragraph clarity source:
references/does-my-writing-flow-source.md - Example bank index:
references/examples/index.md
Paper Review Core Points
Use references/paper-review.md for the full checklist and workflow.
- Add an end-of-draft self-review question list in five dimensions:
- contribution,
- writing clarity,
- experimental strength,
- evaluation completeness,
- method design soundness.
- Treat claim-evidence alignment as a hard constraint, especially for Abstract and Introduction.
- Perform adversarial writing: review as a skeptical reviewer and resolve every high-risk question.
- Revise until major rejection risks are explicitly addressed.
Execution Rules
- Build a mini-outline before drafting prose.
- For each subsection, explicitly include motivation, design, and technical advantage when applicable.
- Avoid writing style that looks like incremental patching of a naive baseline.
- Keep terminology stable across the full paper.
- If a claim cannot be supported by results, weaken or remove the claim.
- Before finalizing, append and answer a five-dimension self-review question list, then revise the paper based on unresolved items.
- Do not load all section references (Introduction/Abstract/Related Work/Method/Experiments/Conclusion) at once; load only the specific section guide needed for the current edit target.
Output Contract
When asked to rewrite or draft sections, return:
- A compact section outline (3-7 bullets).
- Revised paragraphs with explicit paragraph roles (opening/challenge/method/advantage/evidence/limitation).
- A short self-review checklist covering clarity, flow, terminology consistency, unsupported claims, and missing evidence.
- A claim-evidence map for each major claim in the revised text using
Claim: ... | Evidence: ... | Status: supported/needs evidence.
Adjacent human-facing documents
This skill governs the published paper draft itself (Abstract, Introduction, Related Work, Method, Experiments, Conclusion). When the work also requires producing or revising meta-documents that support the paper -- for example:
- updates to the project's
PLAN.md, - per-section research notes (
notes/section_<N>.md), - per-component implementation plans (
notes/impl_<component>.md), - the project's
README.md, - a reviewer-response draft,
those documents have a different audience (the user, co-authors,
reviewers) and a different style budget than the paper itself. Load
~/.scicomp-research-skills/skills/human-facing-doc-authoring/SKILL.md
for the conventions and per-doc-type structural skeletons. Use BOTH
skills together: paper-writing for the paper draft, human-facing for
any meta-doc.
Resource discipline for paper-writing sessions
A paper-writing session typically iterates across multiple sections,
re-reads many survey notes, may re-grep the paper draft repeatedly,
and often spans multiple sessions before a section is finalised.
Whenever the session is going to be heavy (more than ~5 file reads,
multiple section drafts, or a span across multiple sittings), load
~/.scicomp-research-skills/skills/agent-resource-discipline/SKILL.md
at session start. In particular:
agent-resource-discipline/references/persistent-memory.md-- the first-/last-action protocol that updatesnotes/section_<N>.mdandPLAN.mdstatus fields so the next session resumes cheaply.agent-resource-discipline/references/context-window-budget.md-- the rule that this skill's Execution Rule #7 ("do not load all section references at once") generalises to: do not load all survey notes at once, do not load the full.txtextraction of every cited paper -- target-grep instead.
Both skills compose: paper-writing for what to write; agent-resource- discipline for what to load while writing.
Note on this skill's references/ files
The references files under references/ (abstract.md, conclusion.md,
experiments.md, introduction.md, method.md, paper-review.md,
related-work.md, examples/) are vendored from the upstream
Master-cai/Research-Paper-Writing-Skills
repository at commit 9ee5edd (see ATTRIBUTION.md). They are
deliberately preserved without per-file date-stamp footers -- our
universal "every plan-of-record-style document ends with a date-stamp
footer" convention (root AGENTS.md Section 6) does not apply to
upstream-imported reference content; modifying the upstream files to
add footers would create false revision history.
When upstream evolves the references files, we may selectively
cherry-pick changes (per ATTRIBUTION.md "Pulling updates from
upstream"). When we substantially modify a reference file, we will
add a *Revised YYYY-MM-DD by A. Attia: <note>.* footer to that
specific file at that point. Until then the upstream provenance is
authoritative.
Revised 2026-05-13: added "Adjacent human-facing documents" section pointing at the human-facing-doc-authoring skill for meta-docs (PLAN.md, section/impl notes, README, rebuttal) that this skill does not directly govern. Revised 2026-05-13: added "Resource discipline for paper-writing sessions" section pointing at the agent-resource-discipline skill for the cross-cutting context-window / persistent-memory protocol that complements this skill's Execution Rule #7. Revised 2026-05-14 (post-fresh-audit): documented the deliberate exception from the universal date-stamp-footer convention for upstream-vendored references files (the eight files under references/ that were imported from Master-cai upstream and have not been substantially modified).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

