A skill your agent uses when drafting the response to an R&R or referee report for a Journal of Financial Markets (JFM) manuscript — turning microstructure objections into a point-by-point response…

MITAuto-check passedResearch & Science

Install Jfm Rebuttal

skills CLI
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jfm-rebuttal -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jfm-rebuttal --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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-rebuttal .claude/skills/jfm-rebuttal && rm -rf skills-src

Use ~/.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/

Facts

Skill name
jfm-rebuttal
GitHub stars
1.2k
Token cost
~2k tokens
SKILL.md length
1,078 words
Files
1
Skills in repo
2,387
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when drafting the response to an R&R or referee report for a Journal of Financial Markets (JFM) manuscript — turning microstructure objections into a point-by-point response…

  • Works in 6 steps: Open with a short summary of the main… → Reproduce every comment verbatim,… → Lead with the fatal-if-true comments the… → …
  • Drafting the response to an R&R
  • SKILL.md covers When to trigger, Structuring the JFM response, Microstructure-specific moves… and Documenting result stability…, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Jfm Rebuttal is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting the response to an R&R or referee report for a Journal of Financial Markets (JFM) manuscript — turning microstructure objections into a point-by-point response and a revised draft. Plans and drafts the rebuttal; it does not invent evidence or citations.

Its SKILL.md is about 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.

When your agent uses it

  • Drafting the response to an R&R
  • Tasks that involve Peer review
  • Tasks that involve Citation management

Example prompts

  • “/jfm-rebuttal”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Open with a short summary of the main changes and the headline result's stability ("the X-bps effect is unchanged after the requested…
  2. Reproduce every comment verbatim, numbered by referee, each followed by a concise response and a pointer to the exact revised location…
  3. Lead with the fatal-if-true comments the editor flagged (from jfm-referee-strategy), then the rest in order.
  4. For new analysis, state what you ran, the result, and whether the headline survives — show the number, not just "we addressed this."
  5. For push-backs, concede the framing, then give the microstructure evidence. "The referee is right to worry about endogeneity; the…
  6. For conflicting referees, name the conflict and ask the editor for guidance rather than silently siding with one.

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

Jfm Rebuttal loads about 2k tokens when it runs. Until then it costs about 71 tokens; SKILL.md has 1,078 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~71
When it runs · the whole SKILL.md, loaded when a task matches
~2k

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). 1,078 words, ~2,034 tokens.

Download SKILL.mdSave it as .claude/skills/jfm-rebuttal/SKILL.md (or your agent's skills folder).
name
jfm-rebuttal
description
Use when drafting the response to an R&R or referee report for a Journal of Financial Markets (JFM) manuscript — turning microstructure objections into a point-by-point response and a revised draft. Plans and drafts the rebuttal; it does not invent evidence or citations.

Rebuttal Strategy (jfm-rebuttal)

When to trigger

  • A JFM decision letter (R&R or reject-and-resubmit) has arrived and a response letter is due
  • The referee asks for new microstructure analysis (alternative measures, a placebo, a subsample) and you must plan it
  • You disagree with a comment and need to push back without antagonizing the referee
  • Comments conflict across referees and the editor must be asked to adjudicate
  • The revision risks ballooning and you need to keep it inside the editor's real decision rule

Structuring the JFM response

The response letter is read by busy specialists; make compliance visible and verifiable. The governing principle: do the work, then make it effortless to see you did it.

  1. Open with a short summary of the main changes and the headline result's stability ("the X-bps effect is unchanged after the requested checks").
  2. Reproduce every comment verbatim, numbered by referee, each followed by a concise response and a pointer to the exact revised location ("new Table 5, p. 14; Internet Appendix Table IA.3").
  3. Lead with the fatal-if-true comments the editor flagged (from jfm-referee-strategy), then the rest in order.
  4. For new analysis, state what you ran, the result, and whether the headline survives — show the number, not just "we addressed this."
  5. For push-backs, concede the framing, then give the microstructure evidence. "The referee is right to worry about endogeneity; the tick-size shock is exogenous to firm fundamentals because …" beats a flat refusal.
  6. For conflicting referees, name the conflict and ask the editor for guidance rather than silently siding with one.

Microstructure-specific moves that win R&Rs

  • Measurement-artifact comment → add the alternative liquidity/impact construct and show the effect holds; this is the single most common JFM ask.
  • Endogeneity comment → strengthen the design (find/justify the exogenous market-structure variation) rather than adding controls.
  • Inference comment → re-report with two-way clustering / NW and state it; usually cheap and fully closes the point.
  • "Not microstructure enough" → sharpen the mechanism framing and add the heterogeneity exhibit showing the effect where the trading-process theory predicts.
  • Generalizability → add an asset class / venue / period, or scope the claim honestly; do not over-promise.

Documenting result stability across the revision

Because most JFM revisions add measurement and inference checks, the headline number often shifts slightly. Get ahead of this: maintain a small table (for yourself, and summarized in the letter) showing the headline coefficient under the original and each newly requested specification, so the reader sees the result is stable rather than wondering why a number changed between rounds. If a check does move the estimate materially, explain why in microstructure terms rather than burying it — a transparent "the effect attenuates to X bps once we use realized spreads, consistent with [reason]" is far stronger than a silent change a referee notices.

Worked response entry (illustrative)

Referee 2, Comment 3: "The spread effect may simply reflect the alternative liquidity measure chosen."

Response: We thank the referee for raising this. We now re-estimate the main result using quoted, effective, and realized spreads and the Amihud measure (new Table 4, columns 2-5; full battery in Internet Appendix Table IA.3). The effect ranges from 9 to 14 bps across all four constructs and remains significant at the 1% level, so it is not an artifact of any single measure. We added a sentence to Section 4.2 (p. 15) noting this.

This entry reproduces the comment, names the new analysis, gives the actual numbers and their stability, and points to exact locations. It does not say "we addressed this" — it shows it.

Sequencing and tone

Order the letter to mirror the editor's priorities: fatal/editor-flagged comments first, then referee-by-referee. Open each referee's section by thanking them and summarizing the changes their report produced. For a genuine disagreement, never refuse flatly — concede the concern's legitimacy, then present the microstructure evidence that resolves it; if it cannot be resolved, scope the claim honestly. When two referees pull in opposite directions, state both positions and ask the editor for direction rather than silently complying with one and ignoring the other. The revised manuscript and Internet Appendix must say exactly what the letter claims they say — an editor will spot-check.

Show full SKILL.md (392 more words)Show less

Checklist

  • Every referee comment reproduced and answered, numbered, with a location pointer
  • Editor-flagged / fatal comments addressed first and most thoroughly
  • New analyses report the actual result and whether the headline survives
  • Measurement-artifact ask answered with an alternative construct
  • Endogeneity ask answered by design, not by adding controls
  • Push-backs concede the concern, then rebut with microstructure evidence
  • Conflicting comments escalated to the editor, not silently resolved
  • Revised draft and Internet Appendix updated consistently with the letter

Handling the comment you cannot fully satisfy

Some asks cannot be met — the data to run the requested test do not exist, or a requested redesign would not be identified. Do not ignore these and hope, and do not pretend to comply with a token gesture. State plainly what you tried, why the ideal version is infeasible, and the best available alternative you ran instead, with its result. "We cannot obtain order-level data for this venue; as the closest feasible test we use consolidated TAQ depth, which shows the same pattern (new IA.5)." Microstructure referees respect a candid constraint far more than a hollow "addressed." If the comment reflects a genuine limitation of the design, acknowledge it as a scope condition in the paper rather than overselling around it — this both answers the referee and pre-empts the same objection in any future round.

Anti-patterns

  • "We have addressed this" with no location pointer or number
  • Adding controls when the referee asked for identification
  • Arguing down a measurement-artifact concern instead of running the alternative measure
  • Defensive or dismissive tone toward a specialist referee
  • Silently picking one referee's view when two conflict
  • A response letter whose claims the revised draft does not actually support

Managing scope so the revision converges

R&Rs balloon when authors treat every comment as equal and add analysis without removing anything. Keep the revision converging: anchor on the editor's essential comments, do exactly the work those require, and resist gold-plating the minor ones beyond a sentence and an appendix table. When a referee's suggestion would push the paper away from its microstructure core (e.g., "add a corporate-governance angle"), politely note that it lies outside the paper's market-mechanism focus rather than diluting the contribution to comply. Track a one-line status per comment (done / added exhibit / pushed back / escalated) so nothing is silently dropped — an unaddressed comment is the fastest way to lose a second round.

Output format

text
【Journal】Journal of Financial Markets (JFM)
【Skill】jfm-rebuttal
【Summary line】headline result stability after revisions
【Comment ledger】each comment → response → location pointer? [Y/N]
【Fatal first】editor-flagged comments addressed first? [Y/N]
【New analysis】results stated with numbers, headline survives? [Y/N]
【Push-backs】concede-then-rebut with evidence? [Y/N]
【Conflicts】escalated to editor where referees disagree? [Y/N]
【Next step】resubmit via Editorial Manager (re-run jfm-submission preflight)

© 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-Financial-Markets-Skills/skills/jfm-rebuttal of brycewang-stanford/Awesome-Journal-Skills.

Open the folder on GitHubat commit 932eb23

Compare with similar skills

Jfm Rebuttal 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.

Jfm Rebuttal compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Jfm Rebuttal this skillbrycewang-stanford/Awesome-Journal-Skills1.2k—~2kAutomated safety check: PassMIT
Academic Paper Writing PipelineImbad0202/academic-research-skills51k—~16kAutomated safety check: PassCustom licence
Peer ReviewK-Dense-AI/claude-scientific-writer2.4k2 repos~3.1kAutomated safety check: NotesMIT
Academic Research Suite for CodexImbad0202/academic-research-skills-codex12k—~12kAutomated safety check: PassCustom licence
Social Science Paper Writingfakerqwq/social-science-paper-writing-skill382—~7kAutomated safety check: PassNone
Review Papermaxwell2732/paper-replicate-agent-demo1372 repos~1.1kAutomated safety check: PassNone

Similar skills

  • 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.

    51k GitHub stars~16k tokensUpdated yesterday
    Research & ScienceAuto-check passed
  • Peer Review

    K-Dense-AI/claude-scientific-writer

    Prepare evidence-bounded, constructive peer-review drafts and structured manuscript assessments.

    2.4k GitHub starsUsed in 2 repos~3.1k tokens
    Research & ScienceAuto-check: notes
  • Academic Research Suite for Codex

    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.

    12k GitHub stars~12k tokensUpdated 7 days ago
    Research & ScienceAuto-check passed
  • Social Science Paper Writing

    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.

    382 GitHub stars~7k tokensUpdated 4 mo ago
    Research & ScienceAuto-check passed
  • Review Paper

    maxwell2732/paper-replicate-agent-demo

    Comprehensive manuscript review covering argument structure, econometric specification, citation completeness, and potential referee objections

    137 GitHub starsUsed in 2 repos~1.1k tokens
    Research & ScienceAuto-check passed
  • 00 Academic Router

    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…

    871 GitHub stars~976 tokensUpdated 1 mo ago
    Research & ScienceAuto-check passed

More from brycewang-stanford/Awesome-Journal-Skills

All 2,387 skills in this repo
  • Aaag 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…

    1.2k GitHub stars~1.3k tokensUpdated 14 days ago
    Auto-check passed
  • 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…

    1.2k GitHub stars~1.3k tokensUpdated 14 days ago
    Auto-check passed
  • 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…

    1.2k GitHub stars~1.4k tokensUpdated 14 days ago
    Auto-check passed
  • 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…

    1.2k GitHub stars~1.4k tokensUpdated 14 days ago
    Auto-check passed
  • 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…

    1.2k GitHub stars~1.3k tokensUpdated 14 days ago
    Auto-check passed
  • 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…

    1.2k GitHub stars~1.6k tokensUpdated 14 days ago
    Auto-check passed

Questions about Jfm Rebuttal

What does Jfm Rebuttal do?

A skill your agent uses when drafting the response to an R&R or referee report for a Journal of Financial Markets (JFM) manuscript — turning microstructure objections into a point-by-point response…. Jfm Rebuttal is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting the response to an R&R or referee report for a Journal of Financial Markets (JFM) manuscript — turning microstructure objections into a point-by-point response and a revised draft.

When should I use Jfm Rebuttal?

Jfm Rebuttal fits situations like: drafting the response to an R&R; tasks that involve Peer review; tasks that involve Citation management.

How do I install Jfm Rebuttal in Claude Code?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jfm-rebuttal -a claude-code`. Or copy the skill folder (Journal-of-Financial-Markets-Skills/skills/jfm-rebuttal in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/jfm-rebuttal in your project. Claude Code loads it when a task matches its description.

How do I install Jfm Rebuttal in Codex?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jfm-rebuttal -a codex`. Or copy the skill folder (Journal-of-Financial-Markets-Skills/skills/jfm-rebuttal in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/jfm-rebuttal in your project. Codex loads it when a task matches its description.

Can I use Jfm Rebuttal 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 jfm-rebuttal -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-rebuttal, .gemini/skills/jfm-rebuttal, .github/skills/jfm-rebuttal and .opencode/skills/jfm-rebuttal in your project.

What does Jfm Rebuttal need to run?

SKILL.md names no scripts, command-line tools or credentials: Jfm Rebuttal is instructions for the agent only.

Does Jfm Rebuttal 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 Jfm Rebuttal 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 Jfm Rebuttal use?

Jfm Rebuttal 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 Jfm Rebuttal use?

About 2k tokens (SKILL.md is roughly 8.1k 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 Jfm Rebuttal?

Skills that share tags, products or a category with Jfm Rebuttal: 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.

Who maintains Jfm Rebuttal?

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.