fse-supplementary
Use when deciding what belongs in an ESEC/FSE paper body versus its anonymized artifact and appendices, covering the ACM-template page budget, the rule that decision-critical evidence stays inside the reviewed pages, double-anonymous supplementary material, and how to split an empirical-SE paper between body and package.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fse-supplementary --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# FSE Supplementary Use this when assembling FSE supplementary material. The governing rule is simple and strict: **the paper must be judgeable from the reviewed pages alone.** The artifact and any appendix support the paper; they do not hold the argument. Reviewers read the artifact at their discretion, so anything the decision depends on lives in the body. ## What goes where | Content | Body (within page budget) | Artifact / appendix | |---|---|---| | Research questions and their answers | Yes | — | | Core technique or study design | Yes | Full parameter grids, extra config | | The headline results and their threats | Yes | Full result tables, secondary plots | | Statistical tests behind a claim | The result + test named | The computation notebook | | Subject-system list | Summary + selection criterion | The complete list | | Raw data, logs, scripts | — | Yes | | Reproduction instructions | A pointer | The README and run scripts | If a reviewer would need to open the artifact to know whether to accept, the paper is mis-partitioned — move that evidence into the body. ## The page-budget discipline FSE's ACM-template budget (FSE 2027: ≤18 pages of text and figures, plus reference pa
- What goes where
- The page-budget discipline
- Double-anonymous supplementary rules
- Appendix architecture (when the template allows in-paper appendices)
- Vignette: splitting a mixed-methods paper
- Output format
What does the fse-supplementary skill do?
Use when deciding what belongs in an ESEC/FSE paper body versus its anonymized artifact and appendices, covering the ACM-template page budget, the rule that decision-critical evidence stays inside the reviewed pages, double-anonymous supplementary material, and how to split an empirical-SE paper between body and package.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fse-supplementary --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.