Agent skill · Business & Finance

finman-rebuttal

Use when a Financial Management (FM) decision letter arrives (R&R or conditional accept) and a response-to-referees letter plus a revision plan must be drafted. Plans and structures the response; it does not run the new analysis (finman-identification / finman-robustness) or the resubmission preflight (finman-submission).

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill finman-rebuttal --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 7 KB
Bundled scripts: none
Path: Financial-Management-Skills/skills/finman-rebuttal/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Rebuttal & Response Letter (finman-rebuttal) ## When to trigger - An FM **R&R** or **conditional acceptance** decision letter has arrived - You need to triage referee comments into must-do / argue / defer - You are drafting the response-to-referees document and the revision plan - A reject-with-encouragement note needs a strategy before any re-engagement ## How to read an FM decision The editor's letter is the **priority signal**: it tells you which referee concerns are binding and which are optional. Given FM's criteria, the binding asks usually concern **credibility (identification/inference)** and **whether the contribution is interesting and general enough**, rather than robustness volume — FM **under-weights trivial robustness**, so an R&R rarely turns on "run ten more checks." Address the editor's stated priorities first and in full; treat the referee reports as the menu the editor has already filtered. Because FM values papers "people actually read," a revision that also **sharpens the framing and the so-what** — not just the econometrics — reads as responsive to the journal's taste. A revision is judged on whether the binding concerns are genuinely resolved and the paper

What's inside
Steps it walks through
  1. When to trigger
  2. How to read an FM decision
  3. Response-letter structure
  4. Triage table
  5. Checklist
  6. Anti-patterns
  7. The FM-specific revision instinct
  8. Worked vignette (illustrative)
  9. Handling a reject-with-encouragement
  10. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the finman-rebuttal skill do?

Use when a Financial Management (FM) decision letter arrives (R&R or conditional accept) and a response-to-referees letter plus a revision plan must be drafted. Plans and structures the response; it does not run the new analysis (finman-identification / finman-robustness) or the resubmission preflight (finman-submission).

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill finman-rebuttal --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.

Keep going