jais-rebuttal
Use when a Journal of the Association for Information Systems (JAIS) revision decision has arrived and you must plan the revision and draft the point-by-point response — prioritizing the Senior Editor's letter, answering theory- and method-specific concerns in their proper currency, updating the required data materials, and keeping the manuscript within its category budget and double-blind anonymity. Drafts the response after the manuscript is actually revised; interpret the decision first with jais-review-process.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jais-rebuttal --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.
# Rebuttal & Response Letter (jais-rebuttal) ## When to trigger - You received a major or minor revision (or a reject-and-resubmit) from JAIS - You have read the decision with `jais-review-process` and revised the manuscript - You need a point-by-point response that the Senior Editor and reviewers can audit - Reviewers conflict and you must decide which way to revise ## Revise first, then write the response Do not draft the response letter before the manuscript is actually revised. The response is a map to real changes, not a list of promises. For each point, make the change in the manuscript first; the letter then points to where and how. This matters more at JAIS because the process is **developmental** — the SE is engaging with the paper's trajectory, and an honest, concrete response shows you used the developmental opportunity rather than deflecting it. ## Anchor the revision in the Senior Editor's letter The **Senior Editor owns the decision**, so the SE's letter sets priorities. Build a triage table: SE-elevated concerns first, then AE and reviewer points, flagging where reviewers conflict. Resolve conflicts in the direction the SE signaled, and say so explicitly when you do.
- When to trigger
- Revise first, then write the response
- Anchor the revision in the Senior Editor's letter
- Disagree only with evidence, and only where the SE has not ruled
- Answer concerns in the currency of your tradition
- Update the required data materials
- Keep length, anonymity, and category in check
- Open the response with a contribution-and-changes summary
- Write a clean, auditable response
- Checklist
- Anti-patterns
- Output format
What does the jais-rebuttal skill do?
Use when a Journal of the Association for Information Systems (JAIS) revision decision has arrived and you must plan the revision and draft the point-by-point response — prioritizing the Senior Editor's letter, answering theory- and method-specific concerns in their proper currency, updating the required data materials, and keeping the manuscript within its category budget and double-blind anonymity. Drafts the response after the manuscript is actually revised; interpret the decision first with jais-review-process.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jais-rebuttal --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.