research-paper-writing

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.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "research-paper-writing" with this command: npx skills add master-cai/research-paper-writing-skills/master-cai-research-paper-writing-skills-research-paper-writing

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

  1. Clarify the paper story before sentence-level edits.
  2. Use section-specific guidance in references/.
  3. Rewrite paragraph-by-paragraph with one message per paragraph.
  4. Run reverse outlining after writing each section.
  5. Check every major claim in Abstract/Introduction against experimental evidence.
  6. Run final-paper adversarial review with references/paper-review.md.

Global Principles

  1. Keep one paragraph for one message only.
  2. State the paragraph message in the first sentence.
  3. Make nouns self-contained; define new terms before reusing them.
  4. Maintain sentence-to-sentence flow (cause, contrast, consequence, or refinement).
  5. Iterate with adversarial self-review: read as a skeptical reviewer.
  6. Treat visual quality as core content, not decoration.
  7. Use a clean teaser and pipeline figure.
  8. Use readable, minimal-ink tables.
  9. Keep formatting consistent and tidy.

Paragraph Clarity Check (Important)

Use this quick test whenever the user asks whether a paragraph "flows" or is clear.

  1. 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)?
  2. 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.
  3. 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 Rview): 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.

  1. Add an end-of-draft self-review question list in five dimensions:
    • contribution,
    • writing clarity,
    • experimental strength,
    • evaluation completeness,
    • method design soundness.
  2. Treat claim-evidence alignment as a hard constraint, especially for Abstract and Introduction.
  3. Perform adversarial writing: review as a skeptical reviewer and resolve every high-risk question.
  4. Revise until major rejection risks are explicitly addressed.

Execution Rules

  1. Build a mini-outline before drafting prose.
  2. For each subsection, explicitly include motivation, design, and technical advantage when applicable.
  3. Avoid writing style that looks like incremental patching of a naive baseline.
  4. Keep terminology stable across the full paper.
  5. If a claim cannot be supported by results, weaken or remove the claim.
  6. Before finalizing, append and answer a five-dimension self-review question list, then revise the paper based on unresolved items.
  7. 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:

  1. A compact section outline (3-7 bullets).
  2. Revised paragraphs with explicit paragraph roles (opening/challenge/method/advantage/evidence/limitation).
  3. A short self-review checklist covering clarity, flow, terminology consistency, unsupported claims, and missing evidence.
  4. A claim-evidence map for each major claim in the revised text using Claim: ... | Evidence: ... | Status: supported/needs evidence.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Research

learn-anything-in-one-hour

Teach users any new skill/knowledge X in ~1 hour using a fixed 4-step workflow optimized for complete beginners, focusing on 80/20 rule for maximum value in minimum time. Triggers when user asks to learn something new quickly, or mentions "learn X in one hour".

Archived SourceRecently Updated
Research

X/Twitter Research

# X/Twitter Research Skill

Archived SourceRecently Updated
Research

council

Convene the Council of High Intelligence — multi-persona deliberation with historical thinkers for deeper analysis of complex problems.

Archived SourceRecently Updated
Research

polymarket-openclaw-trader

Reusable Polymarket + OpenClaw trading operations skill for any workspace. Use when the user needs to set up, run, tune, monitor, and deploy an automated Polymarket trading project (paper/live), including env configuration, risk controls, reporting, and dashboard operations.

Archived SourceRecently Updated