Academic Paper Writing Pipeline
Imbad0202/academic-research-skills
Runs a 12-agent pipeline that plans, drafts, cites, reviews and formats academic papers, with modes for revision, rebuttals, abstracts and citation checks.
A skill your agent uses when anticipating the microstructure referee's objections for a Journal of Financial Markets (JFM) manuscript — a pre-submission pre-mortem and, post-decision, a triage of…
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jfm-referee-strategy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jfm-referee-strategy --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-Financial-Markets-Skills/skills/jfm-referee-strategy .claude/skills/jfm-referee-strategy && 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 "jfm-referee-strategy" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Financial-Markets-Skills/skills/jfm-referee-strategy into .claude/skills/jfm-referee-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jfm-referee-strategy", 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-Financial-Markets-Skills/skills/jfm-referee-strategyType 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 jfm-referee-strategy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jfm-referee-strategy --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-Financial-Markets-Skills/skills/jfm-referee-strategy .agents/skills/jfm-referee-strategy && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "jfm-referee-strategy" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Financial-Markets-Skills/skills/jfm-referee-strategy into .agents/skills/jfm-referee-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jfm-referee-strategy", 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 jfm-referee-strategy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jfm-referee-strategy --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-Financial-Markets-Skills/skills/jfm-referee-strategy .cursor/skills/jfm-referee-strategy && 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 "jfm-referee-strategy" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Financial-Markets-Skills/skills/jfm-referee-strategy into .cursor/skills/jfm-referee-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jfm-referee-strategy", 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-Financial-Markets-Skills/skills/jfm-referee-strategy--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 jfm-referee-strategy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jfm-referee-strategy --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-Financial-Markets-Skills/skills/jfm-referee-strategy .gemini/skills/jfm-referee-strategy && 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 "jfm-referee-strategy" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Financial-Markets-Skills/skills/jfm-referee-strategy into .gemini/skills/jfm-referee-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jfm-referee-strategy", 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 jfm-referee-strategyInstalls 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 jfm-referee-strategy -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-Financial-Markets-Skills/skills/jfm-referee-strategy .github/skills/jfm-referee-strategy && 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 "jfm-referee-strategy" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Financial-Markets-Skills/skills/jfm-referee-strategy into .github/skills/jfm-referee-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jfm-referee-strategy", 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 jfm-referee-strategy -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 jfm-referee-strategy --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-Financial-Markets-Skills/skills/jfm-referee-strategy .opencode/skills/jfm-referee-strategy && 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 "jfm-referee-strategy" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Financial-Markets-Skills/skills/jfm-referee-strategy into .opencode/skills/jfm-referee-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jfm-referee-strategy", 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.
jfm-referee-strategyA skill your agent uses when anticipating the microstructure referee's objections for a Journal of Financial Markets (JFM) manuscript — a pre-submission pre-mortem and, post-decision, a triage of…
Jfm Referee Strategy is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when anticipating the microstructure referee's objections for a Journal of Financial Markets (JFM) manuscript — a pre-submission pre-mortem and, post-decision, a triage of the report. Anticipates and triages; it does not invent evidence or citations.
Its SKILL.md is about 2.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, covering Peer review and Citation management. 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.
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Jfm Referee Strategy loads about 2.2k tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 1,114 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.
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.
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 1,114 words, ~2,184 tokens.
.claude/skills/jfm-referee-strategy/SKILL.md (or your agent's skills folder).A JFM referee is a microstructure specialist. The predictable lines of attack cluster, and most live in measurement and identification, not novelty.
| Referee line | What they really doubt | Pre-empt with |
|---|---|---|
| "This is not really microstructure" | the mechanism is broad finance | jfm-topic-selection framing; lead with the trading-process object |
| "The result is driven by the liquidity measure" | measurement artifact | jfm-empirical-design + alternative constructs in jfm-robustness |
| "Liquidity is endogenous here" | reverse causality / confounding | jfm-identification: a market-structure shock or defensible IV |
| "Your event window / filters are arbitrary" | researcher-degrees-of-freedom | justify window from mechanics; document every filter |
| "Standard errors overstate precision" | un-clustered panel inference | two-way clustering / NW; state it in table notes |
| "Incremental to [known paper]" | contribution undersold | jfm-literature-positioning: explicit they/we gap |
| "PIN/structural estimates are fragile" | numerical instability | report solver settings, multistart, sensitivity |
Pre-submission pre-mortem. For each row above that could apply, write the strongest version of the objection and the exhibit/argument that answers it. If an answer requires analysis you have not run, run it now — it is cheaper than an R&R cycle. The output is a list of latent weaknesses, each with a planned defense.
Post-decision triage. Sort every comment into: (1) fatal-if-true — goes to the top of the response and gets the most work; (2) fixable — new analysis or exposition; (3) defensible — politely push back with evidence; (4) editor-flagged — the editor signaled priority, so it is effectively (1). Read the editor's letter for the real decision rule: which comments must be resolved for acceptance. Then hand the sorted list to jfm-rebuttal.
Run the pre-mortem twice. The first pass is before submission, while there is still time to run the analysis that closes a foreseeable objection — this is its highest value, since adding an alternative-measure column now costs days, whereas discovering the gap in an R&R costs months. The second pass is on receiving the report, to triage the actual comments against your anticipated list: comments you predicted are already half-answered, and genuinely new ones tell you where your model of the field was incomplete. Skipping the pre-submission pass is the most expensive economy in the whole process.
A paper claims a new dark-pool venue worsened lit-market liquidity. The pre-mortem surfaces: (1) "It's just the measure" — the result holds only for quoted spread → run effective and realized before submitting; (2) "Endogenous venue choice" — flow self-selects into the dark pool → exploit the staggered venue launch and cluster by stock; (3) "Time-of-day" — dark trading concentrates midday → add intraday-bin fixed effects; (4) "Incremental to known fragmentation work" — name the closest 3 papers and the gap. Each is answered with a concrete exhibit before the editor ever sees the paper. The output is a short table of latent weakness → planned defense → exhibit number, which doubles as the skeleton of the eventual response letter.
The editor's letter, not the referee reports, encodes the real decision rule. Look for: which comments the editor calls "essential" or "must address"; whether the tone is "revise" (fixable) or "we would consider a substantially revised paper" (closer to reject); and whether referees conflict (your cue to ask the editor to adjudicate rather than guess). An R&R that asks only for measurement and inference checks is far more tractable than one questioning the core identification — calibrate the effort and the timeline accordingly, and be honest with coauthors about which it is.
JFM submissions typically draw a microstructure specialist and, sometimes, a broader-finance reader. Plan for both. The specialist scrutinizes measurement, institutional accuracy, and the mechanism — answer them with construction detail, alternative measures, and a heterogeneity test. The generalist asks why the result matters beyond the plumbing — answer them with a clear economic-magnitude statement and a sentence on the broader implication for market quality. A paper written only for the specialist can read as narrow to the generalist; one written only for the generalist loses the specialist's trust. The intro and abstract should satisfy both in their first paragraphs.
Anticipating objections is defensive; the strongest submissions also give the referee reasons to advocate. A microstructure specialist becomes a champion when the paper (1) gets the institutional detail exactly right — they trust authors who clearly know the market's plumbing; (2) offers a clean identifying shock they had not thought to exploit; (3) introduces a measure or decomposition they will want to use themselves; (4) shows the effect where the theory predicts, demonstrating command of the mechanism. Build at least one of these into the paper deliberately, and surface it in the intro and cover letter. A pre-mortem that only patches weaknesses produces a defensible paper; adding an advocacy hook produces an accepted one.
Not every revise request is equally winnable. Sort the editor's asks by the cost and risk of the work they demand. Tractable R&Rs ask for alternative liquidity measures, better clustering, more robustness, sharper exposition, or an added subsample — all additive, none threatening the core. Hard but doable R&Rs ask for a heterogeneity test of the mechanism or a new data source for generalizability. Near-reject R&Rs question the identification itself ("we are not convinced liquidity is exogenous here") — these require a redesign, not a patch, and you should decide honestly whether you can deliver one before sinking months into a revision. Tell coauthors which bucket the letter is in; mis-reading a near-reject as a tractable R&R wastes a cycle.
【Journal】Journal of Financial Markets (JFM)
【Skill】jfm-referee-strategy
【Mode】pre-mortem / post-decision triage
【Top objection】<microstructure line> → planned answer
【Measurement defense】alternative constructs ready? [Y/N]
【Endogeneity defense】shock/IV ready? [Y/N]
【Triage (if report)】fatal / fixable / defensible / editor-flagged counts
【Editor signal】what must be resolved for acceptance
【Next skill】jfm-rebuttal© 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
Just SKILL.md in Journal-of-Financial-Markets-Skills/skills/jfm-referee-strategy of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Jfm Referee Strategy 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 |
|---|---|---|---|---|---|---|
| Jfm Referee Strategy this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~2.2k | Automated safety check: Pass | MIT | |
| Academic Paper Writing PipelineImbad0202/academic-research-skills | 51k | — | ~16k | Automated safety check: Pass | Custom licence | |
| Peer ReviewK-Dense-AI/claude-scientific-writer | 2.4k | 2 repos | ~3.1k | Automated safety check: Notes | MIT | |
| Academic Research Suite for CodexImbad0202/academic-research-skills-codex | 12k | — | ~12k | Automated safety check: Pass | Custom licence | |
| Social Science Paper Writingfakerqwq/social-science-paper-writing-skill | 382 | — | ~7k | Automated safety check: Pass | None | |
| Review Papermaxwell2732/paper-replicate-agent-demo | 137 | 2 repos | ~1.1k | Automated safety check: Pass | None |
Imbad0202/academic-research-skills
Runs a 12-agent pipeline that plans, drafts, cites, reviews and formats academic papers, with modes for revision, rebuttals, abstracts and citation checks.
K-Dense-AI/claude-scientific-writer
Prepare evidence-bounded, constructive peer-review drafts and structured manuscript assessments.
Imbad0202/academic-research-skills-codex
A router skill that sends academic work such as literature reviews, drafting, citation checks, peer review and revision to the right workflow in the ARS suite.
fakerqwq/social-science-paper-writing-skill
Helps draft, diagnose, review and revise social science papers, from topic and research question to literature review, citation risks and pre-submission checks.
maxwell2732/paper-replicate-agent-demo
Comprehensive manuscript review covering argument structure, econometric specification, citation completeness, and potential referee objections
agentscope-ai/OpenJudge
A skill your agent uses when the user wants help with academic papers or citations but it's unclear which specific workflow fits — reviewing a paper, checking a BibTeX file for fake references, or…
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…
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…
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…
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…
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…
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…
Categories
A skill your agent uses when anticipating the microstructure referee's objections for a Journal of Financial Markets (JFM) manuscript — a pre-submission pre-mortem and, post-decision, a triage of…. Jfm Referee Strategy is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when anticipating the microstructure referee's objections for a Journal of Financial Markets (JFM) manuscript — a pre-submission pre-mortem and, post-decision, a triage of the report.
Jfm Referee Strategy fits situations like: anticipating the microstructure referees objections for a Journal of Financial Markets (JFM) manuscript — a pre-submission pre-mortem and; A triage of the report.
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jfm-referee-strategy -a claude-code`. Or copy the skill folder (Journal-of-Financial-Markets-Skills/skills/jfm-referee-strategy in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/jfm-referee-strategy in your project. Claude Code loads it when a task matches its description.
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jfm-referee-strategy -a codex`. Or copy the skill folder (Journal-of-Financial-Markets-Skills/skills/jfm-referee-strategy in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/jfm-referee-strategy in your project. Codex loads it when a task matches its description.
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 jfm-referee-strategy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/jfm-referee-strategy, .gemini/skills/jfm-referee-strategy, .github/skills/jfm-referee-strategy and .opencode/skills/jfm-referee-strategy in your project.
SKILL.md names no scripts, command-line tools or credentials: Jfm Referee Strategy is instructions for the agent only.
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.
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.
Jfm Referee Strategy is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.2k tokens (SKILL.md is roughly 8.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Jfm Referee Strategy: Academic Paper Writing Pipeline (Imbad0202/academic-research-skills, 51k stars), Peer Review (K-Dense-AI/claude-scientific-writer, 2.4k stars), Academic Research Suite for Codex (Imbad0202/academic-research-skills-codex, 12k stars) and Social Science Paper Writing (fakerqwq/social-science-paper-writing-skill, 382 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
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.