ts-paper-review

Runs adversarial multi-reviewer peer review on academic paper drafts with verified issue lists.

1.1k|19|Updated Jun 18, 2026
One-click install
npx skills add https://github.com/Spark-To-Paper-Skills/spark-to-paper-skills --skill ts-paper-review-spark-to-paper-skills
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ts-paper-review
Source: https://github.com/Spark-To-Paper-Skills/spark-to-paper-skills/tree/main/skills/ts-paper-review
Command: npx skills add https://github.com/Spark-To-Paper-Skills/spark-to-paper-skills --skill ts-paper-review-spark-to-paper-skills

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Forward-only drafting and polishing pipelines never argue against a paper the way a real reviewer will, so weak claims, unsupported numbers, and internal inconsistencies survive into the final PDF. This Skill hardens a drafted paper by simulating an adversarial peer-review panel before figures and LaTeX finalization. ## Core Features & Use Cases - Isolated multi-lens review: N reviewers (Theory/Foundations, Empirical/Benchmark, Applied/Systems) each read the whole paper independently, and every issue must carry an exact verbatim evidence quote plus a close criterion. - Adversarial verification: Each candidate issue faces three perspective-diverse skeptics (misreading, already-addressed, scope-or-severity) and survives only if a majority fails to refute it, filtering plausible-but-wrong critiques. - Loop-until-dry with tiered execution: Review rounds repeat until no new issues survive, running identically via a Workflow script, parallel subagents, or in-context sequential role-play depending on available tools. - Use Case: After refining a research proposal draft, run this stage to get a prioritized, severity-sorted issue list (blocker/major/minor/nit), fix each item through the refine stage against its close criterion, then re-run lint checks to confirm the fixes landed cleanly. ## Quick Start Review my drafted paper in the current working directory with an adversarial reviewer panel and list the verified issues by severity.

Frequently Asked Questions about ts-paper-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run an adversarial peer review on my paper draft?

Assemble the paper text from your section files, then invoke the review stage with a venue profile and results mode. It returns a severity-sorted issue list with verbatim evidence quotes and close criteria that you fix through the refine stage.

What is the difference between proposal and data_aware review modes?

Proposal mode treats blank result tables as intentional and judges method soundness, novelty, and evaluation plan quality. Data_aware mode applies full claims-versus-evidence scrutiny, checking that numbers support claims, baselines are fair, and ablations are covered.

Can the review run without the Workflow tool available?

Yes. The algorithm has three execution tiers: a Workflow script, parallel subagents via a Task or Agent tool, and in-context sequential role-play. All tiers produce the identical issue structure and log output, so the review is never skipped for missing tooling.

How does the review filter out false or invalid issues?

Each candidate issue faces three adversarial verifiers arguing misreading, already-addressed, and scope-or-severity angles. An issue is dropped when at least two of the three angles refute it, and issues lacking a usable close criterion are discarded at merge time.

When should I skip the paper review stage?

Skip only when the user explicitly requests a quick or no-review draft, recording the opt-out in the route log. It is not a substitute for an official venue rebuttal or a from-scratch drafter, and single requested edits belong to the refine stage.