icde-topic-selection
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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icde-topic-selection --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 Topic Selection Use this before writing. ICDE is strongest for **data engineering** — the design, building, management, and evaluation of data-intensive systems — where the contribution is a reconstructable data-management primitive with a systems-grade evaluation. ## The data-management-primitive test Ask what primitive the paper advances: an **access method**, a **query operator**, an **execution or storage mechanism**, a **transaction or concurrency protocol**, a **data integration/cleaning/provenance technique**, or a **scalable analytics engine**. If no primitive exists — if the database is merely a container for a result that lives elsewhere — the ICDE framing does not exist either. ## Routing from ICDE's seat: the three-venue triangle The scopes of ICDE, SIGMOD, and VLDB overlap almost entirely, so routing is usually about **calendar geometry and house culture**, not topic. Deciding from ICDE's seat: | If the deciding factor is... | Lean toward | Because | |---|---|---| | You want two fixed shots a year and IEEE-Xplore proceedings | **ICDE** | Two rounds per edition (≈June + November), single-blind, IEEE format | | You want quarterly journal-style rounds with a formal
- The data-management-primitive test
- Routing from ICDE's seat: the three-venue triangle
- Fit signal table
- Sharpening moves before committing
- Output format
What does the icde-topic-selection skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icde-topic-selection --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.