Agent skill · Code Review & Quality

tar-review-process

Use when understanding how The Accounting Review (TAR) review and decisions work, or when reading a TAR decision letter — the editor routing, double-blind two-reviewer model, decision types, and post-publication integrity rules. Explains and interprets the process; it does not draft the revision and response (tar-rebuttal).

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

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

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Path: The-Accounting-Review-Skills/skills/tar-review-process/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

# Understanding TAR Review (tar-review-process) ## When to trigger - You want to set realistic expectations before or after submitting to TAR - A decision letter arrived and you need to read its signal before responding - You are unsure who the Senior Editor / Lead Editor / Editor / Ad hoc Editor are in the process - You want to know what "anonymity," "data authenticity," or "Expression of Concern" mean for you ## How TAR routes a manuscript TAR uses a **tiered editor structure** distinct from INFORMS-style permanent departmental area-editors: - A single **Senior Editor** oversees the whole process — **Mohan Venkatachalam (Duke, Fuqua), sitting Senior Editor since June 2026** (succeeding Kathryn Kadous, Emory; verify the current masthead). - Named **Lead Editors** (e.g., Brian Mittendorf, Edward L. Maydew, Kristina M. Rennekamp, Paul Hribar) share Senior-Editor responsibilities: assigning editors, issuing decision letters, handling **desk rejections** and **appeals**. - A bench of roughly two dozen standing **Editors** handle manuscripts in their areas (roster 待核实). - **Ad hoc Editors** are appointed for specialized topics/methods a manuscript requires. A submission may be **desk-r

What's inside
Steps it walks through
  1. When to trigger
  2. How TAR routes a manuscript
  3. Reading the decision
  4. Integrity & post-publication rules to know
  5. What you control
  6. Checklist
  7. Anti-patterns
  8. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the tar-review-process skill do?

Use when understanding how The Accounting Review (TAR) review and decisions work, or when reading a TAR decision letter — the editor routing, double-blind two-reviewer model, decision types, and post-publication integrity rules. Explains and interprets the process; it does not draft the revision and response (tar-rebuttal).

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill tar-review-process --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