Individual skill
fse-experiments
Use when designing or auditing ESEC/FSE empirical evaluations, covering real subject systems, fair baselines, SE-standard statistics and effect sizes, qualitative and mixed-methods rigor, contamination-aware LLM ablations, provenance for mining studies, and matching evidence to the shape of each software-engineering claim.
FSE-Skills/skills/fse-experiments/SKILL.md
Source commit 932eb23331721b16e967c59f093781be1928b498
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- 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.
- 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
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# FSE Experiments
Use this before submission when the empirical story is not yet locked. FSE reviewers are SE
empiricists; the evaluation is where a good idea is won or lost. The organizing principle is
**evidence proportional to the claim** — the study must test the thing the paper actually asserts,
on subjects and baselines a skeptic would accept.
## Evaluation audit
- **Match evidence to the claim shape.** A claim about *developer behavior* needs behavior data; a
claim about *detection* needs a labeled ground truth; a claim about *scalability* needs runtime
on realistically sized inputs. Accuracy against a proxy label is not evidence for a practice
claim.
- **Use real subject systems,** sampled by a stated criterion, and list them in the artifact. Toy