research-paper-writing
- Repo stars 3,238
- Author repo Research-Paper-Writing-Skills
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 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.
- 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.
- Fluxly category
- Writing
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Author / version / license
- @Master-cai · no license declared
- Fluxly token estimate
- Lean
- Fluxly setup estimate
- Guided setup
- External API key
- No requirement detected
- Detected OS requirements
- Unspecified
- Runtime requirements
- Unspecified
- Detected file/system behavior
-
- Read-only
- Write / modify
- Shell exec
- Detected network behavior
- Local-only
- Install commands
- None (reference only)
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
The current SKILL.md does not define a fixed output example. 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.
Clarify the paper story before sentence-level edits. Use section-specific guidance in references/. Rewrite paragraph-by-paragraph with one message per paragraph.
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.
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?
Load only the needed section file: Introduction: references/introduction.md Abstract: references/abstract.md
Use references/paper-review.md for the full checklist and workflow. Add an end-of-draft self-review question list in five dimensions: contribution,
# 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.
… Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.
sections -> Overview → Core Workflow → Global Principles → Paragraph Clarity Check (Important) → Section Guides → Paper Review Core Points
terms -> Use this skill to rewrite a research paper into a reviewer-friendly, high-clarity draft. · 1. Clarify the paper story before sentence-level edits. · 1. Keep one paragraph for one message only. · 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? · Use references/paper-review.md for the full checklist and workflow. · 1. Build a mini-outline before drafting prose. · 1. A compact section outline (3-7 bullets).
files/cmd -> references/ · references/paper-review.md · references/does-my-writing-flow-source.md · references/introduction.md · references/abstract.md · references/related-work.md · references/method.md · references/experiments.md
body sha256 -> 45ac8a8e3d2d
Decide Fit First
Design Intent
How To Use It
Boundaries And Review