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

ASecurity

Use to understand how the Journal of Communication (JoC) evaluates a manuscript — double-anonymous review, editorial screening for fit, external review by two or three referees, decision categories, and editor discretion. Sets expectations and shapes the paper to survive review; it does not contact editors.

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

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-review-process --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Joc Review Process?

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

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

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

Download with Pro
Files
SKILL.md
---
name: joc-review-process
description: Use to understand how the Journal of Communication (JoC) evaluates a manuscript — double-anonymous review, editorial screening for fit, external review by two or three referees, decision categories, and editor discretion. Sets expectations and shapes the paper to survive review; it does not contact editors.
---

# Review Process (joc-review-process)

Knowing how JoC screens and decides lets you pre-empt the failure modes before submitting. JoC is
**double-anonymous** and screens for fit before sending papers to external reviewers.

## When to trigger

- Before submitting, to stress-test fit and anonymization
- Deciding whether the contribution is significant enough for JoC vs. a more specialized outlet
- Interpreting a decision letter and setting expectations
- Understanding what reviewers are instructed to weigh

## How JoC review works

1. **Double-anonymous.** Reviewers do not know the authors and authors do not know reviewers.
   Anonymize the **main document and supplemental materials**; write self-citations in the third
   person (see `joc-submission`).
2. **Editorial screening first.** Manuscripts judged to fit the interests of JoC are sent out for
   external review; those that do not fit — too narrow, off-scope, or insufficiently significant for a
   field-wide flagship — may be declined without full review.
3. **External review.** Manuscripts that pass are sent to expert referees, **usually two or three**,
   under the double-anonymous model.
4. **Decision categories**: typically **reject**, **revise and resubmit** (major or minor), or
   **accept** — with the final call **at the editor's discretion**, weighing reviewer recommendations.
5. **Timeline.** Authors can generally expect a first decision within roughly **90 days** (treat as
   approximate; see 待核实).

## Open science in review

- A **Data Availability Statement** is expected; **preregistration** (if any) should be noted in the
  cover letter; **Open Science Badge** materials must be deposited to be claimed (see
  `joc-open-science-and-transparency`).

## Shape the paper to pass

- Make general significance explicit (avoids the "too narrow / not significant enough" screen-out).
- Engage the relevant literatures, including across subfields (see `joc-literature-positioning`).
- Clear ethics/IRB and human-subjects compliance up front.
- Write to expert reviewers: anticipate the strongest objection and answer it in the design.

## Anti-patterns

- Submitting a platform-only or single-topic paper to a field-wide flagship (fit screen-out)
- Ignoring an obvious related literature
- Expecting acceptance without revision — most accepted papers go through at least one R&R
- Leaving identifiers in supplemental materials (breaks double-anonymity)

## Output format

```
【Fit check】field-wide significance vs. specialized outlet — any red flags?
【Significance】general enough to clear the editorial screen? [Y/N]
【Literature engaged】incl. cross-subfield? [Y/N]
【Anonymization】main doc + supplements clean? [Y/N]
【Realistic outcome】reject / R&R (major/minor) / (rare) accept
【Next】joc-submission (or joc-rebuttal if decided)
```

## Supplementary resources

- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — double-anonymous review, referee count, decision timeline, editor discretion

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 →