Individual skill
edbt-reproducibility
Use when strengthening EDBT reproducibility for a database-systems paper, covering a runnable artifact, pinned environments and workloads, dataset and query-log provenance, claim-to-evidence mapping, honest degrees of reproducibility, and consistency between the paper and the package for the open-access OpenProceedings record.
EDBT-Skills/skills/edbt-reproducibility/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
- Yes
- 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,411
- 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
- data Derived category
- data-databases 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 · 5,247 bytes
Read excerpt
# EDBT Reproducibility
Use this before submission and again before camera-ready. EDBT's community has a
reproducibility-forward culture, and the published record is **open access on OpenProceedings** —
so an inspectable, re-runnable package raises a paper's standing and, for an **Experiments &
Analysis** paper, *is* the contribution. The goal is that a competent reader could rebuild your
measurements and reach your conclusions.
## Evidence map
- Map each claim, mechanism, and reported number to a **verifiable location** — a paper section, a
table generated from a logged run, or a script in the artifact.
- For a mechanism, give enough of the algorithm, data structures, parameters, and system integration
that a reader could reimplement or rebuild it.