psychrev-rebuttal
Use when a Psychological Review decision letter (usually a major revision) has arrived and you must write the response document and revise the theory. Drafts the response and revision plan; it does NOT run the resubmission preflight (psychrev-submission) or build new theory from scratch (psychrev-theory-construction).
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill psychrev-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.
# Revision & Response Document (psychrev-rebuttal) > Write the response **after** the theory has actually been revised. At a theory journal a > response that argues rather than strengthens the model fails. Revise first, then document. ## When to trigger - A major/minor revision decision has arrived - You have reviewer comments and must produce a point-by-point response - You are tempted to defend
What does the psychrev-rebuttal skill do?
Use when a Psychological Review decision letter (usually a major revision) has arrived and you must write the response document and revise the theory. Drafts the response and revision plan; it does NOT run the resubmission preflight (psychrev-submission) or build new theory from scratch (psychrev-theory-construction).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill psychrev-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.