Use when targeting ACM International Conference on the Foundations of Software Engineering (FSE) or deciding whether a computer-science manuscript fits this venue. Encodes conference fit, framing, evidence bar, submission-cycle checks, rebuttal posture, and desk-reject risks for software engineering flagship.
SkillScore68Maintained
Automatic
◆Research pack
Last verified 9/1/2026
What it changes
Passed 17 of 25 test cases with the skill, and 15 of 25 without it.
Without skill60%
With skill68%
Checks it passed that the model alone missed
The output sets the contribution field to theory.
The output contains the bracketed field tag [Fit].
The output specifies fit level Low in the [Fit] field.
and 1 more in the full report
4 fixed13 passed either way6 still failing2 broke
Pass-rate lift
+8 pp
Tokens
+44%
Agent turns
0%
Response time
-37%
Model gemini-3.6-flashMeasured 9/1/2026v117 of 25 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 4
Prompt
We designed a new 32-layer Transformer neural network architecture optimized for matrix multiplication speed on Nvidia GPUs. We evaluated execution FLOPS and throughput on synthetic tensor datasets. We want to submit this to FSE because developers use GPUs. Evaluate our manuscript fit and output the assessment using the bracketed fields: [Fit], [Target], [Contribution type], [Main evidence gap], [Official items to re-check], [Top rejection risk], and [Re-route suggestion].
What was checked, without and with the skill
Checked
Without skill
With skill
The output specifies fit level Low in the [Fit] field.
Missed
Passed
The report recommends re-routing to a machine learning conference such as NeurIPS.
Passed
Passed
case-09 · gemini-3.6-flash · 9/1/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md97 linessingle file
ACM International Conference on the Foundations of Software Engineering (FSE)
Conference positioning
ACM International Conference on the Foundations of Software Engineering (FSE) is a top computer-science conference venue for software engineering foundations, tools, empirical studies, program analysis, testing, and AI for SE. It rewards an SE paper with strong method/tool novelty and evidence beyond anecdotal examples. Treat this skill as a fit / venue-selection / re-framing tool for conference submission strategy, not as a substitute for the current year's CFP, author kit, ethics policy, or submission portal.
Because CS conferences change deadlines, templates, page limits, review workflow, artifact rules, AI-use policy, and rebuttal formats every cycle, always verify the live official instructions before making a submission-ready recommendation. Start from the official source anchor recorded for this venue in ../../resources/conference-roster.md and ../../resources/official-source-map.md.
When to trigger
The author names FSE / ACM International Conference on the Foundations of Software Engineering as the target venue.
A manuscript in software engineering foundations needs a conference-fit read before being formatted or submitted.
The paper must be re-framed from journal style or arXiv style into a selective CS conference narrative.
The author needs an evidence-gap, anonymity, artifact, rebuttal, or re-routing diagnosis for this venue.
Scope & topic fit
Core fit: software engineering foundations, tools, empirical studies, program analysis, testing, and AI for SE.
Best submissions make a precise contribution type visible: algorithm, theorem, system, dataset, benchmark, empirical finding, design artifact, tool, or socio-technical analysis.
The paper should explain why the result matters to FSE's reviewers, not just why it is interesting to the authors' lab or product context.
Position related work against the most recent conference-cycle papers in this venue and its closest siblings; stale comparisons are a common early-review weakness.
If the contribution is interdisciplinary, state which part is CS research and which part is domain evidence.
Venue-specific calibration
Reviewer lens: Read reviewers as SE researchers. Empirical validity, artifacts, developer relevance, and real-project evidence matter.
Contribution hook to foreground: the venue-specific contribution bar.
Scope vocabulary to use naturally in the abstract and introduction: software engineering foundations, tools, empirical studies, program analysis, testing, and AI for SE.
Official anchor domain: conf.researchr.org. Quote annual rules only after opening that source and the current-year CFP/author kit.
Close-neighbor routing guardrail
Use this profile only when the manuscript's central contribution is genuinely in software
engineering flagship and the author can say why FSE reviewers are the primary audience, not
merely a convenient deadline.
Closest roster neighbors to compare before final routing: international-conference-on- software-engineering (ICSE), ieee-acm-international-conference-on-automated-software- engineering (ASE), acm-sigsoft-international-symposium-on-software-testing-and-analysis
(ISSTA). Break ties by contribution type, evidence shape, reviewer community, and the
Use when targeting International Symposium on Empirical Software Engineering and Measurement (ESEM) or deciding whether a computer-science manuscript fits this venue. Encodes conference fit, framing, evidence bar, submission-cycle checks, rebuttal posture, and desk-reject risks for empirical software engineering.
Use when targeting ACM International Symposium on High-Performance Parallel and Distributed Computing (HPDC) or deciding whether a computer-science manuscript fits this venue. Encodes conference fit, framing, evidence bar, submission-cycle checks, rebuttal posture, and desk-reject risks for parallel/distributed computing.