fse-submission
Use when auditing an ESEC/FSE research-track submission for HotCRP readiness, covering the mandatory paper-registration step, the ACM Primary Article Template page budget, double-anonymous "heavy" anonymity, the open-science Data Availability statement, PACMSE publication, and desk-reject triage before the AoE cutoff.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fse-submission --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 Submission Run this audit before uploading to the FSE HotCRP site. FSE research papers are published as **journal articles in PACMSE** (Proceedings of the ACM on Software Engineering), so the submission is judged like a journal manuscript that also earns a conference slot. Every number below was read from the FSE 2026/2027 research-papers calls on 2026-07-09 via search renderings of the `conf.researchr.org` URLs (see `resources/official-source-map.md`); treat them as a one-cycle snapshot and reopen the live call first. ## The two-step deadline FSE separates **paper registration** from **paper submission**, and both are AoE: - **Registration** locks in title, abstract, authors, and conflicts a week early (FSE 2026: 4 September 2025). Miss it and the system will not accept the PDF later. - **Submission** uploads the anonymized PDF (FSE 2026: 11 September 2025). FSE 2027's single research deadline is 2 October 2026. Register with the *real* title and abstract, not a placeholder — the abstract drives reviewer bidding, and a registered abstract that diverges from the final paper quietly worsens your PC match. ## Format and page budget - **ACM Primary Article Template**, unmodified
- The two-step deadline
- Format and page budget
- Double-anonymous "heavy" sweep
- Open science at submission time
- Desk-risk triage
- Final-week order of operations
- Reverify each cycle
- Output format
Mechanical pass on the submission PDF and any anonymized artifact archive pdfinfo paper.pdf | grep -Ei 'author|creator|producer' pdftotext paper.pdf - | grep -nEi 'github\.com/[a-z0-9-]+|gitlab|zenodo\.org/record|acknowledg|grant' | head unzip -l artifact.zip | grep -Ei '\.git/|\.DS_Store|/home/|/Users/' | head grep -rni 'university\|@[a-z0-9.]*\.edu\|our (tool|group|lab)' artifact/ --include='*.md' | head
What does the fse-submission skill do?
Use when auditing an ESEC/FSE research-track submission for HotCRP readiness, covering the mandatory paper-registration step, the ACM Primary Article Template page budget, double-anonymous "heavy" anonymity, the open-science Data Availability statement, PACMSE publication, and desk-reject triage before the AoE cutoff.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fse-submission --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.