icdt-workflow
Use when planning an ICDT (International Conference on Database Theory) campaign end to end, running the two-submission-cycle calendar backward from a chosen cycle deadline through abstract registration, the first-cycle revision round, LIPIcs camera-ready, and presentation at the co-located EDBT/ICDT event.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icdt-workflow --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.
# ICDT Workflow Plan the campaign backward from a chosen **cycle deadline**. ICDT's defining calendar feature is **two submission cycles per year**, so the first planning act is not "when is the deadline" but "which cycle, and does the Cycle-1 revision option help me?" Everything downstream — abstract registration, the revision window, LIPIcs camera-ready, and the talk at the co-located EDBT/ICDT
What does the icdt-workflow skill do?
Use when planning an ICDT (International Conference on Database Theory) campaign end to end, running the two-submission-cycle calendar backward from a chosen cycle deadline through abstract registration, the first-cycle revision round, LIPIcs camera-ready, and presentation at the co-located EDBT/ICDT event.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icdt-workflow --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.