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

Jpsp Review Process

ASecurity

Use to understand how a Journal of Personality and Social Psychology (JPSP) manuscript is judged — per-section editors, masked review, the theoretical-innovation gate, central vs. peripheral limitations, and decision categories. Sets expectations; it does not predict any specific editor's or reviewer's verdict.

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

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Jpsp Review Process?

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

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

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

Download with Pro
Files
SKILL.md
---
name: jpsp-review-process
description: Use to understand how a Journal of Personality and Social Psychology (JPSP) manuscript is judged — per-section editors, masked review, the theoretical-innovation gate, central vs. peripheral limitations, and decision categories. Sets expectations; it does not predict any specific editor's or reviewer's verdict.
---

# Review Process — Per Section (jpsp-review-process)

JPSP is reviewed **inside one of three independently edited sections**, by an editor and reviewers
who are **mutually masked** to the authors. Knowing how *your* section frames decisions helps you
anticipate what reviewers will ask. The IRGP section has published an unusually explicit review model
(below); ASC and PPID share the masked, theory-first culture but set their own specifics (verify).

## When to trigger

- Anticipating how the section will evaluate the paper before submitting
- Interpreting a decision letter's framing (innovation, central vs. peripheral limitations)
- Deciding whether a prospective design should be a Registered Report (Stage 1)

## How the section judges a paper

1. **Section routing.** The paper is handled by the editor of the section you submitted to (ASC, IRGP,
   or PPID); a mis-fit paper can be re-routed or returned. Choose the section deliberately
   (`jpsp-topic-selection`).
2. **Triage.** Papers limited in theoretical scope or methodologically deficient may be **triaged
   (desk-screened)** so authors can move on quickly (IRGP guidance; verify per section).
3. **Innovation gate.** Reviewers first judge whether the **underlying ideas** are sufficiently
   innovative/generative — often *independent* of data strength. A "no" focuses the review on why the
   theoretical bar is unmet; a "yes/probably yes" moves to evaluating the studies.
4. **Central vs. peripheral limitations (IRGP).** Reviewers categorize limitations as **central**
   (must be fixed for the studies to be interpretable) or **peripheral** (could be fixed but the work
   is already compelling), and central ones as addressable with **existing** vs. **new** data.
5. **Decision categories (IRGP, verify per section):**
   - **Accept with revision** — may be offered on the **first round** when the paper is sufficiently
     innovative with **no central limitations**.
   - **Revise and resubmit** — central limitations addressable with **existing** studies/data.
   - **Reject** — central limitations require **new** studies/data (a later resubmission with new data
     is treated as a **new** submission).
   Revised manuscripts are often decided **without further reviews**.
6. **Masked review.** Both directions masked — keep identity out of text, files, and repository links.

## Anti-patterns

- Submitting to the wrong section and hoping the editor re-routes favorably
- Leading with method polish when the **idea** has not cleared the innovation gate
- Treating an R&R as acceptance — central limitations still gate the decision
- Resubmitting a rejected paper with brand-new data and expecting continuity (it is a new submission)
- De-anonymizing yourself via self-references or repository URLs

## Output format

```
【Section + editor stream】ASC / IRGP / PPID
【Innovation gate】is the idea a "yes/probably yes"? why
【Likely limitations】central vs peripheral; existing vs new data to fix
【Plausible decision】accept-with-revision / R&R / reject (section-specific)
【Registered Report?】if prospective, Stage 1 considered?
【Next】jpsp-submission (pre-submit) or jpsp-rebuttal (on decision)
```

## Supplementary resources

- [`../../resources/external_tools.md`](../../resources/external_tools.md) — preregistration / Registered Report tooling
- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — IRGP review model, masked-review policy, per-section editors

Attribution

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

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

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

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

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', ...

686011 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 →