Individual skill
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.
ICDE-Skills/skills/icde-writing-style/SKILL.md
Source commit 932eb23331721b16e967c59f093781be1928b498
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Network or broad shell
- 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,400
- 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
- legal Derived category
- writing Derived category
- data Derived category
- research 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 · 3,894 bytes
Read excerpt
# 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.