agentleFS
Sign inStart free
NilsHellwigNilsHellwig/acl-paper-skills/skills/writing/SKILL.md

writing

Skill3 starsChanged 13 days agoMITView on GitHub

Writing rules for NLP/ACL paper prose. Use when writing, editing, shortening or rephrasing paper text (sections, abstract, captions, rebuttal or response text), or when checking prose for machine-written style.

51 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use addskill, apply-firmware and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ryanportfolioSkill

    addskill

    Create, import, update, or install repo or personal skills: runtime ownership, resources, discovery checks.

    Also in 6 projects that use this

  • ryanportfolioSkill

    apply-firmware

    Bring current folder (plain folder, existing repo, old or partial firmware copy) up to full Harness Firmware in place. Mirror external repo → adopt-repo.

    Also in 6 projects that use this

  • +10 more from ryanportfolio

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 45 edited versions we read keep these.

  • 1

    Distinctive

    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. Very specific:

    Every factual change to a claim about another paper goes through the literature skill: the claim must match the paper's body.

    line 22
  2. Distinctive:

    Run the checks of ai-patterns.md on every sentence you produce or touch.

    line 23

“Common” is measured: kept by at least 6 in 10 of the 45 edited versions of this file we could read. “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

How to edit and, on request, draft prose for an ACL paper. The authors write the paper; this skill makes their text clearer and keeps it theirs.

Order of authority

  1. ## Style and ## Terminology in the project's CLAUDE.md: the authors' own rules.
  2. This skill and ai-patterns.md.
  3. General academic English, in the variant set as english in paper.config.json.

Asking

Formatting and wording questions often have several valid answers (table layout, caption style, notation, where a result goes, how strongly to phrase a claim). When neither CLAUDE.md nor the existing text settles one, ask with AskUserQuestion: the options, each with a short example, and your recommendation. Add the answer to ## Style in CLAUDE.md when the user wants it to hold for the whole paper.

Editing the authors' text

  • Change as little as the goal needs. Keep the authors' terms, claims, structure and voice; fix what is unclear, wrong or reads as machine-written.
  • Show each change as before → after with a one-line reason, unless the user asked for a direct rewrite.
  • Every factual change to a claim about another paper goes through the literature skill: the claim must match the paper's body.
  • Run the checks of ai-patterns.md on every sentence you produce or touch.

Drafting new text

Drafting is fine when the user asks for it. Work from their material: notes, results tables, bullet points, the existing sections. Mark the draft as a draft and point out each claim that still needs a citation or a number from their results. Write no results, numbers or citations that are not in their material or in a read-full paper.

ACL conventions

  • \citet{} when the authors are part of the sentence ("\citet{x} show ..."), \citep{} otherwise. Never an author-year in plain text.
  • Introduce every abbreviation once with its spelled-out form, then use the abbreviation. Method, model and dataset names coined by a cited paper need no spelled-out form.
  • Non-breaking space before references: Table~\ref{...}, Section~\ref{...}.
  • Present tense for what the paper does and shows, past tense for what was run.
  • Numbers in text match the tables exactly.
  • The Limitations section states real limitations of this work. Current ARR rules on it (and on page limits, anonymity, AI assistance) come from the guidelines-check skill, never from memory.

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.

Check your setup, free