icdt-author-response
Use when responding to ICDT (International Conference on Database Theory) referees — principally the first-cycle Revise-and-resubmit round, where you return a corrected paper that closes each identified proof gap, plus any short author-comment phase, keeping the response anonymous and mapping every referee point to a concrete change in the revised PDF.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icdt-author-response --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 Author Response Write the response for a venue where the referees **checked your proofs**. ICDT's central author-interaction mechanism is the **Cycle-1 Revise-and-resubmit**: not a short rebuttal that argues taste, but a returned paper in which each gap the referees named has been *closed* and the change documented. The second read is done by the same referees; a point raised and not addres
What does the icdt-author-response skill do?
Use when responding to ICDT (International Conference on Database Theory) referees — principally the first-cycle Revise-and-resubmit round, where you return a corrected paper that closes each identified proof gap, plus any short author-comment phase, keeping the response anonymous and mapping every referee point to a concrete change in the revised PDF.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icdt-author-response --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.