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

Jcf Review Process

ASecurity

Use to understand and plan around the Journal of Corporate Finance (JCF) review process — single-anonymized (single-blind) refereeing, a minimum of two reviewers, an active desk-rejection policy, and required Elsevier declarations. It sets expectations and timing strategy; it does not draft the manuscript or the rebuttal.

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

Installs into .claude/skills of the current project.

Are you the author of Jcf Review Process?

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

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

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

Download with Pro
Files
SKILL.md
---
name: jcf-review-process
description: Use to understand and plan around the Journal of Corporate Finance (JCF) review process — single-anonymized (single-blind) refereeing, a minimum of two reviewers, an active desk-rejection policy, and required Elsevier declarations. It sets expectations and timing strategy; it does not draft the manuscript or the rebuttal.
---

# Review Process (jcf-review-process)

## When to trigger

- Setting expectations for what happens after you submit
- Deciding how to handle the single-anonymized model and required declarations
- Planning for the desk-rejection screen and the reviewer round

## How JCF review works (verified; re-confirm on the official guide)

- **Single anonymized (single-blind) peer review.** Reviewers see the authors' identities; authors do **not** see reviewers. There is **no double-blind anonymization** to perform — do **not** strip your name and affiliation.
- Suitable submissions are sent to a **minimum of two independent reviewers**.
- An **active desk-rejection policy** rejects a non-trivial fraction of papers **without full review** to reduce reviewer burden — the editor screen is real and fast.
- A **competing-interest declaration** is required via Elsevier's declarations tool, and a **generative-AI disclosure** is required at submission.

## Implications for strategy

- Because review is single-anonymized, your reputation and prior work are **visible** — frame self-citations naturally, but do not assume name recognition substitutes for a clean design.
- Clearing the **desk screen** depends on a legible contribution and credible identification on page one (see jcf-contribution-framing, jcf-identification-strategy). Expect scrutiny of whether the paper is truly corporate finance and whether the mechanism is first-order.
- Two reviewers means two independent sets of demands at R&R — anticipate divergent asks (see jcf-rebuttal).

## Pre-submission checklist

- [ ] Manuscript is **not** anonymized (single-blind — author identity expected)
- [ ] Competing-interest declaration and generative-AI disclosure prepared
- [ ] Contribution and identification legible up front (desk-screen ready)
- [ ] US$340 fee ready (paid at submission; see jcf-submission)

## Anti-patterns

- Double-blind anonymizing a single-anonymized submission.
- Assuming a desk decision means a thorough review — it often does not.
- Skipping the required declarations and stalling the submission.

## Output

```
【Model】single-anonymized — author identity shown? [confirmed]
【Declarations】competing-interest + AI disclosure ready? [Y/N]
【Desk-screen】contribution + ID legible up front? [Y/N]
【Reviewers】expect ≥2 independent → plan divergent R&R
```

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 →