research-paper-writing
- Repo stars 3,238
- Author updated Live
- Author repo Research-Paper-Writing-Skills
- Domain
- Writing
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @Master-cai · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: research-paper-writing
description: Improve academic paper writing quality for ML/CV/NLP-style papers with clear section structure…
category: writing
runtime: no special runtime
---
# research-paper-writing output preview
## PART A: Task fit
- Use case: 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..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Overview / Core Workflow / Global Principles” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “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.”.
- **02** When the source has headings, the agent prioritizes “Overview / Core Workflow / Global Principles” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands.
Start with a small task and check whether the result follows “Overview / Core Workflow / Global Principles”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: research-paper-writing
description: Improve academic paper writing quality for ML/CV/NLP-style papers with clear section structure…
category: writing
source: Master-cai/Research-Paper-Writing-Skills
---
# research-paper-writing
## When to use
- Improve academic paper writing quality for ML/CV/NLP-style papers with clear section structure, paragraph flow, and re…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Overview / Core Workflow / Global Principles” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "research-paper-writing" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Overview / Core Workflow / Global Principles
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files, run shell commands | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} 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.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review