jcf-review-process
Use when planning around the Journal of Corporate Finance (JCF) review process — single-anonymized (single-blind) refereeing, a minimum of two reviewers, an active desk-rejection policy, decision-letter interpretation, and required Elsevier declarations. It sets expectations and timing strategy; it does not draft the manuscript or the rebuttal.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jcf-review-process --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 o
- When to trigger
- How JCF review works (verified; re-confirm on the official guide)
- Implications for strategy
- Pre-submission checklist
- Desk-rejection patterns at this venue
- Reading the decision letter
- Timing expectations (plan, do not rely)
- Anti-patterns
- Output
What does the jcf-review-process skill do?
Use when planning around the Journal of Corporate Finance (JCF) review process — single-anonymized (single-blind) refereeing, a minimum of two reviewers, an active desk-rejection policy, decision-letter interpretation, and required Elsevier declarations. It sets expectations and timing strategy; it does not draft the manuscript or the rebuttal.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jcf-review-process --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.