icde-writing-style
Use when revising an IEEE ICDE paper for the first-page data-engineering contract, a reconstructable mechanism description, the running-example device, performance claims scoped to the workloads actually run, single-blind first-person phrasing, and 12-page IEEE two-column compression that survives a builder-heavy program committee.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icde-writing-style --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.
# ICDE Writing Style Use this when revising the main paper. ICDE papers must state, compactly, what data-engineering primitive is new and give a builder enough to reconstruct it, all inside a tight IEEE two-column budget. ## Revision rules - Put the **data-engineering contribution on the first page**: the bottleneck, why current systems fall short, the mechanism, the measured evidence, and who can build on it. - Name the **bottleneck and the operating point**. A systems claim without a workload, hardware, and cost metric is unfalsifiable and reads as marketing to an ICDE reviewer. - Make the **mechanism reconstructable**. The reader should be able to rebuild the core idea from the body; "a novel structure" is not a mechanism. - Pair every performance claim with a **figure, table, or measured crossover**, and disclose the **cost** of every gain — ICDE reviewers distrust a win with no accounting. - Use a **running example** (one concrete workload) introduced early and reused; it carries intuition through the paper more efficiently than repeated abstraction. - Because ICDE is **single-blind**, write in natural first person and cite your own prior work directly — do not perform the ano
- Revision rules
- Mechanism-presentation discipline
- Sentence-level rewrites
- Vignette: compressing into 12 IEEE two-column pages
- Output format
What does the icde-writing-style skill do?
Use when revising an IEEE ICDE paper for the first-page data-engineering contract, a reconstructable mechanism description, the running-example device, performance claims scoped to the workloads actually run, single-blind first-person phrasing, and 12-page IEEE two-column compression that survives a builder-heavy program committee.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icde-writing-style --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.