Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Joc Rebuttal

ASecurity

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.

1,052 stars
0 votes
0 copies
0 views
Added 6/5/2026
ai-agentsrustgo

Works with

cli

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill joc-rebuttal --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Joc Rebuttal?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Joc Rebuttal
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-joc-rebuttal/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-joc-rebuttal)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: joc-rebuttal
description: 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.
---

# 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,
richer interpretive warrant, sharper theoretical/critical stakes, or stronger validation and code.
A demand that looks unreasonable usually makes sense once you name the paradigm behind it. The
Editor-in-Chief's letter tells you which demands are **load-bearing** vs. optional.

## Step 2 — Decide each comment with the page budget in view

Every comment resolves to one of four moves, and three of them cost pages:

| Move | When | Page-budget effect |
|------|------|--------------------|
| **Do in main text** | load-bearing; the editor flagged it | costs pages — find offsets |
| **Do in supplement** | adds rigor but not the core argument | frees main-text pages (DAS/Appendix) |
| **Reframe, don't add** | the concern is about framing, not missing analysis | cheap; often the best move |
| **Decline, with a reason** | the request breaks the paper or comes from a paradigm the paper isn't written in | costs nothing; must be argued, not dodged |

When you add, **say what you cut or moved** to stay under 35 pages — reviewers and the editor see the
tradeoff and trust it more than a paper that silently bloats.

## Step 3 — Broker the cross-paradigm conflicts in the open

When a quantitative reviewer and an interpretive/critical reviewer pull opposite ways, do **not**
quietly side with one. State the tension, choose a principled path that keeps the paper coherent in
**its own** paradigm, and explain to the editor why that path serves the contribution. A paper that
tries to be all paradigms at once usually loses its argument; defend what the study *is*.

## Step 4 — Keep the revision submittable

- **Double-anonymous integrity**: the revised main document **and supplements** stay de-identified;
  keep self-citations in the **third person**.
- **Transparency**: update the **Data Availability Statement** and any **Open Science Badge** claims so
  new analyses, data, or materials are covered (see `joc-open-science-and-transparency`).
- **Format**: still **APA 7th**, .docx, within ~35 pages; the JoC Forum reply path is for shorter
  exchanges, not full R&Rs.

## Response memo structure (per reviewer, then a global note)

Lead with a short note to the editor: the 2–3 changes that matter most, and how you kept the paper
under the page cap. Then, per reviewer, a compact entry:

```
R# (paradigm: post-positivist / interpretive / critical / computational)
• Comment → [paraphrase]
  Action: did-in-text / did-in-supplement / reframed / declined(reason)
  Where: §/p./Table/Fig./Supplement S#   |  Pages: +/- vs. prior draft
```

## Anti-patterns

- Treating a different-paradigm comment as "wrong" instead of naming the stance and answering it on its terms
- Quietly satisfying one reviewer while ignoring a conflicting one
- Adding analyses until the paper busts the 35-page cap, with no statement of what moved
- Letting the Data Availability Statement / badges fall out of sync with the new analyses
- Re-identifying the authors in the revised file or supplements (breaks double-anonymity)
- Diluting the paper's own paradigm to look agreeable to every reviewer

## Output format

```
【Reviewer paradigm map】R1/R2/R3 → stance + what "convincing" means to each
【Editor's load-bearing points】listed and solved first?
【Per-comment moves】in-text / supplement / reframe / decline — each with location
【Page budget】revised length ≤ ~35 pp; what was cut or moved to supplement
【Cross-paradigm conflicts】brokered in the open, paper's paradigm protected? [Y/N]
【Anonymity + DAS/badges】third-person self-cites + transparency updated? [Y/N]
【Next】resubmit via Manuscript Central
```

## Supplementary resources

- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — review model, referee recommendations, page limit, and transparency policy

Attribution

brycewang-stanfordbrycewang-stanford
View sourceMore from brycewang-stanford →
SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1066601 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

693161 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

651 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →