Skip to content
Agentmart
Submit a tool

manuscript-review

Referee a full manuscript against a named target journal through independent lenses on style, consistency, unsupported claims, math, exhibits, and…

Skill by bobbyZhong10

IndexedMIT
Write a review

Chalk Labs

Need help deploying manuscript-review?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/bobbyzhong10-manuscript-review

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Referee a full manuscript against a named target journal through independent lenses on style, consistency, unsupported claims, math, exhibits, and contribution, triaged CRITICAL/MAJOR/MINOR. TRIGGER on review my paper, referee my draft, is this ready to submit, what would a referee say, desk reject risk, read this like Reviewer 2, referee this for a journal, or write my referee report. Critiquing an idea or plan is council; answering referees is referee-response.

Use cases: documents, writing, research

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/manuscript-review

What's inside

Skill name
manuscript-review
Description
Referee a full manuscript against a named target journal through independent lenses on style, consistency, unsupported claims, math, exhibits, and contribution, triaged CRITICAL/MAJOR/MINOR. TRIGGER on review my paper, referee my draft, is this ready to submit, what would a referee say, desk reject risk, read this like Reviewer 2, referee this for a journal, or write my referee report. Critiquing an idea or plan is council; answering referees is referee-response.
License
MIT
Instructions
420 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# manuscript-review

This file is the canonical Empirical Workflow Kit implementation. Runtime views
defined in `workflow.manifest.yaml` link here; edit only the canonical tree.

Resolve `<skills_root>` from `workflow.manifest.yaml:canonical_source.skills_root`
before using a path below.

Adapted from `ericluo04/claude-academic-workflow` at commit `8958cc246e65cdf7c36604f397a1c1719b7e2c14`; see `THIRD_PARTY_NOTICES.md`.

Six agents read the manuscript in parallel and return severity-tagged findings with quoted
evidence; the main thread consolidates them into one dated report ranked by what would sink the
paper. Nothing in the manuscript is edited. Topology and agent roles adapted from
[`claesbackman/AI-research-feedback`](https://github.com/claesbackman/AI-research-feedback), the
reader-understanding assessment from
[`aspi6246/Claude-Code-Presentation`](https://github.com/aspi6246/Claude-Code-Presentation).

For research organization, economic meaning, contribution, and behavioral claims,
read `../empirical-workflow/references/research-writing.md` before synthesis or
drafting. Apply the relevant evidence-strategy boundary; do not turn the
operation's output format into a mandatory manuscript structure.

## Options

| Argument | Default | Meaning |
|---|---|---|
| a journal name (first token) | `top-field` | journal persona and bar for agent 6 |
| a file path | auto-detect | main `.tex`, or a `.pdf` of the compiled draft |
| `--quick` | off | run only agents 6 and 3, skip the rest |
| `--referee` | off | journal referee mode: a submittable report, see below |

Recognized journals, case-insensitive, covering the UTD 24 and FT 50 lists plus the top economics
and IO journals; full names, publishers, and list membership are in
`<skills_root>/literature-review/references/journal-scope.md`. Information systems: `MISQ`,
`ISR`, `JMIS`, `IJOC`. Operations: `OR` (or `OpsRes`), `MSOM`, `POM`, `JOM`. Marketing: `MKSCI`,
`JMR`, `JM`, `JCR`, `JCP`, `JAMS`. Management and organization: `AMJ`, `AMR`, `ASQ`, `OrgSci`,
`SMJ`, `JIBS`, `JMgmt`, `JMS`, `OrgStud`, `OBHDP`, `JAP`, `ResPol`, `JBV`, `ETP`, `SEJ`.
Current FT 50 additions: `AMA` (Academy of Management Annals), `ASR` (American Sociological
Review), `PsychSci` (Psychological Science). Former FT 50 titles remain recognized as valid target
aliases but are not labeled current FT 50 unless the central scope reference says so.
Cross-field: `MS`. Accounting: `TAR`, `JAR`, `JAE`, `AOS`, `CAR`, `RAST`. Finance: `JF`, `JFE`,
`RFS`, `JFQA`, `RoF`. Economics: `AER`, `AERI`, `QJE`, `JPE`, `Econometrica`, `REStud`, `REStat`,
`JEEA`, `AEJApplied`, `AEJPolicy`, `AEJMicro`, `AEJMacro`, `JME`, `RED`. Industrial
organization: `RAND`, `JIE`, `IJIO`, `JEMS`, `QME`. Anything unrecognized is treated as a file
path, and an absent journal means `top-field`: high general standards for a leading field
journal, no specific persona. Add journals by editing this list. Store the result as
`TARGET_JOURNAL`.

## Referee mode

Before reviewing a third party's submission, complete the protocol's policy and confidentiality
check. If the journal, institution, agreement, or consent terms do not authorize transfer to the
active model or service, stop. Record the authority and permitted scope in the review request.

`--referee` switches the skill from a pre-submission check on the user's own draft to a
submittable report on a paper the user is refereeing for a journal. Enter this mode when the flag
is passed, when the user says they are refereeing, or when the paper is clearly not theirs. When
it is ambiguous whose paper it is, ask which hat the user is wearing before doing anything else.

What changes:

- The manuscript must be supplied as a path or a PDF. Phase 1 uses step 1 only; never glob the
  working directory or the Overleaf projects. If no path was given, ask for one.
- Agent 6 keeps its full brief, including the reader-understanding assessment, but critiques the paper
  for the editor and drops every piece of advice addressed to the author: no fallback outlets in
  part 5, no coaching on what would reach the target's bar. Its recommendation becomes one of the
  journal's conventional decisions: accept, minor revision, major revision, or reject.
- All six agents still run (two with `--quick`), and the CRITICAL/MAJOR/MINOR triage still
  happens, as internal analysis. The final report is written from that analysis and never shows
  the tags.

The output replaces the phase 3 structure. Write `REFEREE_REPORT_<YYYY-MM-DD>.md` to the current
working directory, or wherever the user says; never into an Overleaf project. Address it to the
editor and the authors in the conventional register:

1. A summary paragraph restating the paper in the referee's own words: the research question, the
   design, the data, and the main findings. Specific enough to show the paper was read.
2. Major comments, numbered. Built from the CRITICAL and MAJOR findings: identification threats,
   missing analyses, overclaiming, internal contradictions. Each states the issue, points at the
   exact location, and where possible says what would resolve it.
3. Minor comments, numbered. Notation, exposition, table and figure documentation, typos worth
   the authors' time. Compress agent 1's copy edits into a few representative items; a referee
   report is not a proofreading pass.
4. Recommendation, with a short justification tied to the major comments.

Report back in chat: the report path, the recommendation, and the counts of major and minor
comments.

## Phase 1: find the manuscript

1. An explicit path argument wins. Route PDFs through the helper configured in
   `runtime-profile.yaml`:
   `$EWF_PDF_HELPER text paper.pdf` for the text, or
   `$EWF_PDF_HELPER png paper.pdf --pages N --dpi 150 --out /tmp/p` and then Read
   the PNG when the layout or a figure matters.
2. No path: Glob `**/*.tex` in the working directory.
3. Still nothing: search the manuscript roots configured in `runtime-profile.yaml`, show the
   matching project directories, and ask which one. Do not guess between projects.

In referee mode, step 1 is the only step: skip steps 2 and 3 and ask for the path if none was
given.

When parallel workers are unavailable or not authorized, execute the same six lenses sequentially
into separate immutable findings files. Do not let later lenses read earlier verdicts. Consolidate
only after all requested lenses finish; consequence, not vote count, sets priority.

Then build the file set. The main document is the `.tex` containing `\documentclass` or
`\begin{document}`; follow every `\input`, `\include`, and `\subfile` to get the rest, and read
all of them. Figures are `**/[Ff]igure*/**/*.pdf` and the same for `png`, `jpg`, `jpeg`, `eps`,
`svg`, plus root-level images. Tables are `**/[Tt]able*/**/*.tex` plus root-level
`*[Tt]able*.tex`. Exclude `**/_minted-*/**`, `**/build/**`, `**/output/**`, `**/.git/**`, and
Dropbox conflicted copies (`*conflicted copy*`), which are stale and produce phantom findings.

Record every file path and its role, the figure and table lists, and the title, authors, and
abstract. If no figures turn up, tell the user they may live in a non-standard directory and to
re-run with an explicit path. Same for tables, adding that agent 5 will then be limited to
captions and cross-references.

## Manuscript-only cold read

From bobbyZhong10/empirical-workflow-kit, MIT.

More from bobbyZhong10/empirical-workflow-kit

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Oct 5, 2026 (25 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from bobbyZhong10

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get manuscript-review running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying manuscript-review?

CallGet help
Cite this page

manuscript-review skill. Agent Mart. https://agentmart.dev/skills/bobbyzhong10-manuscript-review (last updated 2026-10-24)