agentleFS
JihaoXinJihaoXin/paper-machine/skills/paper-structure/SKILL.md

paper-structure

Skill0 starsChanged 3 months agoMITView on GitHub

Write the sections of a research paper so each does its job. Use when drafting or restructuring an abstract, introduction, related work, method, experiments, or conclusion. Covers what belongs where and the failure patterns that make agent-written papers read as hollow.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If a paper is close to yours, say so plainly and say what is different.

    line 41
  2. Distinctive:

    If the method is simple, say it is simple.

    line 50
  3. Very specific:

    every number traces to a file (see numbers-traceable)

    line 60
  4. Distinctive:

    Write it yourself, honestly, and do it before a reviewer does it for you.

    line 67

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Paper Structure

Agent-written drafts are usually grammatical and usually hollow. They restate the topic instead of making an argument. This is a section-by- section account of what each part has to accomplish.

Abstract

Four sentences, in this order, is enough: the problem, why existing work does not settle it, what you did, what you found with a number.

The most common failure is an abstract that describes the topic rather than the finding. "We study the effect of X on Y" is not a result. "X reduces Y by 12 percent, but only when Z holds" is.

Introduction

The job is to make the reader believe the problem is real before you propose anything.

  1. The context, in two or three sentences, not a history of the field
  2. The specific gap, stated so a reader can disagree with it
  3. Your approach in one sentence
  4. Your contributions as claims, not activities

"We conduct extensive experiments" is an activity. "We show that method X fails whenever the input distribution shifts by more than k" is a claim. Write claims.

Related work

Organise by idea, not chronology, and never as a list of summaries. The useful unit is: this line of work does A, it assumes B, and B does not hold in our setting.

If a paper is close to yours, say so plainly and say what is different. Reviewers already know that paper. Failing to cite it reads as ignorance or concealment.

Method

Enough for someone to reimplement it. Define your notation before using it. State assumptions explicitly, including the uncomfortable ones.

If the method is simple, say it is simple. Dressing a simple idea in notation to look sophisticated is transparent and it annoys reviewers.

Experiments

Structure: setup, then research questions, then a result per question.

  • state datasets, baselines, metrics and seeds before any numbers
  • one table or figure should answer one question
  • report variance, not just means
  • every number traces to a file (see numbers-traceable)

Include the experiment that did not work. Its absence is more conspicuous than its presence.

Limitations

Write it yourself, honestly, and do it before a reviewer does it for you. A limitations section that names the real weakness buys credibility for everything else. One that lists only "we did not test on more datasets" is read as evasion.

Conclusion

Two or three sentences: what you found, what it means, what is next. Do not introduce new claims here, and do not restate the abstract word for word.

Global failure patterns to check for

  • Restatement. The same sentence appearing in abstract, intro and conclusion with different word order.
  • Unsupported comparatives. "Significantly better", "much faster", "substantially improves", with no number and no test.
  • Orphan artifacts. A figure or table nothing refers to.
  • Contribution inflation. Four bullets that are one contribution split four ways.
  • Passive vagueness. "It was observed that improvements occurred." Say who did what and by how much.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.