Menu

Individual skill

fse-writing-style

0upvotes

Use when revising an ESEC/FSE paper for a practitioner-grounded software-engineering contribution on the first page, research-question contracts, a threats-to-validity section that argues rather than recites, evidence proportional to the claim, double-anonymous wording, and disciplined use of the ACM-template page budget.

FSE-Skills/skills/fse-writing-style/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,409
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# FSE Writing Style

Use this when revising the main paper. FSE papers are PACMSE journal articles read by SE
empiricists, so they need a **software-engineering contribution stated in the first page** and
evidence a reviewer trusts. The failure this skill prevents is a technically fine paper that reads
like a systems demo or an ML result with an SE title glued on.

## Revision rules

- **Lead with the SE contribution:** the problem a practitioner recognizes, why the current state
  is inadequate, the contribution (technique and/or finding), the evidence, and what changes for
  software engineering.
- **State research questions as contracts.** Each RQ should name what is measured and how it will
  be judged; every RQ must be answered explicitly in the results, and no result should exist
Back to top