Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

submission

Estrellas4

Forks0

Actualizado14 de julio de 2026 a las 23:50

Pre-submission checks, bibliography verification, and peer-review responses. Use when the manuscript nears submission, when verifying references, or when responding to reviewers.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

claycantrell

claycantrell/claude-research-scaffold

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

EditoresArtes, diseño, entretenimiento, deportes y medios·SOC 27-3041

SKILL.md

readonly

name	submission
description	Pre-submission checks, bibliography verification, and peer-review responses. Use when the manuscript nears submission, when verifying references, or when responding to reviewers.

Submission

When the manuscript is nearing submission

Copy templates/submission-checklist.md to the project root as submission-checklist.md
Work through it top to bottom with the user, checking items off in the file
make verify-bib — verifies every references.bib entry (authors, given names, year, title) against Crossref/arXiv. Fix every ✗ against the published record; manually check every ? (books, workshop papers) and ⚠ (author-name variants)
Grounding pass: for every example, quote, and statistic in the manuscript, open the underlying source file and confirm it matches verbatim
Claims pass: search for "prove", "demonstrate", "show that", "establish" — downgrade to "suggest"/"indicate" where evidence is correlational or ablation-based
Run make lint, make grammar, make readability; build with make pdf and read the whole PDF at print size (figures especially)
After submitting: record venue, date, and version in progress.md; tag the snapshot git tag submitted-<venue>-<date>

Verifying a single source's standing

make verify DOI="..." — has the paper been supported or contradicted? (optional tool: needs a paid scite.ai account; if missing, check the paper's citations manually on scite.ai or Semantic Scholar)
Report supported/contradicted/mixed; suggest alternatives if disputed

Responding to peer review

Copy templates/peer-review-response.md into manuscript/
Fill in responses point by point with the user — quote each reviewer comment, state the change made, cite where in the manuscript
make diff OLD="<submitted version>" NEW="manuscript/main.md" — track-changes PDF for the resubmission
Record the revision round in progress.md

Repo hygiene for published papers

Replace the scaffold README with a paper-specific one: key finding, repo structure, reproduction steps, dataset table
Confirm the code-availability link works from a fresh clone

Más de este repositorio

mismo repositorio

building-the-paper

claycantrell/claude-research-scaffold

Build the manuscript to PDF/DOCX/HTML, create figures and diagrams, manage cross-references, and run writing-quality checks (lint, grammar, readability).

2026-07-144

finding-papers

claycantrell/claude-research-scaffold

Search academic literature, manage the search queue, download papers, and verify sources. Use when the user wants to find papers, when working search-queue.md, or when adding references.

2026-07-144

drafting

claycantrell/claude-research-scaffold

Create writing plans, section drafts, and manuscript prose. Use when drafting or editing any part of the paper, building evidence chains from notes, or planning the writing.

2026-07-144

empirical-experiments

claycantrell/claude-research-scaffold

Conventions for projects that generate their own results — running models, labeling data, computing statistics. Use when writing or running experiment code, or when drafting sections that report original results.

2026-07-144

git-for-beginners

claycantrell/claude-research-scaffold

Plain-language Git for a non-technical user — snapshots, backups, undo, and disaster recovery. Use for any Git operation beyond a routine commit, and whenever the user says save, back up, undo, or go back.

2026-07-144

reading-notes

claycantrell/claude-research-scaffold

Extract text from papers, summarize them, and create reading notes. Use when reading or summarizing a paper, and automatically after downloading one.

2026-07-144

Submission

When the manuscript is nearing submission

Copy templates/submission-checklist.md to the project root as submission-checklist.md

Work through it top to bottom with the user, checking items off in the file

make verify-bib — verifies every references.bib entry (authors, given names, year, title) against Crossref/arXiv. Fix every ✗ against the published record; manually check every ? (books, workshop papers) and ⚠ (author-name variants)

Grounding pass: for every example, quote, and statistic in the manuscript, open the underlying source file and confirm it matches verbatim

Claims pass: search for "prove", "demonstrate", "show that", "establish" — downgrade to "suggest"/"indicate" where evidence is correlational or ablation-based

Run make lint, make grammar, make readability; build with make pdf and read the whole PDF at print size (figures especially)

After submitting: record venue, date, and version in progress.md; tag the snapshot git tag submitted-<venue>-<date>

Verifying a single source's standing

make verify DOI="..." — has the paper been supported or contradicted? (optional tool: needs a paid scite.ai account; if missing, check the paper's citations manually on scite.ai or Semantic Scholar)

Report supported/contradicted/mixed; suggest alternatives if disputed

Responding to peer review

Copy templates/peer-review-response.md into manuscript/

Fill in responses point by point with the user — quote each reviewer comment, state the change made, cite where in the manuscript

make diff OLD="<submitted version>" NEW="manuscript/main.md" — track-changes PDF for the resubmission

Record the revision round in progress.md

Repo hygiene for published papers

Replace the scaffold README with a paper-specific one: key finding, repo structure, reproduction steps, dataset table

Confirm the code-availability link works from a fresh clone