icde-related-work
Use when positioning an IEEE ICDE submission against the database canon and neighboring venues, running a reinvention audit across SIGMOD, VLDB, EDBT, and shipping systems, handling two-round concurrency, distinguishing engineering delta from genuine novelty, and covering both the literature and production systems an ICDE reviewer expects.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icde-related-work --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 Related Work Use this to audit novelty and eligibility. Reopen the current call for the original-work and prior-publication rules before advising authors. ## Positioning checks - Separate **genuine novelty** (a new mechanism, access method, protocol, or primitive) from **engineering delta** (a faster implementation of a known idea). ICDE rewards the former; the latter needs an unusually strong evaluation to survive. - Run a **reinvention audit** against the deep database canon. Because data management has a fifty-year literature, a "new" index or join often has a 1980s or 1990s ancestor; find it and state the difference, or a reviewer will. - Cover **both** the research venues **and shipping systems**. ICDE reviewers expect you to know the relevant production databases, not just papers; ignoring a system that already does what you claim is a recognizable reject pattern. - Because ICDE is **single-blind**, cite your own prior work directly and link repositories freely — there is no anonymity to preserve in the bibliography. - State overlap with any prior short/workshop version honestly; the original-work rule bars work already published beyond a few double-column pages. ## Th
- Positioning checks
- The venue-ring coverage table
- The concurrency question at ICDE
- Positioning vignette
- Overlap judgment calls
- Output format
What does the icde-related-work skill do?
Use when positioning an IEEE ICDE submission against the database canon and neighboring venues, running a reinvention audit across SIGMOD, VLDB, EDBT, and shipping systems, handling two-round concurrency, distinguishing engineering delta from genuine novelty, and covering both the literature and production systems an ICDE reviewer expects.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icde-related-work --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.