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

Jcr Rebuttal

ASecurity

Use when responding to a Journal of Consumer Research (JCR) revise-and-resubmit — planning the revision, running new studies or analyses, satisfying the transparency requirements that become mandatory at invited revision, and drafting a point-by-point response letter for double-anonymized re-review. Drafts the response after the revision is real; it does not interpret the decision (jcr-review-process).

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

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Jcr Rebuttal?

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

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

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

Download with Pro
Files
SKILL.md
---
name: jcr-rebuttal
description: Use when responding to a Journal of Consumer Research (JCR) revise-and-resubmit — planning the revision, running new studies or analyses, satisfying the transparency requirements that become mandatory at invited revision, and drafting a point-by-point response letter for double-anonymized re-review. Drafts the response after the revision is real; it does not interpret the decision (jcr-review-process).
---

# Revision & Rebuttal (jcr-rebuttal)

## When to trigger

- You received a JCR R&R and need a plan plus a response letter
- Reviewers want additional studies, process evidence, or analyses
- You must satisfy data/materials posting now required at invited revision
- You are reconciling conflicting reviewer requests across disciplines

## Revise first, write the letter second

A JCR response letter documents revisions that already exist. Sequence the work:

1. **Triage by the editor's priorities.** The co-editor's letter signals which concerns are decisive — fix those substantively, not cosmetically.
2. **Strengthen the conceptual contribution.** If reviewers found it incremental, sharpen the advance/deepen/repudiate claim (`jcr-contribution-framing`) — re-running studies will not save a thin contribution.
3. **Add the evidence the genre demands.** Experiments: new studies for **process** (manipulated mediator, predicted moderators), replications across stimuli/populations, cleaner inference (`jcr-data-analysis`). CCT: deeper grounding, additional informants, a tighter audit trail.
4. **Reconcile conflicts transparently.** Where reviewers disagree, choose a defensible path, explain the reasoning, and let the editor adjudicate — do not silently split the difference.

## Satisfy the transparency requirements that activate at revision

At **invited revision**, JCR's transparency regime tightens: posting of **data and study materials to an approved repository** (OSF, Harvard Dataverse, Qualitative Data Repository, ResearchBox) becomes **required** (accessible to editors) unless an exemption is granted, and **replication code** must be provided. Update the **Data Collection Statement** to cover any new studies. Confirm your data-retention plan (**≥ 7 years**). Address any transparency reviewer concerns explicitly in the letter.

## Writing the point-by-point response

- **Open** with a brief summary of the major changes and gratitude for the developmental feedback.
- **Address every comment** in order, per reviewer: quote the comment, state what you changed, and point to the manuscript location (page/section, new study number, new exhibit).
- **Show, don't assert.** Reference new results, new figures, and repository links rather than promising compliance.
- **Keep anonymization intact.** The revised manuscript re-enters **double-anonymized** review — re-scrub identifiers, keep self-citations neutral, describe field sites generically.
- **Respect the page cap.** New studies must fit the **60-page** manuscript (embedded exhibits count); push supporting material to the **web appendix (≤ 40 MB)**.

## Checklist

- [ ] Editor's decisive concerns addressed substantively
- [ ] Contribution sharpened if flagged as incremental
- [ ] New process evidence / replications (experiments) or deeper grounding (CCT) added
- [ ] Conflicting reviewer requests reconciled with transparent reasoning
- [ ] Data/materials posted to an approved repository; replication code supplied; Data Collection Statement updated
- [ ] Point-by-point letter quotes each comment and cites manuscript locations
- [ ] Revised manuscript re-anonymized; within 60 pages; overflow in the web appendix

## Anti-patterns

- Promising changes in the letter that the manuscript does not contain.
- Cosmetic edits to decisive concerns.
- Adding studies that bloat the manuscript past the page cap.
- Ignoring transparency requirements that become mandatory at revision.
- Breaking anonymization when describing new data or sites.

## Output format

```
【Editor's priorities】addressed: [...]
【Contribution】sharpened? advance/deepen/repudiate restated
【New evidence】studies/analyses (experiments) or grounding (CCT) added
【Conflicts】reconciled with reasoning
【Transparency】repository deposit + code + updated Data Collection Statement: done?
【Response letter】point-by-point, with locations; re-anonymized; ≤60 pp
【Next step】resubmit via ScholarOne → jcr-review-process
```

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 →