Individual skill
edbt-writing-style
Use when revising an EDBT paper for a data-management contribution on the first page, a reproducibly described mechanism, an evaluation that survives a database-systems reviewer, honest scope, and disciplined use of the per-shape page budget (Regular / Experiments-&-Analysis / Vision) in the OpenProceedings template.
EDBT-Skills/skills/edbt-writing-style/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
- writing Derived category
- 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,607 bytes
Read excerpt
# EDBT Writing Style
Use this when revising the main paper. EDBT papers are read by database-systems reviewers and
published open access on OpenProceedings, so they need a **data-management contribution stated on
the first page** and an evaluation a skeptic trusts. The failure this skill prevents is a technically
fine paper that reads like a vague performance claim or a re-skinned ML result with a database title.
## Revision rules
- **Lead with the data-management contribution:** the concrete problem (a storage, query-processing,
indexing, transaction, integration, or data-quality problem), why current systems fall short, the
contribution (mechanism and/or study), the evidence on real workloads, and what it enables.
- **Make the mechanism reproducible in prose.** Describe the algorithm, data structures, parameters,
and system integration precisely enough that a competent reader could reimplement it — vagueness