Skip to content
Agentmart
Submit a tool

pre-submission-reviewer

Runs a pre-submission review of a technical paper across five dimensions: macro logic, writing details, English grammar, LaTeX formatting, and figure quality.

Skill by zms618

IndexedCC-BY-4.0
Write a review

Chalk Labs

Need help deploying pre-submission-reviewer?

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/zms618-pre-submission-reviewer

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

Runs a pre-submission review of a technical paper across five dimensions: macro logic, writing details, English grammar, LaTeX formatting, and figure quality. Uses a reviewer-style severity taxonomy (CRITICAL / MAJOR / MINOR) and flags banned AI-tone vocabulary and em-dash misuse. Use when the user asks to 'review this paper', 'audit before submission', 'check the draft', 'find issues', 'proofread', or within one week of a submission deadline.

Use cases: documents, security, 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/pre-submission-reviewer

What's inside

Skill name
pre-submission-reviewer
Description
Runs a pre-submission review of a technical paper across five dimensions: macro logic, writing details, English grammar, LaTeX formatting, and figure quality. Uses a reviewer-style severity taxonomy (CRITICAL / MAJOR / MINOR) and flags banned AI-tone vocabulary and em-dash misuse. Use when the user asks to 'review this paper', 'audit before submission', 'check the draft', 'find issues', 'proofread', or within one week of a submission deadline.
License
CC-BY-4.0
Instructions
314 lines in SKILL.md · view on GitHub

Files (6)

  • SKILL.md
  • forbidden-patterns.md · references/
  • grammar-rules.md · references/
  • latex-rules.md · references/
  • logic-and-structure.md · references/
  • section-guides.md · references/

SKILL.md (first lines)

# Pre-Submission Reviewer

## Overview

Three to five days before a submission deadline is the window where
a careful external review pays off most. This skill takes a full
paper or key sections and produces a structured review across five
dimensions, each with severity-tagged findings and concrete
rewrite suggestions. It enforces the mechanical rules from the
writing-checklist section (no em-dashes, no banned AI-tone
vocabulary, leading text per paragraph, topic-sentence discipline,
citation-format uniformity) and surfaces the patterns that
non-native English-speaking authors most commonly violate
(articles, subject-verb agreement, tense consistency, which versus
that, Chinglish phrasing).

The output is not a rewrite. It is a prioritised list of findings
with severity tags; the author decides which to fix. CRITICAL items
should block submission until addressed.

## When to use this skill

- Three to five days before a submission deadline.
- The user asks to 'review this paper', 'audit before submission',
  'check the draft', 'find issues', 'proofread'.
- After a camera-ready revision, before sending the final version.
- After any major rewrite (rebuttal responses, Section 3 overhaul).
- When the user suspects AI-tone contamination in a section.

## When NOT to use this skill

- The paper is still being structured. Use `tech-paper-template`,
  `intro-drafter`, or `benchmark-paper-template` (separate plugin) first.
- The user wants structural advice rather than review. Use the
  drafting skills instead.

## Core procedure

### Step 0: paradigm and venue fit

Before the dimensional review, settle two things.

**Paradigm**, judged by research method, because what counts as a
severe problem differs by paradigm:

- **STEM / technical** (CS, engineering, materials, chemistry): weight
  the Introduction chain, contribution-to-section mapping, baseline
  coverage, ablation-based attribution, figure quality. Benchmark
  papers additionally get coverage, reproducibility, and
  contamination checks; chemistry and materials get characterization
  completeness, purity, controls, replicates.
- **Humanities** (literature, history, philosophy, discourse
  analysis): weight whether the thesis is explicit and defensible,
  core concepts pinned down and stable across sections, the
  literature genuinely engaged, and the material (texts, archives,
  cases) able to carry the claims. Do **not** demand baselines or
  ablations here; check instead whether sub-arguments build on each
  other rather than sit in parallel, and whether conclusions outrun
  the material.
- **Empirical social science**: weight operationalized research
  questions, sampling and data-source justification, statistics
  matched to data types, conclusions bounded by the sample. For
  theory papers, "experiments" reads as "proofs": check the proofs,
  and never call the evidence thin merely because there is no results
  table.
- **Finance / economics**: weight identification credibility,
  endogeneity handling, robustness checks (their absence is a
  first-round flag), and economic versus merely statistical
  significance.
- **Law**: weight the accuracy of statutes, case numbers, and
  holdings (an invented or wrong citation is rejection-level), the
  clarity of the interpretive approach, and whether comparative
  arguments state their scope.

When the paradigm is unclear, ask the author before reviewing with
the wrong ruler.

**Venue fit**: if the stated target venue's scope visibly mismatches
the paper's topic or contribution type, that is a real rejection
risk, not a taste note. Flag it as a finding and suggest two or three
better-fitting venues.

### Step 1: Dimension 1 Macro logic review

See: references/logic-and-structure.md for the Logic First rule,
Self-contained rule, Leading Text rule, and Running Example rule.

Check:

- Introduction flowchart is intact (Background, Limitations, Goal
  or Key Idea, Challenges, Methodology, Contributions).
- Contributions map one-to-one with methodology modules and with
  section numbers.
- Experiments validate the paper's main claims, not tangential
  ones.
- Related Work covers the necessary prior art.
- Running example is consistent across Introduction, Methodology,
  Experiments.
- The headline result's attribution is isolated: an ablation
  separates the core mechanism from peripheral factors (a routing
  step, post-processing, a stronger base model, favorable samples).
  No such ablation: flag "attribution unverified" as MAJOR.
- Claims match their evidence: "solves" is stronger than most papers
  earn (usually "improves"); "state-of-the-art" needs the benchmark
  and conditions; "we are the first" gets checked or flagged.

Every break in the chain is CRITICAL.

**Retrieval-grounded checks** (when the environment has a
literature-search capability: a scholarly tool, web search over
scholarly indexes, or shell access to public APIs):

1. **Novelty verification**: extract two or three keyword groups from
   the paper's core method and problem setting, retrieve, and identify
   the three to five closest published works. If Related Work already
   covers them, the paper's positioning stands; a highly relevant
   uncovered work is a MAJOR finding ("missed X, Author et al.,
   Year"). Compare on difference axes; a similar title alone proves
   nothing.

From zms618/no-heartburn-academic-skills, CC-BY-4.0.

More from zms618/no-heartburn-academic-skills

Signals

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

From GitHub (fetched Oct 24, 2026).

Details

License
CC-BY-4.0
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from zms618

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 pre-submission-reviewer 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 pre-submission-reviewer?

CallGet help
Cite this page

pre-submission-reviewer skill. Agent Mart. https://agentmart.dev/skills/zms618-pre-submission-reviewer (last updated 2026-10-24)