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 Review Process

ASecurity

Use when understanding how Journal of Consumer Research (JCR) review and decisions work — double-anonymized review, the co-editor/AE/reviewer structure, decision letters, and what reviewers from different disciplines expect — before submitting or when a decision arrives. Sets expectations; the actual response is drafted in jcr-rebuttal.

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

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Jcr Review Process?

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

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

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

Download with Pro
Files
SKILL.md
---
name: jcr-review-process
description: Use when understanding how Journal of Consumer Research (JCR) review and decisions work — double-anonymized review, the co-editor/AE/reviewer structure, decision letters, and what reviewers from different disciplines expect — before submitting or when a decision arrives. Sets expectations; the actual response is drafted in jcr-rebuttal.
---

# Review Process (jcr-review-process)

## When to trigger

- You want to know what to expect after submitting to JCR
- A decision letter arrived and you need to read it before responding
- You are unsure who handles the manuscript and what each reviewer weighs
- You want to calibrate to JCR's developmental, multi-round culture

## How JCR review is organized

JCR uses **double-anonymized** (masked) peer review: reviewers do not see author identity and authors do not see reviewers'. Editorially, the journal is led by an **Editor in Chief** (Oleg Urminsky, Chicago Booth, term Jan 1, 2025 – Dec 31, 2028) with **Co-Editors** who handle full manuscript portfolios, **Associate Editors**, an **Editorial Review Board**, and ad hoc reviewers. The active co-editor roster is time-sensitive — **待核实**; confirm the current masthead at consumerresearcher.com. The precise desk-assignment/routing mechanism is **待核实** (the official pages do not describe a fixed departmental area-editor routing); in practice a co-editor takes the manuscript and assigns reviewers.

JCR's identity as a **multi-disciplinary** journal shapes the review: you may draw reviewers from psychology, anthropology, sociology, economics, marketing, or statistics, and an experimental paper and a CCT paper are held to **the same conceptual bar** — advancing, deepening, or repudiating theory about consumption — even though their evidentiary standards differ.

## What reviewers weigh

- **Conceptual contribution first.** Reviewers ask "what do we now understand about consumers?" as insistently as "is the evidence sound?" A robust effect with no theory advance will not clear the bar.
- **Evidence appropriate to the genre.** Experimentalists probe process evidence (mediation, manipulated mediators, boundary conditions, clean inference); interpretive reviewers probe trustworthiness, immersion, and the grounding of conceptual claims.
- **Research transparency.** Expect scrutiny of the **Data Collection Statement**, data/materials availability, replication code, and reporting completeness, especially at revision.
- **Interdisciplinary legibility.** A reviewer outside your subfield must be able to follow the argument.

## Reading the decision letter

- **Reject / desk reject:** usually a fit or contribution problem — return to `jcr-topic-selection` / `jcr-contribution-framing`.
- **Revise & resubmit (R&R):** developmental; the editor's letter prioritizes which concerns are decisive. First-round accepts are essentially unheard of — an R&R is a strong signal.
- Map each reviewer point to a stage (theory / methods / analysis / framing / exhibits) and to the relevant jcr-* skill before drafting a response.
- Note any **transparency conditions** (post data/materials, supply code) that become required at invited revision.

## Expectations & norms

- The process is **developmental and multi-round**; plan for substantial revision cycles.
- Treat the editor's framing as the spine of your revision priorities; reconcile conflicting reviewer requests transparently rather than averaging them.
- Re-anonymize the revised manuscript; double-anonymized review continues across rounds.

## Anti-patterns

- Reading reviews as a checklist while ignoring the editor's priorities.
- Assuming the contribution is accepted because the method passed.
- Underestimating the number of revision rounds.
- Deferring transparency compliance until after acceptance.

## Output format

```
【Decision type】reject / desk reject / R&R
【Editor's priorities】the decisive concerns, in order
【Reviewer map】each point → stage → jcr-* skill
【Genre standard】experimental process evidence / CCT trustworthiness
【Transparency conditions】data/materials/code required at revision?
【Next step】jcr-rebuttal (if R&R) or re-scope (if reject)
```

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 →