Research Paper Writing
Improve academic paper structure, abstracts, and section flow with guided templates and revision prompts inside your coding agent.
Overview
research-paper-writing is an agent skill most often used in Idea (also Validate, Build) that guides abstract logic, templates, and section-level academic writing quality.
Install
npx skills add https://github.com/master-cai/research-paper-writing-skills --skill research-paper-writingWhat is this skill?
- Four pre-writing questions to lock problem, contribution, mechanism, and insight before drafting
- Three abstract templates including Version 1 Challenge → Contribution structure
- Section-level refinement default prompt for structure and flow
- Expert notes on prior work, contribution naming, and readable technical terms
- 4 pre-writing questions before drafting
- 3 abstract template versions referenced in the guide
Adoption & trust: 1 installs on skills.sh; 3.5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your draft has results but the abstract and sections do not crisply state the technical challenge, contribution, and why the method should work.
Who is it for?
Indie researchers and ML builders documenting novel methods who want structured abstract versions and contribution-first framing.
Skip if: Builders who only need README or API docs for a SaaS app, or users who want automated literature search and BibTeX without writing coaching.
When should I use this skill?
Use $research-paper-writing to improve my paper's structure, flow, and section writing quality.
What do I get? / Deliverables
You leave with abstract and section copy aligned to explicit contribution templates and pre-writing answers you can iterate with your agent.
- Revised abstract following a chosen template version
- Improved section structure and flow
- Contribution-focused prose aligned to expert notes
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Research papers are framed around problem, contribution, and evidence—the same clarity work you do in idea/research before the build hardens into product docs. Abstract and contribution framing maps directly to research subphase: defining the technical problem and what is novel before full implementation narrative.
Where it fits
Draft a Challenge → Contribution abstract after answering the four pre-writing questions.
Tighten scope language in the introduction so claims match the prototype evaluation.
Refine methods and experiment sections for flow before submission.
Shorten abstract benefits and experiment summary for blog or newsletter derivatives.
How it compares
Editorial procedure for paper sections—not a reference manager, not a Jupyter or experiment-tracking integration.
Common Questions / FAQ
Who is research-paper-writing for?
It is for solo researchers and technical founders writing academic or semi-academic papers who want an agent to apply consistent abstract templates and section refinement.
When should I use research-paper-writing?
Use it in idea/research while framing contributions; in validate when polishing a prototype paper; and in build/docs when aligning sections with what you actually built.
Is research-paper-writing safe to install?
It is primarily markdown procedural guidance with no bundled executables in the excerpt; still review the Security Audits panel on this Prism page before enabling in your agent.
SKILL.md
READMESKILL.md - Research Paper Writing
interface: display_name: "Research Paper Writing" short_description: "Academic paper writing and section-level refinement" default_prompt: "Use $research-paper-writing to improve my paper's structure, flow, and section writing quality." # Abstract Writing Guide ## Goal Write a strong abstract by doing three things repeatedly: 1. Think through the abstract logic first. 2. Follow one template (Version 1/2/3 below). 3. Revise the abstract many times. ## Pre-Writing Questions (Important) Answer these before writing: 1. What technical problem do we solve, and why is there no well-established solution? (important) 2. What is our technical contribution? 3. Why can our method work in essence? 4. What technical advantage and new insight do we provide? (important) ## Version 1: Challenge -> Contribution Introduce the technical challenge, then use one to two sentences to present the technical contribution that solves the challenge. ### Structure 1. Task. 2. Technical challenge for previous methods. 3. One to two sentences introducing the technical contribution for solving the challenge. 4. Benefits of the technical contribution. 5. Experiment summary. ### Expert Notes 1. Discuss previous work around the technical challenge that we actually solve. 2. For the contribution sentence(s), usually mention the technical term/name only; do not explain every detailed step. 3. The technical term must be easy to understand; readers should not feel a jump. 4. This ability is very important for writing a good abstract. Version 1 local cite: 1. `references/examples/abstract/template-a.md` ## Version 2: Challenge -> Insight -> Contribution Introduce the technical challenge, then use one to two sentences to present the insight for solving the challenge, and then one sentence to present the technical contribution that implements this insight. ### Structure 1. Task. 2. Technical challenge for previous methods. 3. One sentence introducing the insight for solving the challenge. 4. One to two sentences introducing the technical contribution that implements the insight. 5. Benefits of technical novelty. 6. Experiment summary. ### Expert Notes 1. Discuss previous work around the technical challenge that we actually solve. 2. Introduce the insight in one clear sentence. 3. For the implementation sentence(s), usually mention the technical term/name only; do not explain every detailed step. 4. The technical term must be easy to understand; do not create a jump in reading. 5. This ability is very important for writing a good abstract. Version 2 local cite: 1. `references/examples/abstract/template-b.md` ## Version 3: Multiple Contributions Version 3: When there are multiple technical contributions, describe each contribution together with its technical advantage. ### Structure 1. Task. 2. If needed, one contrast sentence about prior methods. 3. Contribution sentence 1 + technical advantage. 4. Contribution sentence 2 + technical advantage. 5. Contribution sentence 3 + technical advantage. 6. Experiment summary. ### Expert Notes 1. When there are multiple technical contributions, describe each contribution together with its technical advantage. 2. The ability to express "contribution + advantage" in one sentence is very important for writing a good abstract. Version 3 local cite: 1. `references/examples/abstract/template-c.md` ## Example Bank 1. `references/examples/abstract-examples.md` 2. `references/examples/abstract/template-a.md` 3. `references/examples/abstract/template-b.md` 4. `references/examples/abstract/template-c.md` ## Abstract Quality Checklist 1. Can a reader identify task, challenge, insight/contribution, and results in one pass? 2. Are all major claims supported by experiments? 3. Are technical names self-contained and readable? 4. Is there any sentence that mixes too many messages? # Conclusion Writing Guide ## Goal Close the paper with clear takeaways and credible limitations. ## Structure 1. Restate