ICDE Skills

A 12-skill depth pack for IEEE ICDE (International Conference on Data Engineering) research-track papers: three-venue routing across SIGMOD/PVLDB/ICDE, the two-round-per-edition calendar, single-blind CMT submission, revise-and-resubmit dynamics, IEEE-format camera-ready and Xplore publication, artifact availability, reproducibility, related work, experiments, and workflow. Grounded in the ICDE 20

by @brycewang-stanford 6 skills

Install

npx skillmds@latest add plugin:brycewang-stanford/icde-skills

One command, no setup. In Claude Code it lands as a managed plugin you can enable, disable or remove with /plugin. On any other agent it installs the 6 skills into that agent's own folder.

Or inside Claude Code

In the Plugins tab, add this marketplace:

skillmds/skillmd
/plugin install brycewang-stanford-icde-skills@skillmd

Adds the marketplace once; later plugins need the second line only.

Or install by hand

Download the plugin and unzip its skills/ folder into your agent's skills directory. Works with every agent, no CLI needed.

Download plugin Paths per agent

Just the markdown? SKILL.md files only.

This plugin

skills: 6
authors: 1

Published by a registry member. Review its skills before installing.

Skills in this plugin

▌
Icde Submission · brycewang-stanford
Use when auditing an IEEE ICDE research-track submission for round choice, Microsoft CMT setup, conflict declarations, the IEEE 12-page format, single-blind requirements, supplemental-material availability, the June/November two-round calendar, desk-reject triggers, and final-week sequencing for a data-engineering systems paper.

1k repo stars
▌
Icde Related Work · brycewang-stanford
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.

1k repo stars
▌
Icde Writing Style · brycewang-stanford
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.

1k repo stars
▌
Icde Author Response · brycewang-stanford
Use when responding to IEEE ICDE reviews, whether drafting a rebuttal to reviewer concerns or preparing a revise-and-resubmit change document for an invited ICDE revision under the 4-week window, coordinating with area chairs, addressing systems-reviewer pushback on baselines and cost, and deciding what is feasible before the revision deadline.

1k repo stars
▌
Icde Topic Selection · brycewang-stanford
Use when deciding whether a project is a strong IEEE ICDE fit, routing among the three database venues from ICDE's seat (SIGMOD's quarterly rounds vs PVLDB's monthly deadlines vs ICDE's two rounds), choosing ICDE research vs industry track, applying the data-management-primitive test, and comparing with TKDE, EDBT, or systems venues.

1k repo stars
▌
Icde Artifact Evaluation · brycewang-stanford
Use when packaging IEEE ICDE code, data, workload generators, and logs as supplemental material whose availability reviewers score, and for any post-acceptance reproducibility or badge process the edition runs. Covers what a builder-heavy committee inspects first, making a data-systems benchmark turnkey, and single-blind packaging.

1k repo stars