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

Jfi Rebuttal

ASecurity

Use to plan an R&R response letter for the Journal of Financial Intermediation — single-blind review where referees know you, often a small number of expert reports, and an editor whose decision is final. It structures the response; it does not fabricate results.

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 jfi-rebuttal --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Jfi Rebuttal?

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

Security grade badge for Jfi Rebuttal
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-jfi-rebuttal/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-jfi-rebuttal)

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

Download with Pro
Files
SKILL.md
---
name: jfi-rebuttal
description: Use to plan an R&R response letter for the Journal of Financial Intermediation — single-blind review where referees know you, often a small number of expert reports, and an editor whose decision is final. It structures the response; it does not fabricate results.
---

# R&R Rebuttal Strategy (jfi-rebuttal)

## When to trigger

- You received an R&R or a reject-with-encouragement and must reply to referees and the Managing Editor
- War-gaming likely objections before submitting (pre-mortem)

## JFI-specific posture (verified 2026-06-01; re-confirm on the official page)

- Review is **single-anonymized (single-blind)** — referees know who you are, so tone matters and
  gratuitous self-defense reads poorly.
- A paper may rest on a **minimum of one expert reviewer**, so a single decisive report can shape the
  outcome; treat each point as potentially pivotal.
- The **editor's decision is final** with no appeals channel — the response letter is your main (and
  possibly only) instrument; make it count rather than relying on a later escalation.
- The reviewer is a **banking / financial-intermediation specialist** — answer in the field's terms
  (identification of the intermediary mechanism, sample/bank-panel construction, robustness), not generic
  prose.

## Response-letter structure

1. **Cover note to the Managing Editor** — summarize the 2–4 substantive changes and how the paper is now
   stronger; keep it short.
2. **Point-by-point replies** — quote each referee comment, then respond:
   - **Agree + did it:** state the change and the new exhibit/section/line number.
   - **Agree in part:** scope the change; explain the boundary.
   - **Respectfully disagree:** give evidence (a robustness table, a derivation, a citation), never just assertion.
3. **Summary-of-changes table** — comment → change → location.
4. **Clean revised manuscript** plus a tracked-changes copy.

## Empirical vs. theory rebuttals

- **Empirical (bank/loan-panel):** answer endogeneity/selection challenges with a sharper design, a
  placebo, an alternative sample, or a clustering/inference fix — not hand-waving (see
  jfi-identification-strategy, jfi-data-analysis).
- **Theory:** address generality and assumption objections by stating which results survive a relaxed
  assumption, adding a proposition or a numerical example, or clarifying the proof step questioned.

## Anti-patterns

- A defensive tone toward a referee who knows your identity
- Promising changes without making them, or burying them where the referee cannot find them
- Treating a single referee's point as ignorable — it may be decisive
- Banking on an appeal for a decision the journal states is final

## Output format

```
【Editor note】2–4 line summary of substantive changes
【Replies】per comment: agree-did / agree-part / disagree-with-evidence
【Changes table】comment → change → location
【Files】clean + tracked-changes manuscript staged
```

Attribution

brycewang-stanfordbrycewang-stanford
View sourceMore from brycewang-stanford →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

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

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

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', ...

686011 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 →