Individual skill
fse-related-work
Use when positioning an ESEC/FSE submission against the software-engineering literature across ICSE, FSE, ASE, ISSTA, MSR, and the SE journals (EMSE, TSE, TOSEM), writing delta-first contrast rather than a citation catalog, keeping self-citations double-anonymous, and handling concurrent, preprint, and prior-version overlap.
FSE-Skills/skills/fse-related-work/SKILL.md
Source commit 932eb23331721b16e967c59f093781be1928b498
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Network or broad shell
- 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,401
- Repository last updated
- Sep 27, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- academic-writing Repository topic
- agent-skills Repository topic
- journal Repository topic
- academic-research Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- awesome-list Repository topic
- claude Repository topic
- claude-code Repository topic
- economics Repository topic
- engineering Derived category
- writing Derived category
- research Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 4,309 bytes
Read excerpt
# FSE Related Work
Use this to audit novelty and eligibility. FSE reviewers are close to the SE literature and expect
to see where your paper sits relative to the nearest prior work — stated as a **delta**, not a
list. Reopen the current call for dual-submission, anonymity, and prior-publication rules before
advising authors.
## Positioning checks
- **Separate the software-engineering novelty from the engineering effort.** What is new: a
technique, an empirical finding, a validated measurement, a design, or an evidence regime nobody
had covered?
- **Cover the SE lanes.** FSE reviewers expect the flagship venues and the journals, not just the
papers nearest your method (see the table). A bibliography missing the obvious sibling work reads