Hypothesis Generation
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
A skill your agent uses 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…
Install Jcf Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jcf-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jcf-review-process --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/Journal-of-Corporate-Finance-Skills/skills/jcf-review-process .claude/skills/jcf-review-process && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "jcf-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Corporate-Finance-Skills/skills/jcf-review-process into .claude/skills/jcf-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jcf-review-process", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Corporate-Finance-Skills/skills/jcf-review-processType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jcf-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jcf-review-process --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/Journal-of-Corporate-Finance-Skills/skills/jcf-review-process .agents/skills/jcf-review-process && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "jcf-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Corporate-Finance-Skills/skills/jcf-review-process into .agents/skills/jcf-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jcf-review-process", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jcf-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jcf-review-process --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/Journal-of-Corporate-Finance-Skills/skills/jcf-review-process .cursor/skills/jcf-review-process && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "jcf-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Corporate-Finance-Skills/skills/jcf-review-process into .cursor/skills/jcf-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jcf-review-process", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path Journal-of-Corporate-Finance-Skills/skills/jcf-review-process--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jcf-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jcf-review-process --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/Journal-of-Corporate-Finance-Skills/skills/jcf-review-process .gemini/skills/jcf-review-process && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "jcf-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Corporate-Finance-Skills/skills/jcf-review-process into .gemini/skills/jcf-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jcf-review-process", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jcf-review-processInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jcf-review-process -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/Journal-of-Corporate-Finance-Skills/skills/jcf-review-process .github/skills/jcf-review-process && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "jcf-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Corporate-Finance-Skills/skills/jcf-review-process into .github/skills/jcf-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jcf-review-process", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jcf-review-process -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jcf-review-process --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/Journal-of-Corporate-Finance-Skills/skills/jcf-review-process .opencode/skills/jcf-review-process && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "jcf-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Corporate-Finance-Skills/skills/jcf-review-process into .opencode/skills/jcf-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jcf-review-process", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
jcf-review-process- GitHub stars
- 1.2k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 495 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses 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…
- Planning around the Journal of Corporate Finance (JCF) review process — single-anonymized (single-blind) refereeing
- SKILL.md covers When to trigger, How JCF review works…, Implications for strategy and Pre-submission checklist, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- A minimum of two reviewers
What it does
Jcf Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Research & Science. The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- 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
Example prompts
- “/jcf-review-process”
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Jcf Review Process loads about 1.2k tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 495 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 495 words, ~1,249 tokens.
Download SKILL.mdSave it as
.claude/skills/jcf-review-process/SKILL.md (or your agent's skills folder).- name
- jcf-review-process
- description
- 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.
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)
Desk-rejection patterns at this venue
The active desk screen filters predictable failure modes. Audit against each:
Pattern | Why the JCF desk stops it
No firm decision at the center | Reads as an asset-pricing / macro / accounting misroute
OLS-with-controls on an endogenous choice | Identification bar unmet for empirical corporate finance
Contribution invisible on page one | The editor screens fast; buried novelty is no novelty
Stale question, no new wedge | A larger sample alone does not move a conversation
Mechanical replication on a new country | Needs institutional variation doing real work
Scope mismatch with the JCF remit | Even good papers get routed elsewhereA desk rejection here is a routing-and-legibility verdict, not a referee report — fix framing or venue choice, not necessarily the analysis.
Show full SKILL.md (225 more words)Show less
Reading the decision letter
- Desk reject with a scope sentence → re-aim the venue; the analysis was likely never evaluated.
- Desk reject citing identification → the design is visibly below the bar; rebuild before resubmitting anywhere comparable.
- R&R where the editor names two or three priorities → those outrank every reviewer point; structure the revision around them.
- Reviewer reports of very different depth → the editor weighs the thorough one; do not over-invest in the cursory report's minor points.
- "Major revision" demanding a redesign → decide early whether the redesigned paper is still your paper; a scope reply (see jcf-rebuttal) beats a grudging redesign.
Timing expectations (plan, do not rely)
Elsevier publishes journal-level speed metrics on the JCF homepage; they vary year to year, so confirm against the journal's current author guidelines rather than hallway numbers. Planning heuristics: budget for the desk screen to resolve quickly relative to full review; assume a complete round with two-plus reviewers takes meaningfully longer; never hang a hard deadline (job market, tenure file) on a single round resolving fast. The US$340 fee is sunk per submission — a premature submission that draws an avoidable desk rejection costs both the fee and the cleanest first impression at this venue.
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© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in Journal-of-Corporate-Finance-Skills/skills/jcf-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Jcf Review Process next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Jcf Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Hypothesis Generationspacering-net/codeg | 3.9k | 14 repos | ~3.6k | Automated safety check: Notes | MIT | |
| GitHub Deep Researchbytedance/deer-flow | 84k | 4 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Nature Paper CardYuan1z0825/nature-skills | 47k | 2 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Content Research Writerweapp-tailwindcss/weapp-tailwindcss | 1.9k | 25 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Last30daysmvanhorn/last30days-skill | 64k | — | ~7.9k | Automated safety check: Notes | MIT |
Similar skills
GitHub Deep Research
bytedance/deer-flow
Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.
Nature Paper Card
Yuan1z0825/nature-skills
Builds a structured deep-reading card for one scientific paper, covering methods, how experiments support claims, limitations and research ideas, with a script to prepare the source.
Content Research Writer
weapp-tailwindcss/weapp-tailwindcss
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section.
Last30days
mvanhorn/last30days-skill
Research what people actually say about any topic in the last 30 days.
Peer Review
spacering-net/codeg
Structured manuscript/grant review with checklist-based evaluation.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Related
Categories
Questions about Jcf Review Process
What does Jcf Review Process do?
A skill your agent uses 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…. Jcf Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
When should I use Jcf Review Process?
Jcf Review Process fits situations like: 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.
How do I install Jcf Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jcf-review-process -a claude-code`. Or copy the skill folder (Journal-of-Corporate-Finance-Skills/skills/jcf-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/jcf-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Jcf Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jcf-review-process -a codex`. Or copy the skill folder (Journal-of-Corporate-Finance-Skills/skills/jcf-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/jcf-review-process in your project. Codex loads it when a task matches its description.
Can I use Jcf Review Process in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jcf-review-process -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/jcf-review-process, .gemini/skills/jcf-review-process, .github/skills/jcf-review-process and .opencode/skills/jcf-review-process in your project.
What does Jcf Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Jcf Review Process is instructions for the agent only.
Does Jcf Review Process access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Jcf Review Process safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Jcf Review Process use?
Jcf Review Process is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Jcf Review Process use?
About 1.2k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Jcf Review Process?
Skills that share tags, products or a category with Jcf Review Process: Hypothesis Generation (spacering-net/codeg, 3.9k stars), GitHub Deep Research (bytedance/deer-flow, 84k stars), Nature Paper Card (Yuan1z0825/nature-skills, 47k stars) and Content Research Writer (weapp-tailwindcss/weapp-tailwindcss, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Jcf Review Process?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.