Agent skill

joc-rebuttal

Use when revising a Journal of Communication (JoC) manuscript after a revise-and-resubmit. The hard problem at JoC is that communication is a multi-paradigm field, so a single R&R can carry post-positivist, interpretive, critical, and computational reviewers who want incompatible things — inside a fixed 35-page cap. Plans the revision and response memo; it does not fabricate new results.

brycew6m4,252★ · +31/wk · 3 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill joc-rebuttal --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Path: Journal-of-Communication-Skills/skills/joc-rebuttal/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 984 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# R&R Revision & Response (joc-rebuttal) Communication is **not a single-paradigm discipline**, and JoC reviewers reflect that: one referee may reason as a post-positivist media-effects scholar, another as an interpretive or critical/cultural scholar, another from computational communication. A JoC R&R therefore is less "satisfy everyone" and more "**broker across paradigms** without breaking the paper" — and you must do it inside JoC's **hard ~35-page limit** (text, references, tables, figures, and endnotes all count). This skill is about that brokering and the page budget, not about inventing data. ## When to trigger - A JoC R&R arrived and you are scoping the revision before touching the manuscript - Two reviewers want changes that come from **different epistemologies** and partly conflict - Required additions threaten to push the paper over the 35-page cap - You are writing the cover memo to the Editor-in-Chief ## Step 1 — Map the reviewers by paradigm before you write anything For each reviewer, label the **stance** their comments come from (post-positivist / interpretive / critical / computational / mixed) and what "convincing" means to them — more controls and robustness, ri

What's inside
Steps it walks through
  1. When to trigger
  2. Step 1 — Map the reviewers by paradigm before you write anything
  3. Step 2 — Decide each comment with the page budget in view
  4. Step 3 — Broker the cross-paradigm conflicts in the open
  5. Step 4 — Keep the revision submittable
  6. Response memo structure (per reviewer, then a global note)
  7. Anti-patterns
  8. Output format
  9. Supplementary resources
More from Awesome-Journal-Skills
All skills →
About this skill
What does the joc-rebuttal skill do?

Use when revising a Journal of Communication (JoC) manuscript after a revise-and-resubmit. The hard problem at JoC is that communication is a multi-paradigm field, so a single R&R can carry post-positivist, interpretive, critical, and computational reviewers who want incompatible things — inside a fixed 35-page cap. Plans the revision and response memo; it does not fabricate new results.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill joc-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 984 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.

Keep going