submission-audit
Submission Audit
Overview
Use this skill for late-stage manuscript QA. It is narrower than manuscript-optimizer: do not use it to redesign a paper from scratch. Use it when the structure mostly exists and the main task is to catch the failures that survive normal revision cycles.
The core rule is simple: never treat a clean-looking manuscript as submission-ready until the front half, figures, legends, methods, supplement, and venue expectations have been checked against each other.
Use the helper script when you want a fast local pass over figure citations:
python ~/.codex/skills/submission-audit/scripts/check_figure_refs.py path/to/manuscript.md
# Claude Code (global install): replace ~/.codex/skills with ~/.claude/skills
# Claude Code (project-local install): replace ~/.codex/skills with .claude/skills
When To Use
Use this skill when:
More from boom5426/nature-paper-skills
academic-presentations
>-
18paper-workflow
Use when deciding which paper-related skill to use or how to sequence manuscript work from project setup through submission and rebuttal.
15reference-audit-guide
Use when the user asks for citation-verification principles, reference-audit best practices, or guidance on preventing fake or inaccurate citations in academic writing.
14rebuttal-response
Use when responding to journal or conference reviewer comments and you need a structured author response, aligned manuscript edits, and clear decisions about when to clarify, add evidence, concede, or respectfully disagree.
14paper-reviewer
Use when acting as a journal or grant reviewer and writing formal reviewer-side evaluations focused on methodology, statistics, reporting standards, reproducibility, and constructive feedback.
13paper-bootstrap
Use when starting a new manuscript project or cleaning up an existing paper directory and you need a standard structure, active source files, project memory, and venue defaults before deeper writing begins.
12